Leadership across companies expects AI to magically cut time-to-ship in half.
Yes, AI can help engineers code faster. But coding was never the bottleneck.
The real drag is non-tech stuff - planning, periodic status updates, cross-team coordination, unclear requirements, stakeholder alignment, reviews, approvals, handoffs, deployment cycles, and on-call rotations.
Cumulatively, that's ~80% of the work.
Optimizing the remaining ~20% cannot produce a 50% reduction.
If leaders really want to see gains, they should focus less on coding velocity and more on eliminating process friction.
Why you should never work with Indian clients:
>Their requirements change every sec
>No professionalism while communications
>Treats you like they have bought you
>Chick chick during payments
>Expects you to complete complex website for $10
>Will call you anytime like you are their pet
Horrible horrible
@hellonehha We have a team whatsapp group. Only one rule. We are not supposed to talk about work. It is usually used to share personal milestones. New house, marriages, trips etc.
It gets active like thrice a year.
@max_spero_ The top 1% of engineers I have worked with during the past 10 years didn't have GitHub, LinkedIn and LeetCode, they don't make talks for conferences, they don't host podcasts. But they built systems that no one else can do.
If you want your vibe coding to be better, all you have to do is
- write detailed specs and technical documents
- create tons of automated tests
- use old industry standard technologies
- code review a lot more
- manually QA every detail
…maybe I’ll stick to writing code
@ImSh4yy What bothers me is that vibe coding is now the expectation of investors, VCs, and rich "idea guys" in general. Planning for proper engineering is not allowed anymore, because they've "learned" in bootcamp that AI can do everything.
@Myprotein I had placed an order on Aug 31st, the package reached the nearest delivery facility in a week and an attempt for delivery was not made. After getting rescheduled for the next day for two weeks, the package is now auto returned. No help from support after multiple req