What I'm Consuming

Everyone is a Developer (or Builder)

In Scrum, there are just three roles. There is the Product Owner, Scrum Master, and Developer. Developers are the doers of the scrum team. It doesn’t matter if you are working on design, programming, or architecture. No matter what the actual work is, doers are still developers.

The great thing about AI, or maybe the worst thing about AI, depending on your viewing is this: AI is making everyone into developers. There is still going to be specialization, and backlog items are going to be assigned. But in this new world, it doesn’t matter if you went to school and got a CS degree, or if you’re an MBA — you’re still a developer. That’s because everyone has within their grasp the ability to do the job, even if it is poorly.

Post by @carnage4life@mas.to
View on Mastodon


Want to speed up? Teams that embrace this dynamic are going to go further than teams that don’t. The less siloing and gatekeeping of functions, the more software will be produced, and the faster the teams will get. Reserving some types of work for specific people will slow things down. And if you see someone else doing something badly, and something you’re expert in, you can always pitch in and fix it or improve it.

Product Management ISN'T Dead

This article on Substack1 was sent to me by Nate — thanks!

Product Managers are suddenly essential. I agree with most of the article, but I’d add that successful Product Managers focus on the business model. Everyone needs product management, but given their wide range of responsibilities, it’s better to hire someone experienced than try to handle it yourself.

Also, isn’t that true for most fields? Sure, I can design with AI, but it often looks like AI design. I can do QA with AI, but I’ll have to accept its results, which aren’t always perfect. Or I can have AI write code, which is helpful but still needs supervision.

The big issue is that all of these pronouncements about specific careers, whether it is from one company eliminating a function or a big reorganization at a tech giant, is leading to massive shifts in sentiment and job activity. We’ve never been in a more precarious and risky place when it comes to careers.

  1. I don’t usually read Substack because they host Nazis, but this one was sent to me. ↩

PyData Boston February 2026 Recap

A monochrome shot captures a focused tech presentation. A man in a hoodie points at a large screen displaying code, while an engaged audience with laptops watches from tables in the foreground. The clean, modern room suggests a dynamic learning environment.

My Takeaways from the PyData Meetup in Boston

A few nights ago, I attended the PyData Meetup in Boston and left with some valuable insights:

1. Rethinking the “You’re an Expert in…” Prompt

One of my key takeaways was the shift away from using the “you’re an expert in…” prompt. While it used to be useful, the evolution of LLMs has made it unnecessary in many situations. I’ve stopped using it in most of my interactions, and it was great to hear something similar from experts.

2. Exploring Cursor’s Features

The meetup included a comprehensive introduction to Cursor’s less obvious features, such as rules, skills, and commands. I’m excited to dive deeper into them.

3. Breaking Down AI-Assisted Coding Goals

Many developers struggle with AI-assisted coding because they are expecting it to take on a lot of scope. The consensus was that trying to accomplish too much at once yields poor results. Instead, breaking down goals into smaller, manageable steps and planning them out beforehand leads to better results.

My biggest takeaway from the meetup was that AI-assisted coding has come a long way. If you’re a developer who tried it six months or a year ago and was disappointed by the results, I recommend giving it another shot.

It was a great night and I enjoyed reconnecting with others in the community. And also to be updated on the latest advancements in AI-assisted coding.