@javarevisited You can build any app in 2 days, but the right app still takes 2 months and then you have to pivot. Nothings changed other that you can pivot faster. Clients will still discuss for weeks about the position of a button and then remove the button completely though.
@Akasheth_ Not exactly true. I’ve become more productive and I’m exploring ways to automate certain parts of my productivity.
The token price crunch that is coming will be interesting as everyone’s automations start to attract a real cost. There will be pressure to justify that cost.
software engineers are the luckiest people right now.
they pay ~$200/month for AI to help with the work.
their company still pays them $10,000/month for the result
that’s $9,800 profit for talking to AI
the funny part?
no one with a full-time dev job is gonna say this publicly
everyone’s just quietly enjoying it
what a time to be alive.
@kareem_carr You still read a lot of code, make a lot of decisions around the code. Also make hand coded minor fixes. The AI is just a tool. And it’s allowed knowledge rich engineers as powerful as a dev team from 6 months ago. And non engineers as powerful and dangerous as a junior dev.
I keep hearing that software engineers don’t write much code anymore and it’s mostly AI now. Can any software engineers confirm how true this is?
Do you just drink coffee and watch Claude code all day now?
Serious question:
Is there any programmer left in the room still coding the traditional way, character by character, without using AI?
If so, why? Explain your reasoning.
we're making @blocks smaller today. here's my note to the company.
####
today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.
first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.
we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.
i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.
a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.
we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.
to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.
to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.
jack
@gerardsans@afiqsazlan Maybe, we can move from software engineering to solving software bottlenecks. At the end of the day, 90 percent of engineering was around coding, maintaining, understanding, reading modifying. Meetings, documentation where hurdles to getting back to the real work.
Software engineering was never about coding. Code is the last step, like pouring concrete into a foundation. The real work is architecture, systems thinking, trade-offs, and product-market fit.
You’re confusing tools with the discipline. Better materials don’t change structural physics. AI may help you build faster, but it doesn’t replace engineering judgment.
And engineering isn’t about chasing perceived demand for personal gain, it’s about building systems that actually solve customer problems. If the outcome for users is secondary, that’s not engineering, that’s chasing a payslip.
I'm rethinking my career as a software engineer.
The more I use AI in my daily work, the more I don't think doubling down on coding is the way forward. I do feel I'm doing more product management, but I don't think that's the way forward either. Should I consider AI/ML science or engineering?
Can anyone recommend books that offer a framework for figuring out where to pivot your career?
in the last 24 hours, I have vibecoded my own and better versions of:
- adobe
- intuit
- salesforce
- shopify
- applovin
- atlassian
- snowflake
- datadog
- cloudflare
- zoom
You can just build things
Skipping the source code could lead to "un-hackable" software.
Since there’s no underlying source code for a human to reverse-engineer or find vulnerabilities in, the binary becomes a black box that only the AI understands.
It would move security from patching bugs to just regenerating a fresh, hardened version of the app every single day.
That kind of speed would change everything about how we use computers.
Elon Musk predicts that AI will bypass coding entirely by the end of 2026 - just creates the binary directly
AI can create a much more efficient binary than can be done by any compiler
So just say, "Create optimized binary for this particular outcome," and you actually bypass even traditional coding
Current: Code → Compiler → Binary → Execute
Future: Prompt → AI-generated Binary → Execute
Grok Code is going to be state-of-the-art in 2–3 months
Software development is about to fundamentally change
AI will eat most of the jobs in next 2-5 years:
Roles at high risk:
- Frontend devs
- Backend devs
- Full-stack devs
- Jr. software engineers
- QA testers
- Basic data analysts
Roles that are safe:
- UI/UX and graphic designers
- Software/system architects
- Entrepreneurs
- AI specialists
Codex is fucking insane
i know literally NOTHING about coding. ZERO. and i just built a fully functioning web app in minutes.
http://localhost:3000/
check it out
@SumitM_X I gotta be honest. Just ask the ai for best practices of microservices architecture. I guess the engineer has to make decisions granted and a senior engineer knows to ask these questions granted. A simple prompt at the start to help the junior dev understand what’s required.
I saw a junior developer create a microservice using ChatGPT in 30 seconds.
I asked one question:
What happens to the data if the other service is down for 10 minutes?
He didnt know.
The AI didnt explain backpressure.
It didnt explain idempotency.
It didnt explain dead letter queues.
Writing code is easy now.
But
Engineering is still hard.
I flagged Bitcoin’s looming crash weeks ago. Shell-shocked investors missed these warning signs. The plunge is clearing out the weak. What comes next will be historic, writes ASX Trader.