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.
Very good set of advices in my opinion on how to prioritize product work in an organization. It very well accounts for the natural tension between sales/marketing and product/engineering.
As always, what really matters in the end is the context
Ever wondered about the details of a mechanical watch? Here is an excellent primer. Lots of attention to details.
Very interesting exploration on software engineering "facts" and what we can really do to increase quality. Unsurprisingly caring for the people seems to be the top factor.
Good exploration of what "engineer" and "engineering" means. Also helps to overcome what software people like us assume is done by the "real engineers" while in fact sometimes they can be as sloppy than us.