About Contact me Presentations rss feed  rss

Interesting learning resources - March 2024

11 Mar 2024

In this post we look at dealing with ambiguity, a high level of what does OODA loops mean, getting better at debugging , and more.

I wasn’t sure how to approach posts from newsletters (some of them behind paywalls). My current standpoint is that if I am able to archive it, then I will include them.

Being a PM at Microsoft: Thriving in ambiguity - By Matthew Roche

This quote is why I wanted to share this article here

Running in the dark with a flashlight

… and the following is another good quote

Keep taking action even in uncertainty

The article main focus is on goals. I enjoyed the examples on how to “eliminate ambiguity” by analysing how aligned are the stakeholders.

Reading about the focus on goals also raises a few questions

The videos are pretty interesting too and it’s a nice touch that they are not just hosted in youtube. Extra internet point to you

What can air combat teach us about software project failure? by Jade Rubick

If you do programming for a living, at some point someone mentioned OODA loops near this is a handy reference to it.

Not only does the post does a high level of what OODA loops are but also it helps with reasoning about why small feedback loops (and the correlated corrections) are more likely to lead to success.

Linux debugging tools you’ll love by Julia Evans

If you never came across these zines by Julia Evans aka b0rk I think this might make your day. If you want to learn the basics and also in depth about something, these zines are just so so so good, I am linking to a debugging one because I really liked it but all of the ones I read are brilliant

(Almost) Every infrastructure decision I endorse or regret after 4 years running infrastructure at a startup by Jack

Nice write up with very concrete reasoning. No need to agree with all the points, however great to learn from other’s experience and see how the decisions matured.

How we evaluated the impact of GitHub Copilot for 3 months by Tobias Deekens

It’s what it says in the tin, and it’s valuable to learn from the shared experiences of others. A great addition to this post would be if the surveys included information broken down by programming language and framework. At least in my experience the value you get of CoPilot depends a lot on that.

EDIT: I reached out to the author of this post and it turns out that CoPilot doesn’t break down metrics by programming language.

5 Mistakes That Made My Documents Terrible by Raviraj Achar

This post caught my eye because I could easily relate to the journey the author had experienced. And from there he goes of to suggest how to address the problems. The common problems are about mindset, understanding who you are writing for, clarity of message (where clarity includes brevity) and using visual aids when needed.

Resources for later in the week

Categories:   ambiguity   writing   OODA-loops   debugging-tools   github   copilot

Want to discuss this post? the best place right now for me is mastodon, please message me with your comment or question.