Rocky Stefano

So what you're saying is that AI allowed you to hit the road running whereas traditional devs take six months to "get up to speed" I'll take it. Especially since I was only given the first three months of their employment to figure out whether they actually knew what they were talking about...

Joined a new AI-native company this week and it’s kind of wild how different it feels already. The laptop arrived, I logged in, and an agent basically took over from there. It set up my dev env, pulled repos, fixed dependency issues, got permissions approved, pointed me at the backlog, linked the architecture docs, and surfaced the Slack debates I actually needed to read before touching production. When I needed context on something, I asked the agent and it found the exact thread from months ago explaining why a decision was made, who owned it, the related Linear issues, and the PRs connected to it. I’ve only been here 3 days but it honestly feels like I’ve worked here for a year because the usual friction and scavenger hunt for context just isn’t there anymore. We should probably stop calling this “onboarding” and rename it to “mounting” because this feels a lot more like mounting a distributed filesystem called “institutional memory” than slowly getting drip-fed context over 6 months.

@akshay_pachaar That was one of the best-written articles I've seen on the subject so far. Thanks very much.

@sama If the model took a minute longer I wouldn't care if it was 50% smarter

i get some anxiety not using the smartest-available model/settings. but sometimes i dont mind if it's really slow. i wonder if we should focus more on a price/speed tradeoff relative to a price/intelligence tradeoff.

@Raptors what's the point of taking @boyles_murray off the court in the 4th quarter? Because he was in foul trouble? Who cares if he is? Let him foul out. He's far more important to us on the court than sitting on the bench letting us lose our lead in the fourth.

It's about time... Too many anonymous bros online greekcitytimes.com/2026/04/28/gre… via @greekcitytimes

@TheGeorgePu Honestly, if I was in my fifties, had worked for a company for 30 years and they basically gifted me early retirement with full benefits.. I would take it in a minute

9,000 Microsoft employees got an email at lunch today. Take the money. Go home. The safest job in tech. Gone in an afternoon. Nobody called it a firing. They called it a retirement gift. This is 2026.

Our company never ran out of credit. This month we barely used it, and I get a message saying that we have to buy more. When I tell you you barely used the service I'm not kidding. If that's what you guys are[ plan on doing in the future I'd rather take the cost of spending $50,000 on having my own model internally

I am happy everyone is switching to Codex, but Tibo if you start rate limiting me or making me use worse models...

Speaking both from the perspective of a parent and an employer, I can tell you that with this sort of technology there is always going to be attrition at some level. People that are quick on their feet, can see the changes coming, and move appropriately, won't have an issue. The ones who think nothing will change, will be the ones left behind. Do I feel for those students that can't find a job? Yes I do, much like I did for my own children when they graduated from uni. However they work hard, the jobs they didn't like until they found ones they did, and now they're thriving. Laziness gets you nowhere. Developers are always going to have work, it might change over time and it may not be what they want, but they'll always have a job.

As AI agents accelerate coding, what is the future of software engineering? Some trends are clear, such as the Product Management Bottleneck, referring to the idea that we are more constrained by deciding what to build rather than the actual building. But many implications, like AI’s impact on the job market, how software teams will be organized, and more, are still being sorted out. The theme of our AI Developer Conference on April 28-29 in San Francisco is The Future of Software Engineering. I look forward to speaking about this topic there, hearing from other speakers on this theme, and chatting with attendees about it. We’re shaping the future, and I hope you will join me there! It is currently trendy in some technology and policy circles to forecast massive job losses due to AI. Even if they have not yet materialized, these losses certainly must be just over the horizon! I have a contrarian view that the AI jobpocalypse — the notion that AI will lead to massive unemployment, perhaps even rioting in the streets — won’t be nearly as bad as dire forecasts by pundits, especially pundits who are trying to paint a picture of how powerful their AI technology is. Among professions, AI is accelerating software engineering most, given the rise of coding agents. According to a new report by Citadel Research, software engineering job postings are rising rapidly. So if software engineering is a harbinger of the impact AI will have on other professions, this expansion of software engineering jobs is encouraging. Yes, fresh college graduates are having a hard time finding jobs. And yes, there have been layoffs that CEOs have attributed to AI, even if a large fraction of this was “AI washing,” where businesses choose to attribute layoffs to AI, even though AI has not changed their internal operations much yet. And yes, there is a subset of job roles, such as call center operator, that are more heavily impacted. Many people are feeling significant job insecurity, and I feel for everyone struggling with employment, whether or not the cause is AI-related. And many other factors, such as over-hiring during the pandemic and high interest rates, have contributed to the slowdown in the labor market, and the notion that AI is leading to unemployment is oversimplified. In software engineering, I see a lot of exciting work ahead to adapt our workflows. It is already clear that: (i) As AI makes coding easier, a lot more people will be doing it. (ii) Writing code by hand and even reading (generated) code is not that important, because we can ask an LLM about the code and operate at a higher level than the raw syntax (although how high we can or should go is rapidly changing). (iii) There will be a lot more custom applications, because now it’s economical to write software for smaller and smaller audiences. (iv) Deciding what to build, more than the actual building, is becoming a bottleneck. (v) The cost of paying down technical debt is decreasing (since AI can refactor for you). At the same time, there are also a lot of open questions for our profession, such as: - In the future, what will be the key skills of a senior software engineer? And for junior levels, what should be the new Computer Science curriculum? - If everyone can build features, what skills, strategies, or resources create competitive advantage for individuals and for businesses? - What are the new building blocks (libraries, SDKs, etc.) of software? How do we organize coding agents to create software? - What should a software team look like? For example, how many engineers, product managers, designers, and so on. What tooling do we need to manage their workflow? - How do AI agents change the workflow of machine learning engineers and data scientists? For example, how can we use agents to accelerate exploring data, identifying hypotheses, and testing them? I’m excited to explore these and other questions about the future of software engineering at AI Dev. I expect this to be an exciting event. Please join us! [Original text: The Batch newsletter.] ai-dev.deeplearning.ai

@elonmusk I rarely agree with you, in fact the older you've gotten, you've lost the spark that initially drew me towards you, not that you give a shit, however, you are a dead center correct on this one.

Canada is cooked

@SamanthaTaghoy @Laurieluvsmolly Finally, somebody with half a fucking brain

“Indigenous” isn’t a sexual or gender identity. Nor is black, or brown, or Asian. Or any other ethnicity. They took a distinct issue and bolted it onto the pre-existing LGBT framework, like some backwards inclusivity trophy that has no positive practical effect. I’m brown. I’m also LGBT. And I can say with absolute confidence that they are two completely different categories. You cannot simply smash them together for political points. One is about race, ethnicity, and ancestry. The other is about sexuality and gender. The suffering of Indigenous women in Canada is tragic and so very underreported. That’s what makes it all the more vital to bring awareness and attention to the issue SPECIFICALLY. Not to dilute the original focus and reduce overall visibility for the Indigenous cause. In this, Indigenous people are merely an addendum in the pantheon of letters rather than its own distinct issue. It’s not meaningful inclusion. And if they actually cared about LGBT issues and the plight of the Indigenous people, they’d be able to see how an alphabet soup acronym does nothing good.

“MMIWG2SLGBTQQIA+” The Canadian government just dropped this absolute monstrosity (and no, it isn’t satire).

@Kuenni_SK @Polymarket What friends?

@Polymarket So Trump better gets his friends under control

JUST IN: Iran announces the United States will be treated as a “direct party” to any Israeli aggression.

@chintanzalani @yrechtman What if you have a hot grown-up?

The only 4 jobs that will remain at tech companies. Credits: @yrechtman

@swmingbird @TechLayoffLover There are only 5 million software engineers in the US approximately. They figure the rest of the population will consume just fine thank you very much. And I don't find it very funny at all even if it's not true.

@TechLayoffLover I want to know what corporations will do when there is no one to consume their products because most people don’t a have a job and money to pay for services.

AMAZON PRIME VIDEO BLOODBATH 2,847 employees got the email at 6:47 AM PST "Your role has been eliminated effective immediately" Badges dead by 7:15 AM. Slack access revoked mid-sentence Senior engineers who built the entire streaming infrastructure. Gone The team that shipped 40% faster last quarter using Claude for code generation. Eliminated 847 contractors in Bangalore just got handed their prompt libraries and deployment scripts Same streaming platform. Same feature velocity expected 14 remaining Seattle engineers to "manage AI-augmented offshore delivery" The kicker: those eliminated seniors spent 8 months documenting every architectural decision into internal wikis Every code pattern. Every debugging workflow. Every performance optimization trick That documentation just became training data for the AI systems replacing them VP of Engineering sent company-wide: "This transition represents our commitment to AI-first development" Severance packages include mandatory 90-day non-compete clauses Meanwhile the Bangalore team already pushed 12 commits using the extracted knowledge base One former L7 told me: "I literally trained the AI that made me redundant" If you're at FAANG and not seeing this coming you're already dead DMs open for anyone who needs to talk

@susu_space @sama Give it a rest for God's sake

@sama When your flagship model requires users to ‘throw in every bit of context they can think of’ to get results, you’ve just described a diagnostic failure. 4o didn’t need that. #keep4o #OpenSource4o

I would like a single word for this phrase: "throw it into the maw with every bit of context I can think of".

The surprising science behind red-light therapy — and how it really works nature.com/articles/d4158…

@neethanwu Thank you. Great post.

@emanueledpt Nice. Forza Azzurri :)

You know, I hate that jobs are getting replaced but this has happened throughout history. The fact that its happening to the developer community is terrible. However, I do remember a time when third party contractors had no issue gouging me for $250k-$350k/yr. Those same "jobs" now being performed by agents. Yes, time will tell, but I do know that the really "smart" developers are the one's embracing that change and learning how to adapt.

@sama You're welcome. Nice to know that our reward is our jobs being taken away.

I have so much gratitude to people who wrote extremely complex software character-by-character. It already feels difficult to remember how much effort it really took. Thank you for getting us to this point.

@Suryanshti777 CLAUDE

🚨 Most developers are using Claude Code wrong. They open the terminal... write a prompt... and expect magic. That’s not where the real power is. Claude Code is actually a 4-layer AI engineering system: 1️⃣ CLAUDE.md → project memory Architecture, rules, commands, conventions 2️⃣ Skills → reusable knowledge packs Testing workflows, code review guides, deploy patterns 3️⃣ Hooks → deterministic guardrails Security checks, enforced rules, automation 4️⃣ Agents → specialized sub-agents Break complex tasks into parallel workflows Once you structure these properly, something interesting happens: Claude stops behaving like a chatbot. It starts behaving like a real AI dev system. Most engineers miss this because they jump straight to prompting. But the difference between average output and production-level results usually comes down to setup. If you're building with AI agents in 2026, learn the system — not just the prompt. I made a Claude Code Starter Pack explaining everything. If you want it: Follow Like + RT Comment CLAUDE I'll DM it to a few people. Future AI dev workflows won't be prompt-first. They’ll be system-first. 🚀 #AI #Claude #AIAgents #LLM #GenAI

@DominionDynamic makes $50M investment in developing a new aircraft canadianmanufacturing.com/?p=316858 I think its amazing to have these built in Canada FOR Canada by Canadians.