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.

Back again – here’s what I have.

• I am deep in the heat-hell of Las Vegas this weekend, where apparently, Las Vegas police issues cyber advisory with cybersecurity, hacker conventions in town – be careful out there…
• Speaking (tangentially) of security, remember that aUtH iS HaRd. Do better.
• I had a lot of head nods in this article on It’s Time to Do Away with “Dry Promotion from HBR
• I miss “simple” C programming. It’s easy(ish), it’s straight-forward, and it makes sense. Except, of course, when it doesn’t. What does it mean to initialize an int?
• I just re-read Good Strategy, Bad Strategy by Richard Rumelt. It says that “good” strategy addresses the most critical challenges facing an organization, while bad strategy often involves vague goals, fluffy language, and a failure to confront the core problems. Yah – that feels right.

Short and brief today – see you in a week.

I started writing today’s post and pondered for a moment how long I’ve been sharing stuff on Fridays. I’ll save you the search – it will be seven years in October.

Yet here we are again with five things that caught my interest this week.

• I’ve been playing contexto every day now. I played it a few years ago, and thought it was too hard, but came across it again, and this time I’m hooked. I got one word this week on my 15th guess with no hints, so there’s nowhere to go but down.
• Last week I linked to the results of the latest Stack Overflow survey. One thing that stood out for a lot of us who viewed the results was how many developers are frustrated by technical debt. This article on Don’t Ask Permission To Do Your Job Correctly: Avoiding The Technical Debt Trap is full of great nuggets.
• Another thing people don’t talk about in Accelerate (for more, see my latest post on The Weasel Speaks) is the little rant against maturity models. This article on Why I Dislike Maturity Models is possibly even better.
• Another head-nodder for me was this article on 7 Rules For An Effective Meeting Culture. So much great info here that is so often ignored.
• Finally – I had some fun refreshing my poor SQL skills by playing The SQL Murder Mystery.

And that’s that – see you in a week.

Often, I type this thing up before Friday and schedule it to publish. I did this last week, and failed to say anything about the fun with Crowd Strike. As annoying as the bug was/is, I’m 10x more annoyed by the internet peanut gallery all chiming in on how this bug “never would have happened on their watch”.

Anyway – here’s some stuff to read.

• Jason Arbon wrote one of the few sensible articles on the Crowd Strike madness. AI is involved, so that’s saying something. AI’s Testplan for CrowdStrike.
• The Stack Overflow Dev Survey results are out – nothing surprising, but interesting anyway.
• I’m always interested in security articles, so this article on getting deleted repos from github was worth the read…but you have to know a FULL FREAKING HASH to exploit it, so as I see it, it’s equal to “hacking” someone’s credit card after they post a picture of it on facebook.
• I don’t often link to articles from product teams, but I like the take on incident metrics from Rootly.
• I finally finished Kara Swisher’s latest book, Burn Notice. I liked it – but I think mostly because I really like Kara Swisher. It’s a bit of an auto-biography of her time in tech, and has an ample portion of good stories and personal anecdotes.

Hope you found something interesting here – see you in a week. Or this weekend if you read my stuff on The Weasel Speaks.

This has been a wild week in this timeline – but beyond the US political drama, a few other interesting things caught my interest.

• I’ve already devoured Season 3 of The Bear, but have also been really enjoying watching Killing Eve on Netflix. It’s sort of weird, but I usually like things that are sort of weird.
• Johanna Rothman wrote an insightful article on How We Plan for Ourselves vs. How We Commit for Our Organizations…and I know some folks I want to read it too.
• I found this collection of famous “flight bugs” and their root causes. I think a lot of us are aware of these, but it’s a nice recap in one place – How a Single Line of Code Brought Down a Billion Dollar Rocket
• Nice encouragement to create Small Pull Requests from the google testing blog.
• The Olympics are coming up, and we all get a chance to watch sports we would never watch otherwise. High on my list this year is synchronized diving – because I saw a video of Cook and Bacon (check out #cooknbacon) recently in a frame by frame that looked like a mirror.
  And also soccer – I will watch lots of soccer.

Another week done – have a great weekend.