unicolet.org

I've long been convinced that AI focus needs to be balanced and look at the processes upstream of sw development. There's incredible potential to improve product and strategy work and very little evidence of any effort going into it. This isn't entirely OpenAI or Anthropic's fault. Product work requires crossing organizational boundaries, querying fragmented tooling, talking to people, and continuously defining and refining strategy. None of this context is readily structured for an AI model to consume; it remains siloed, undocumented, or locked inside people's heads. Melissa Perri talks about this (and other topics) in the latest episode of her Product Thinking podcast. The most interesting part is just 3 minutes into the episode (emphasis mine): [...] "Delivery of designs and code got very fast. Delivery of good decisions became the new bottleneck." Now, I don't think this bottleneck is new. It's exactly what I talk about in the build trap. Wh...

Once again , some supremely well-thought and useful content from Oxide:  https://rfd.shared.oxide.computer/rfd/0576 This time it is about the use of LLMs within Oxide , here are my main take aways: start from values ! A phenomenal example of how values can be so much more than the vanity checklist that most companies use them for focus on the receiving end : why should I spend time reading something that the author did not think was worth enough spending the necessary time to write it? Again, goes back to their strongly writing-oriented culture and values corollary of item number 2: self review AI-generated code before asking others to review it!

Notes and thoughts on the book with one of the longest titles ever, so I'll refer to it as "HP Laserjet" from now on. BY the time I got to read it, I had been aware of this book for a while as it's not exactly new. It never really attracted my attention as it focuses on systems that I was never involved with. This changed recently (past two years) and after purchasing Industrial Devops I made the connection to this book again due to a mention in a promotional post for Industrial Devops. The TL;DR for this book is that it's worth a read: it reinforced some convictions I already had, and went a bit in more depth on others. In both the HP Laserjet book and Industrial Devops I felt the part about certifications was notably absent. Since that's usually an expensive, delicate part of physical products design, I am perplexed at the fact that it's not covered in more depth. Another remark is that some aspects that are strongly highlighted in this itrevolution n...