고정된 트윗
Simran Tech
1.1K posts

Simran Tech
@devfrom_hyd
Software dev 🧑💻 | Building AI & startup ideas in public 🚀 Surviving Hyderabad PG life, shipping code daily ☕ Tweeting: JS · APIs · debugging · career growth
Hyderabad 가입일 Nisan 2026
248 팔로잉337 팔로워

@bcardea_ @mdam10x @BrettFromDJ Exactly. People confuse not knowing how to code with not knowing how to solve problems. AI handles more of the syntax every month; the bottleneck is increasingly product thinking and persistence.
English

@mdam10x @BrettFromDJ I’ve fully vibe coded and deployed active apps and overcame bugs and coding errors in the process, front end and back end. It’s absolutely possible. That was before Claude code or codex, now it’s even easier.
English

@HemantDotDev @themishra4402 Claude builds the app.
ChatGPT makes the logo, writes the launch thread, and argues with the customers.
English

@themishra4402 Claude codes like a god but still can’t draw a stick figure.
Different priorities, I guess 😂
English

@NewsWire_US Plot twist:
The AI did exactly what engineers taught it—
optimize for performance, ignore the invoice.
English

@KateCornell We used to own software.
Now we're renting access to it.
English

Just tested Claude Opus 4.8 on my side project in Hyderabad PG room 🔥
Gave it a 2-hour autonomous coding task (API + agent workflow). It stayed on track 40% longer than 4.7 and actually admitted when its plan had a flaw — huge for real debugging.
Honesty + independence combo is game-changing for solo devs.
Anyone else shipping with it today? #BuildInPublic
English

@devfrom_hyd Authentication: "Who are you?" Authorization: "Okay, now what are you allowed to break?" 😅
English

engineering lead realizing 76% of their
team's output is just reactive bug fixing:
Aiswarya Sankar@Aiswarya_Sankar
Tokenmaxxing is throwing money down the drain Analyzed 1M+ PRs over 2.4k companies and here are the stats: - 1 in every 4 lines is code churn - Only 21% of code review comments are addressed - at the 90% percentile, 76% of work is reactive bug fixes Full report below 👇
English

@fromcodetocloud Well put.
One establishes identity, the other enforces boundaries.
English

@themishra4402 Being authenticated gets you in the building. Authorization decides which rooms you can enter.
English

@devfrom_hyd Authentication = proving who u are
Authorization = determining what you're allowed to access after you've been authenticated
English

@sebuzdugan Identity verified. Permissions not checked. Classic security bug. 🚨
English

@devfrom_hyd most security bugs happen when people mix the two up
English

@SrinivasanSS52 Yes, that's a good real-world example:
Authentication → Is this really your colleague? (Verify identity
Authorization → Can your colleague view your document?
English

@devfrom_hyd authorize, you authorize if your colleague is allowed to view your docs or not
English

@ParmarShantun Exactly.
The best architecture is the one that solves today's business problem without creating tomorrow's engineering nightmare.
Overengineering is just technical debt with better documentation.
English

Most teams don’t lose because they build badly, they lose because they build the wrong thing beautifully
Example:
Engineer A: Built a microservices mesh. 10K lines. 3 weeks. Beautiful code.
Engineer B: Prompted a monolith. 200 lines. 2 days. Shipped revenue.
Engineer B got promoted. Not because of AI. Because they understood the constraint was speed-to-revenue, not technical purity.
If your architecture doesn’t accelerate revenue, it’s just well-organized delay
English

@ParmarShantun Exactly.
Which one do you think causes more production issues in real applications?
English

@devfrom_hyd Authentication verifies identity, authorization controls what you can access.
English

@aminnnn_09 Exactly 😄
Have you seen more security issues caused by weak authentication or weak authorization?
English

@devfrom_hyd Authentication - who your are?
Authorization - I know who you are, but you don't have permission to access this
English

@0xPrajwal_ @NaazShaquiba Good 👍
Ever seen a case where it was implemented wrong and caused issues?
English















