Good food for thought. Explains quite well the factors which impact software development.

Definitely this. The difference between a well performing team and one delivering subpar software is the basics of our trade. Minding your data models, your architectures and the engineering practices will get you a long way.

Interesting idea on how to schedule large refactorings and make sure they happen over time.

Interesting idea, why not use similar workflows than to develop software? For sure this would bring more transparency and automation, should help focusing on higher value tasks.

Understandability is indeed a very important goal. There are easy ways to improve it in a system.

Nice suggestion for talking about your work in various type of situations. Definitely worth trying to frame it like this.

Nice writeup about the benefits of homogeneity in an engineering organization. It also shows how it is a balancing act though, since you need experiments to happen in a controlled way for evolution to still happen.

Interesting list. Definitely good things to try to learn there.

It sometimes feel a bit like caricature... but there's some truth grounded into this article. The faster new software engineers internalize the proposed "truths", the better for their own mental health.

Looks like an old website, still it does a neat job of explaining how the field of knowledge representation evolved. This is nice to see a reference for beginners since I dabbled quite a bit into this years ago and it wasn't very accessible.

Definitely an excellent list to have in mind as soon as you get to engineering management. The four areas listed are the most important.

Healthy criticism of where our industry went. Engineers should exhibit curiosity on how the sausage is made, not just blindly use tools they don't understand.

Definitely this. Also with experience you tend to type less and influence others more.

Good starting point before really exploring this field deeper. Especially important here is the last section on how to use them properly. Be cautious, keep people well-being in mind at all time.

Interesting way to look at our profession... I wonder if this is the core reason of why we have a hard time to turn into a proper engineering discipline, is it even possible at all then?

This rings true to me. What a messy path to get better at our craft!

Another way to look at the fact that software engineering is a team sport. Missing this fact can lead to problems.

Nice (even though a bit long) explanation of the skills needed for a senior software engineers. Definitely a bunch of good advises in there.

For all we like to point out the software industry for blowing up estimates and budgets... it's not a unique phenomenon, civil engineering is also struggling with it. This is a good reminder.

That's nice to see a reusable framework to help organizations get started with their engineering ladder.