How the hell is it November already? I’m at home again (and can’t remember if I was home last week), but here are a few things I found worth sharing.

• Probably not news for anyone, but the latest DORA report is out. Biggest takeaway (yet not surprising at all) for me is that AI coding assistants actually hurt software delivery. I completely believe it will get better…someday.
• I don’t use it anymore, but many hundreds of lines of bug fixes and code in XBox One (and thousands more in infrastructure) were written by me using Notepad++ – which is now 21 years old!
• Jit Gosai (who has sent a number of followers to my substack) posted this week on Why We Failed at Testability (and What We Learned!)
• Nice post on feedback today on HBR – Why High Performers Need Feedback Too
• In a story that will probably be written 1000 times – Resume : AI applied for the job

That’s my list for today. Not the best, but not the worst. See you in a week.

Here we are again. It’s dark and cold in the pacific northwest, but that should only last six months, so it’s not a problem at all…

Here are some things I found interesting this week.

• A lot of us are now paying for public IPv4 addresses on some of our AWS hosted sites. I probably should just move those to IPv6, but I fear that most people won’t be able to get to them. Here’s a nice article on the state of moving to IPv6.
• This article from Human Centric Engineering – From Struggle to Insight – hits on some of the things I’ve talked about on the other blog, but also so much more. I spent 10x as much time researching some of the concepts in the article as I did reading.
• This article from Maaret on Dividing future of testing more evenly is a banger. I wish more testers were like Maaret.
  Brent – if you’re reading, tag this for the podcast.
• Adam Grant’s post today on Why Business Leaders Make Lousy Politicians is excellent. He speaks the truth both in specifics and generalities – and in his usual excellent writing style.
• Finally another one in the “why did I not know about this” (or “why did I forget this existed”) category is devdocs.io – brief documentation on …everything. There’s even an offline version.

Another week over – see y’all in November. US readers – Go. Vote.

Back again with five links of stuff you may (should??) find interesting.

• First – for United States readers only – please vote. All elections are important – this one is extremely important.
• I like the way this article answers the question, Why is my engineering team so much slower than they used to be?
• I somehow failed to notice Johanna Rothman’s ongoing writing about writing non-fiction. This post on Three Surprising (& Useful!) Learnings from My 60 Seconds of Writing WIP Experiment was a great and inspiring read
• I don’t write a lot of code anymore, but when I do, it’s almost always Python. Because I use it rarely, I forget a lot of things. While I can look them up (or use chatgpt), I find that having access to the main language pieces in a brief and condensed format is faster than looking up what I need. This Python Cheatsheet is bookmarked for me, and really handy.
• “Successful software is buggy software” is the premise of this article – Be Suspicious of Success. It’s a short and fun (and accurate).

And now you can continue your Friday. See you in a week.

It’s Friday, and I have links to share.

• Nothing new here – especially for readers of my proper blog at angryweasel.substack.com, but here’s a write up on a recent study of The Real Reasons Employees Leave Companies.
• In the not-surprised category this week is this story on Bypassing airport security via SQL injection
• I somehow lost (forgot) my favorite sun hoody – an Appalachian Gear Alpaca hoody – but AG are unfortunately out of business. I’ve finally settled on an Arms of Andes replacement – but only time will tell if it’s as good as the one I’ve lost.
• I feel like I’ve shared this link before, but it has enough recent updates that it’s worth sharing again. Short story is that cognitive load is probably the biggest factor slowing down your team of knowledge workers.
• And finally, the Engineering Managers’ Guide to Effective Annual Feedback is worth a read for any manager.

Should be something fun in there for everyone. If not – read again next week. I’ll get it right someday.

It’s been a week, for sure. Here are some things I found that I think you should know about.

• A lot of points in this post on Fear of Failure resonated with me. I’ve come to love failure over my career, but it was a difficult path.
• I listen to too many podcasts, but seem to add new podcasts faster than I remove them. The latest addition for me is the Ship It! podcast. So far, it’s been a fun listen.
• HBR hit a homerun (or beat the boss?) with this article on Why Gaming Is Good for the Workplace.
• I’m not a huge fan of Scrum – it can work, but also be all sorts of anti-agile. The author of this article on Are Scrum Masters Too Much Overhead? and I agree that it’s completely possible to “do” Scrum without Scrum Masters.
• I made a video of my September hike. It has a lot of problems. It’s long (30 minutes), the audio is inconsistent, the video is (sometimes) blurry, and various other glitches and goofs. But – it does capture what it’s like to go on a multi day hike.

And that’s all for the week – thank you again for reading.

Back again for more links that you either already knew about, or (ideally) didn’t know that you didn’t know.

• I thought this take on What LLMs for Coding Should Look Like was thoughtful and interesting. We have a long way to go in this area, and I really appreciate folks who recognize that copilot isn’t the pinnacle of computer assisted programming.
• On the heels of my latest blog post, I was happy to see this post on Self-Care Checklist for Leaders. This is almost all stuff I do – but not consistently. It’s a good reminder.
• …and leaning harder into self-reflection, I found this article on self-reflection in engineering leadership that put a lot of things into perspective for me.
• I know I’m a pointy-haired manager now, but I spent the first twenty-ish years of my career writing a shit ton of code. And I think this article stating that Most Programmers Are Actually Bad at Programming is pretty spot on. Disclaimer – it’s a Medium article and requires an account (which is a stupid choice by the author, but that’s why we all have throw away accounts).
• While I hate to use two of your three free articles on HBR in one post, this post on Why Leadership Teams Fail had me nodding my head too much. Whether you’re a leader or not, it’s worth a read.

We’re done for another week. See you in October.

Oh hey – I skipped a week. I decided almost last minute to walk the Wonderland Trail again this year. Here’s an obligatory trail pic before I get into the internet news that’s crossed my path.

• Two different people have pointed me to NotebookLM this week. I’ve played with it briefly, and it’s sort of freaking me out.
• Again, I do not share every Mike Cohn post, but this one on The Surprising Cost of Bad Estimates has a lot of good points.
• I’m always happy when an actual study with data underlines a lot of what I feel like is obvious. This article on How the Next Generation of Managers Is Using Gen AI is worth a read.
• Speaking of AI and head-nodding – nothing surprising here. AI-Generated Code is Causing Outages and Security Issues in Businesses.
• On the recommendation from a colleague, I began reading The Final Empire on my hike. I’m about half-way through, and I’m really enjoying it. I’ll likely begin a long path through the whole Mistborn series.

I’m all out of vacation days, so I’ll be back next week with more.

I am back – sort of. I spent a week in the desert with 50,000 friends, and came back with a cold. I’m mostly better now, but do have a few things to share.

• I’ve been reading a few articles about Plang – and while it’s not my favorite code, I like the idea of being able to create self-correcting code.
• Articles like this one on paying your engineers to stay, are frequent. The concept is correct, but (IMO), not for every employee. If someone is important for long term success of the company, keep them engaged, and pay them well, but other folks may be better off leaving for greener pastures.
• This article from Hazel Weakly is jam packed with ideas and concepts that teams should embrace. Home Baked Abstractions, Store Bought Implementations
• Johanna Rothman is cranking out a wonderful series on How to Calculate the Cost of Delay to Rank All the Work. Part 3 is full of great insights (but of course, feel free to read the whole thing)
• If I could have a penny for every f*%#^@ post this week on the failure of chatgpt to count the ‘R’s in the word strawberry I’d have almost a dollar! For those of you still confused and after two years still don’t have a clue how LLMs work, here’s an article to help. It’s not very good, but it’s simple and hopefully understandable.

Me and my snark will be back in another week.

It’s Friday yet again. Before I forget – no FfF next week. Will tell you about it later. Here are some things I liked on the internet this week.

• First is this article on Finding Joy as a Manager — Even on Bad Days. A lot of good nuggets here for pondering. Note that this article requires a login to hbr, but is otherwise non-paywalled.
• And even more head nodding on this article – The real reason you have 29 dev and test environments. Please read this, and while you are trying to justify that your world is different, remember that odds are that you are not actually a snow flake.
• I also enjoyed this article on Crossing The Chasm: Getting to Senior/Staff Engineer – it hits many great points on what’s needed to get to more senior levels in software roles.
• Boeing is having some issues. Still. This is an interesting article on Why Cutting Costs is Expensive: How $9/Hour Software Engineers Cost Boeing Billions that probably applies to more companies than will admit.
• Nothing to do with software, but I’m super curious to understand why we’re finding weird ugly fish in southern California.

That’s it – see you in two weeks.

It’s Friday, and it’s time to share five things I thought were interesting this week.

• I spent last weekend at DefCon (where thankfully, I did not pick up the infamous “Covid Badge”). I did, however, pick up a custom add-on to the DefCon electronic badge from my old colleague, Kevin – and it’s awesome.
  
• A lot of head-nodding in this article on How Scrum Masters (and Managers) Go Astray By Committing to Plans (and reminded me a lot of my thinking on the topic)
• IEEE has a new update to their Developer Productivity series: Developer Productivity for Humans, Part 7: Software Quality that’s worth a read,
• Buried in this story on The shortest, strangest engineering interview I’ve ever done are a lot of good ideas on interviewing – as well as a few laughs.
• Finally, I read this article on How to Plan Team Re-Organization – which I like a lot because it matches strongly with the way I like to think about these things.

That’s all for this week – I’ll try again in seven days or so.