The Future of Software Development is Software Developers - or why we won't be replaced by #ai anytime soon - by Jason Gorman https://t.co/MmW7zXfHIG

Me in 2005: let me code this whole system over the weekend. Me in 2015: let me glue these open-source projects together to confirm if the idea is worth doing. Me in 2025: let me spend a couple of hours creating a spreadsheet so I don't have to write the app.

Me in 2005: let me code this whole system over the weekend. Me in 2015: let me glue these open-source projects together to confirm if the idea is worth doing. Me in 2025: let me spend a couple of hours creating a spreadsheet so I don't have to write the app.

There is no single part of Scrum that is bad. It's the inseparableness of and strict adherence to all the parts of Scrum that is bad. By definition, you can't separate any parts of Scrum, as in use a subset of Scrum linked with common sense, and still call it Scrum. Not being

WAŻNE❗️POLICJA ZNOWU ZAATAKOWAŁA https://t.co/MRKiWLn4va❗️PODAJ DALEJ 🔁 Sielanka, w której Policja - jak w normalnym państwie - pomaga mieszkańcom i reaguje na zgłoszenia, nie mogła trwać długo. Dziś wprowadzono limit liczby zgłoszeń z https://t.co/dcTfxP7rn8, które w ciągu

The day hasn't passed yet and I think Ghostty will also replace tmux for me.

/me installs ghostty

I still can't believe I can just play this game on my mobile.

"If you can’t have those conversations, stop. You can’t do BDD. You might be able to write some scenarios or some acceptance tests, but they’re likely to be brittle and it’s unlikely that anyone will be interested. Here’s why." https://t.co/KftrDSI3gl

. @lunivore 's blog is such a great #BDD resource. "Don’t start with BDD, and definitely don’t start with the tools." "Start by having conversations, engaging both testers and business stakeholders or their proxies (analysts are good here)."

"There’s always more to build than we have time or resources to build—always." If you somehow started to build 10x quicker, would you fire 9/10 of your developers or would you rather start building 10x more? 🤔

- Your job isn’t to build more software faster: it’s to maximize the outcome and impact you get from what you choose to build.

- Stories aren’t the requirements; they’re discussions about solving problems for our organization, our customers, and our users that lead to agreements on what to build.

- Stories aren’t a written form of requirements; telling stories through collaboration with words and pictures is a mechanism that builds shared understanding.

"There’s always more to build than we have time or resources to build—always." "Minimize output, and maximize outcome and impact." "Remember: at the end of the day, your job isn’t to get the requirements right—your job is to change the world."

"Good story conversations are about who and why, not just what."

Impact. Impact is a longer-term consequence of good outcomes. Outcomes are often something you can observe right away after delivery. The impact takes longer.

Output vs Outcome Output is what happens between the idea and delivery. It's what we build. Output isn't the point, an outcome is. Outcome can be measured by looking at what people do differently to reach their goals as a consequence of what we've built.

"To help remember, photograph and shoot short videos of the results of your conversations."

Documents. "Good documents are like vacation photos" "But, remember, what’s most important isn’t what’s written down—it’s what we remember when we read it. That’s the vacation photo factor."