/Thought Piece

Monitoring Is A Pain

- Mat Duggan tl;dr: “I have a confession. Despite having been hired multiple times in part due to my experience with monitoring platforms, I have come to hate monitoring. Monitoring and observability tools commit the cardinal sin of tricking people into thinking this is an easy problem. It is very simple to monitor a small application or service. Almost none of those approaches scale.” The article suggests several recommendations for improving the monitoring process.

featured in #430

Generating Code Without Generating Technical Debt?

- Reka Horvath tl;dr: GPT and other large language models can produce huge volumes of code quickly. This allows for faster prototyping and iterative development, trying out multiple solutions. But it can also leave us with a bigger amount of mess code to maintain… This article explores several ways how to improve the code generated by these powerful tools and how to fit it into your project.

featured in #429

The Rise Of The AI Engineer

tl;dr: “Every startup I know of has some kind of discuss-ai Slack channel. Those channels will turn from informal groups into formal teams, as Amplitude, Replit and Notion have done. The thousands of Software Engineers working on productionizing AI APIs and OSS models, whether on company time or on nights and weekends, in corporate Slacks or indie Discords, will professionalize and converge on a title - the AI Engineer. This will be the highest-demand eng job of the decade.”

featured in #428

Plain Text Journaling

tl;dr: “I cobbled together a journaling system with {neo,}vim, coreutils and dateutils. This system is loosely based on Ryder Caroll’s Bullet Journal method.” The author gives us a demo.

featured in #424

Tech Debt Metaphor Maximalism

- Avery Pennarun tl;dr: Tech debt is compared to financial debt in a blog post, highlighting the distinction between high-interest shortcuts and low-interest strategic decisions, while emphasizing the importance of managing debt within defined limits and evaluating its impact on the project's sustainability.

featured in #421

AI Means More Developers

- Matt Rickard tl;dr: “Software trends towards higher abstractions. You can do more with less. Not only do developers never need to touch hardware anymore, but they might not even need to interface with public cloud providers and might opt to use developer-friendly middlemen. That means less code to write. Less code to write means a narrower range of skills needed to get started. This lowers the barrier to entry.”

featured in #421

All The Hard Stuff Nobody Talks About When Building Products With LLMs

- Phillip Carter tl;dr: (1) Context windows are a challenge with no complete solution. (2) LLMs are slow and chaining is a nonstarter. (3) Prompt engineering is weird and has few best practices. (4) Correctness and usefulness can be at odds. (5) Prompt injection is an unsolved problem.

featured in #418

Lua: The Little Language That Could

- Matt Blewitt tl;dr: “Lua is probably my favourite “little language” — a language designed to have low cognitive load, and be easy to learn and use. It’s embedded in a lot of software, such as Redis. It’s also used as a scripting language in games such as World of Warcraft and Roblox via Luau. This post is a brief love letter to the language, with some examples of why I like it so much.”

featured in #418

The Case Against Relying Solely On DRY

- Ashley Peacock tl;dr: Instead of being applied when needed, Ashley believes DRY is thrown around anytime duplication is spotted, and this leads to worse code in the long run. Ashley walks through why duplication is not the root of all evil, and why it’s perfectly fine to repeat yourself sometimes.

featured in #398

No-Code Has No Future In A World Of AI

- Ravi Parikh tl;dr: Ravi Parikh, CEO of Airplane, discusses how AI-driven software development will dwarf no-code tools' capabilities and eventually make no-code obsolete.

featured in #394