Coding is hard. Save mental energy, run your tests often 👇 ❌ Type, type, type, read, stare, think, type, type, read, stare... ✅ Type, run, read, type, run, read ‼️ Compiling is automated; don't compile! ❗ Slow down when test failure is unexpected; read errors, not code

Software engineers have negated every advancement in transistor density, computer architecture, compilers, and computer networking over the past 30 years.

https://t.co/bpUjSrw8AJ

"Fundamental" truths about software: - Code is liability - The more code you have, the more bugs you tend to have - The more complex a system, the more important architecture becomes - Writing maintainable code is a lot more effort than just getting it to work

What is happening right now? ChatGPT/OpenAI outage for 3 hours Heroku down for 4 hours (even their status page is down!) NVIDIA dev docs as well (runs on Heroku) Pipedrive (CRM) issues for 4 hours What else is down… and are these connected? Something started 4 hours ago…

Acquiring knowledge is easy, the hard part is knowing what to apply and when. That’s why all true learning is “on the job.” Life is lived in the arena.

There's a way of programming that I've been doing for decades and I realized recently it doesn't come naturally to many folks, so here's a pro tip: Write to the interface you'd like to have. That is, write the code you want, even if it doesn't work, then make it work.

Was in an Amish furniture store a few years ago talking to the carpenter when a notification on my watch vibrated, and I glanced at it. “What’s that,” he asked. I explained to him that my robot vacuum at home was notifying me that it was stuck. “Oh! And what can you do about

Most teams don't have a tech problem. They have a learning problem. Fast feedback, short iterations, real users. That’s how software grows. Stop polishing code in a vacuum. Ship. Learn. Improve. Repeat.

One of the most dreadful and harmful sins in software engineering is/was: class Dog extends Animal { } Reality-chasing models that were imprinted in young and open minds of students.

💡 Do you have an idea, discussion, or presentation you’d like to share spontaneously? Jump into our UNCON session! 🎤 No fixed agenda, just engaging and inspiring conversations. #adc #wdc #dpc

Will there be a part 4 too? Exciting!

🚀 Pim Elshoff will speak at #DPC25! Join 'Domain-Driven Object Modelling (part 2)' ➡️ https://t.co/xASZDmOdUu 📅 Save the date: March 18-21, 2025, in Amsterdam. #php #techtalks #coding @Pelshoff

I want this so bad 🤤

Nice, but have you tried adding the Netherlands and Spain? 😀

Looking forward to this! Hope to see you there!

Now that we have locked in the features we will deliver in the next 6 months and communicated those promises to the market, you can start scrumming. #NotMyAgile

Kids are awesome. Nothing will make you happier.

Just finished reading "Domain Modelling Made Functional" by @ScottWlaschin. As promised, my full review of the book. If I can recommend one book about understanding how to model real-world problems with Functional Programming, it'll be this book. If you want to kill two

Everything we do in software is a set of tradeoffs. The systems that we deal with and endure every day are what they are because of a set of tradeoffs that were chosen, many choices having been "get it done, then make it better." Generally, the second never happens.

"The society that separates its architects from its engineers will have its thinking done by architect astronauts and its engineering by rockstar coders."