You’ll find a whole lot of advice in today’s reading list. Advice on public speaking, changing IT culture, being resilient in a crisis, and even how to A/B test!
[blog] Long Document Summarization Techniques with Java, Langchain4J and Gemini models. Dan looks at three techniques you can use to summarize big docs with Java and your favorite LLM.
[blog] The Product Model in Traditional IT. Can you bring the product model to other types of orgs? This post looks at when it can work with traditional IT teams, when it doesn’t, and what has to change.
[blog] Programming, Fluency, and AI. Important post from Mike. If you’re not fluent in the thing you’re doing with the AI, you’re easily replaceable by AI. Don’t skip depth.
[article] The Anatomy of Slow Code Reviews. Slow reviews are a motivation killer. Google measures this closely. Here’s a post that explores the source of code review challenges.
[blog] The secrets of public speaking. Brian offers up some very good advice for those trying to improve their public speaking, or build up their confidence in the first place.
[blog] How I sent 500 million HTTP requests to 2.5 million hosts. Loved this. It’s a good answer to “what happens when I submit a web request” while also showing how you’d optimize a lot of calls.
[article] How To Be More Resilient: 6 Steps To Success When Life Gets Hard. There’s no pill or item to purchase to make you more resilient. Most of this advice from Eric relates to attitude.
[blog] BigQuery QUALIFY Clause: Towards Cleaner SQL Queries. I’ve got very dated SQL syntax knowledge. QUALIFY is not in my wheelhouse, but now I know more about it.
[article] Why Ruby on Rails Is Still Worth Your While as a Developer. Ruby is a tier-2 language at this point—viable, but not as vendor-supported or used as others—but that doesn’t mean it’s not a good language to work with.
[article] There’s a Smarter Way to A/B Test. Running A/B tests on your product can be expensive. This article proposes different assignment rules that let you run shorter trials.
[article] AI Success Depends on Tackling “Process Debt.” Don’t use AI to automate or augment bad processes. Use this technology moment to rethink processes and start fresh.
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below: