🐥 YellowDuck.be

🔗 Designing AI features that actually help users

2026-04-04T13:00:00Z

Many AI features often misfire due to poor interface design rather than flawed models. By maintaining the original workflow structure, AI can effectively translate user intent into structured data that enhances functionality without overwhelming users.

Traditional filtering interfaces can become complex and unwieldy, making it hard for users to articulate their needs. This approach proposes an intuitive AI-driven intent layer that simplifies user interactions by converting natural language into understandable filter parameters, leading to a more efficient and user-friendly experience.

Continue reading on www.mimiquate.com

#reading-list #frontend #best-practice #ai

🔗 Using ClickHouse as a webhook endpoint with HMAC verification

2026-04-04T08:00:00Z

One of the standout features in ClickHouse 25.12 is the HMAC function, which allows for message authentication with a shared key. This functionality enhances ClickHouse's ability to act as a webhook endpoint by enabling verification of incoming requests, thereby filtering out unauthorized sources.

The setup involves three primary components: a staging table initiated with the MergeTree engine, a materialized view for data validation, and a logs table to store successful entries. This method, paired with ClickHouse's architecture, ensures that only validated data is recorded, while invalid requests are rejected based on signature mismatches.

Continue reading on clickhouse.com

#reading-list #database #best-practice #http

🔗 Re-Implementing the Google Reader API in 2025

2026-04-03T17:00:00Z

In 2025, a post details the implementation of a Google Reader API-compatible service using Elixir. Despite challenges with the original API's lack of documentation, a baseline features implementation emerges, including logging in, fetching subscriptions, and managing feed item statuses.

The project illustrates the complexity of working with reverse-engineered specifications and feeds, emphasizing the need for compatibility with evolving RSS clients. It describes essential concepts and endpoints while acknowledging that the API's intricacies make achieving a complete implementation challenging yet feasible for practical use.

Continue reading on www.davd.io

#reading-list #development #tools #elixir

🔗 Thinking Elixir Podcast 297: JavaScript Joins the BEAM?

2026-04-03T13:00:00Z

News includes Quickbeam bringing a full JS runtime into the BEAM, Elixir’s type system inspiring Python’s Ruff, LiveView Debugger v0.7, Oban v2.21, and more!

Continue reading on podcast.thinkingelixir.com

#reading-list #elixir #phoenix

🔗 AI should help us produce better code

2026-04-03T08:00:00Z

Many developers fear that AI tools will compromise code quality, producing hastily written, flawed code. Instead of accepting poor output, teams should address flaws directly and choose to improve their code quality.

Technical debt often arises from trade-offs during development, and avoiding it in the first place is ideal. Coding agents, like Gemini Jules and OpenAI Codex, can effectively handle refactoring tasks and enhance the development process without disruption, ensuring higher quality outputs with minimal cost.

Continue reading on simonwillison.net

#reading-list #development #best-practice #ai

🔗 Why use static closures?

2026-04-02T13:00:00Z

In PHP, static closures are significant since they prevent unintended references to the object, enhancing memory management. By using the static keyword, developers can ensure closures do not bind to $this, allowing for earlier memory release and avoidance of memory leaks.

The upcoming PHP 8.6 update aims to automate this process with inferred static closures, optimizing performance and memory usage. This change will streamline code, making it safer by default and reducing the risk of accidental captures, further promoting efficient memory management in PHP development.

Continue reading on f2r.github.io

#reading-list #development #php #best-practice

🔗 Type systems are leaky abstractions: the case of Map.take!/2

2026-04-02T08:00:00Z

Adding a type system to Elixir showcases the limits of expressive programming languages. This article examines the proposal of Map.take!/2 and its potential to enhance type safety by raising errors for missing keys in maps.

The function aims to align with Elixir's dynamic nature while addressing type correctness. This post highlights challenges in achieving precise type signatures and suggests that utilizing macros may provide a viable solution to ensure static key validation without exposing the type system to unnecessary complexity.

Continue reading on dashbit.co

#reading-list #pattern #best-practice #elixir

🔗 How do you know if you’re a good leader?

2026-04-01T17:00:00Z

In this article, self-reflection is highlighted as a crucial aspect of effective leadership. Drawing inspiration from Abraham Lincoln's introspective writings, it emphasizes that good leaders embrace self-doubt, manage uncertainty, and seek honest feedback from multiple sources.

Effective leadership isn’t about perfection but recognizing and addressing flaws. Leaders should engage in honest self-evaluation, understanding that their effectiveness is perceived through the experiences of others, not solely their self-assessment.

Continue reading on mikefisher.substack.com

#reading-list #best-practice

🔗 Good software knows when to stop

2026-04-01T13:00:00Z

Good software excels by understanding its core purpose and knowing when to stop evolving. This article highlights that effective tools avoid unnecessary complexity and focus on what truly serves users' needs.

It emphasizes lessons from notable figures in software development, advocating for constraints as advantages. By prioritizing essential features and understanding underlying problems, developers can create better solutions and ensure their software remains impactful without overstretching.

Continue reading on ogirardot.writizzy.com

#reading-list #development #pattern #best-practice

🔗 Using systemd units for Laravel cronjobs and background processes

2026-04-01T08:00:00Z

Most Laravel applications require background processes on Linux servers. This article explains how to use systemd for tasks like cronjobs or queue workers, instead of relying on Supervisor.

Using systemd offers centralized logging, dependency management, and resource limitation benefits. The article details creating service and timer units for running Laravel processes with corresponding examples and commands for verification.

Continue reading on command-g.nl

#reading-list #laravel #best-practice #devops #linux

🔗 Weaving stories with cascading workflows

2026-03-31T13:00:00Z

The newly announced Pro v1.6 RC introduces innovative workflow features, revolutionizing how tasks are coordinated. With its user-friendly design, building workflows requires no specialized knowledge, fostering creativity and spontaneity.

The article showcases the creation of the "Fire Saga" workflow, which generates children's stories through generative AI. By employing Oban Workflows, it seamlessly manages task dependencies, making the storytelling process automated and efficient while producing delightful results.

Continue reading on oban.pro

#reading-list #pattern #elixir #announcement

🔗 Things I miss about Spring Boot after switching to Go

2026-03-31T08:00:00Z

This article compares the advantages of Spring Boot with the simplicity of Go after transitioning from one to the other. It highlights Spring Boot’s extensive features like dependency injection, built-in validations, and a mature ecosystem which greatly aid backend development, whereas Go’s minimalism promotes explicit code and lower resource usage, making deployment easier and faster.

The discussion emphasizes that Spring Boot offers solid foundational tools for complex applications, such as Spring Security and Spring Data, which facilitate quick implementation of essential backend features. Conversely, Go's concurrency model and quick startup times are beneficial for lightweight services and applications, stressing that each technology has its strengths based on the system needs.

Continue reading on sushantdhiman.dev

#reading-list #golang #development #best-practice #java

🔗 A minimalist HTTP library for Go

2026-03-30T13:00:00Z

When migrating API services from TypeScript to Go, the need for a lightweight HTTP framework that integrates with OpenAPI and offers precise middleware control becomes crucial. Zen emerges as a solution, focusing on simplicity and efficiency by utilizing Go's standard library without the bloat of complex dependencies.

The structure of Zen allows for custom middleware execution, ensuring cleaner handlers that are focused solely on business logic. By adopting a schema-first approach for OpenAPI integration, Zen guarantees a rigorous API specification that enhances developer experience while maintaining control over the API contract.

Continue reading on www.unkey.com

#reading-list #golang #development #best-practice #http

🔗 Batch inserts in SQL for large data loads

2026-03-30T08:00:00Z

Large data loads in SQL require efficient insert strategies to enhance performance. Using single row inserts can significantly slow down operations due to overhead from network latency, statement parsing, and transaction commit cycles.

Batching inserts minimizes these issues by reducing the number of statements sent to the database, leading to higher throughput. This article highlights the importance of transaction management, indexing, and how batch processing can optimize data loading strategies.

Continue reading on freedium-mirror.cfd

#reading-list #database #best-practice #sql

🔗 Why I stopped using AI code editors

2026-03-29T13:00:00Z

TL;DR: I chose to make using AI a manual action, because I felt the slow loss of competence over time when I relied on it, and I recommend everyone to be cautious with making AI a key part of their workflow.

In late 2022, I used AI tools for the first time, even before the first version of ChatGPT. In 2023, I started using AI-based tools in my development workflow. Initially, I was super impressed with the capabilities of these LLMs. The fact that I could just copy and paste obscure compiler errors along with the C++ source code, and be told where the error is caused felt like magic.

Once GitHub Copilot started becoming more and more powerful, I started using it more and more. I used various other LLM integrations right in my editor. Using AI was part of my workflow.

In late 2024 I removed all LLM integrations from my code editors. I still use LLMs occasionally and I do think AI can be used in a way that is very beneficial for many programmers. So then why don’t I use AI-powered code editing tools?

Continue reading on lucianonooijen.com

#reading-list #development #tools #ai #github

🔗 Your agent framework is just a bad clone of Elixir: concurrency lessons from telecom to AI

2026-03-29T08:00:00Z

Recently, José Valim published "Why Elixir is the Best Language for AI", citing a Tencent study showing Elixir achieved the highest LLM code completion rate across 20 languages. Claude Opus 4 scored 80.3% on Elixir problems versus 74.9% for C#, the next-best performer.

But there's a deeper argument than "LLMs write good Elixir." It's this: the actor model that Erlang introduced in 1986 is the agent model that AI is rediscovering in 2026. Every pattern the Python AI ecosystem is building (isolated state, message passing, supervision hierarchies, fault recovery) already exists in the BEAM virtual machine. And it's been running telecom switches, WhatsApp, and Discord at scale for decades.

I've been building agentic commerce infrastructure at New Generation. Before that, I shipped a full AI stack serving more than 3 million merchants at a unicorn Brazilian fintech. Both systems run on Elixir. Here's why that's not a hipster language choice. It's an architectural inevitability.

A note on terminology: Throughout this post I refer to "the BEAM." BEAM is the virtual machine that runs both Erlang and Elixir code, similar to how the JVM runs both Java and Kotlin. Erlang (1986) created the VM and the concurrency model. Elixir (2012) is a modern language built on top of it with better ergonomics. When I say "BEAM," I mean the runtime and its properties. When I say "Elixir," I mean the language we write.

Continue reading on georgeguimaraes.com

#reading-list #javascript #typescript #python #ai #elixir

🔗 Easily connecting to BEAM nodes in Kubernetes with kubectl-beam

2026-03-28T14:00:00Z

A kubectl plugin that makes connecting to Erlang and Elixir nodes running in Kubernetes pods as easy as running a single command---with full TTY support and Observer GUI.

Debugging BEAM applications in Kubernetes has always been more painful than it should be. You know the drill: your Phoenix app is misbehaving in production, you need to inspect some process state, maybe run a few commands in an IEx shell, or fire up Observer to see what’s going on. Simple enough on your local machine, right? But in Kubernetes, you end up manually port-forwarding EPMD, figuring out the dynamic distribution port, wrestling with DNS resolution, and praying your terminal doesn’t get mangled in the process.

I’ve done this dance too many times—enough to finally build something that handles all the tedious bits automatically. That’s why I created kubectl-beam, a kubectl plugin that connects you to BEAM nodes running in Kubernetes pods with a single command.

Continue reading on dairon.org

#reading-list #elixir #phoenix #devops #terminal #kubernetes

🔗 Nobody gets promoted for simplicity

2026-03-28T09:00:00Z

“Simplicity is a great virtue, but it requires hard work to achieve and education to appreciate. And to make matters worse, complexity sells better.”
— Edsger Dijkstra

I think there’s something quietly screwing up a lot of engineering teams. In interviews, in promotion packets, in design reviews: the engineer who overbuilds gets a compelling narrative, but the one who ships the simplest thing that works gets… nothing.

This isn’t intentional, of course. Nobody sits down and says, “let’s make sure the people who over-engineer things get promoted!” But that’s what can happen (and it has been, over and over again) when companies evaluate work incorrectly.

Continue reading on terriblesoftware.org

#reading-list #development

🔗 Pausing traffic and retrying in Caddy

2026-03-27T14:00:00Z

A pattern I really like for zero-downtime deploys is the ability to "pause" HTTP traffic at the load balancer, such that incoming requests from browsers appear to take a few extra seconds to return, but under the hood they've actually been held in a queue while a backend server is swapped out or upgraded in some way.

Continue reading on github.com

#reading-list #pattern #http

🔗 Building a weather agent with Jido

2026-03-27T09:00:00Z

We’re going to build a simple agent that can answer natural language questions about the weather. It will understand the request, use a tool to fetch weather data, and then provide a response, all orchestrated by Jido and an LLM.

Continue reading on agentjido.xyz

#reading-list #development #ai #elixir

🔗 Row locks with joins can produce surprising results in PostgreSQL

2026-03-26T18:00:00Z

Here's a database riddle: you have two tables with data connected by a foreign key. The foreign key field is set as not null and the constraint is valid and enforced. You execute a query that joins these two tables and you get no results! How is that possible? We thought it wasn't possible, but a recent incident revealed an edge case we never thought about.

In this article I show how under some circumstances row locks with joins can produce surprising results, and suggest ways to prevent it.

Continue reading on hakibenita.com

#reading-list #database #postgresql #sql

🔗 The instance is up. or is it? Health checking in client-side vs server-side load balancing

2026-03-26T14:00:00Z

A service reports healthy. The load balancer believes it. A request lands on it and times out. Another follows. Then ten more. By the time the system reacts, hundreds of requests have drained into a broken instance while users stared at a spinner.

Health checking sounds simple: ask if something is alive, stop sending traffic if it isn’t. In practice, the mechanism behind that check, and who performs it, determines how fast your system detects failure, how accurately it responds, and how much of that complexity leaks into your application code.

The answer is fundamentally different depending on where load balancing lives: in a central proxy, or in the client itself.

Continue reading on singh-sanjay.com

#reading-list #http

🔗 The illusion of speed: When AI builds a Phoenix app in 30 minutes

2026-03-26T09:00:00Z

Before talking about how to work with AI in a structured way, let me show you why so many people fall in love with vibe coding.

Bruce asked Claude to build a complete application using Phoenix LiveView: Conway’s Game of Life, with controls, pattern library, and interface. It took 30 minutes from idea to working code.

Gliders moving across the screen, speed controls, randomization, ready-made pattern library, clean interface. Worked on the first try.

Continue reading on grox.io

#reading-list #ai #elixir #phoenix

🔗 Git bisect for bug tracking

2026-03-25T14:00:00Z

The bisect command can be used to traverse your commit history to find where an unwaned behavior was introduced. If your current commit is broken, and you have a previous working commit, but there's lots of commits in between, bisect will help you navigate those commits in between to locate which commit added the unwanted behavior.

check out these docs

Continue reading on til.hashrocket.com

#reading-list #tools #git

🔗 Supercharging Claude code with the right (CLI) tools

2026-03-25T09:00:00Z

I’ve been using Claude Code quite a bit lately, and I got curious – what if I asked it directly which tools would make it more productive? Not the usual suspects like ripgrep, jq or git, but tools it wishes it had access to, tools that would genuinely extend its capabilities.

So I did exactly that. I asked Claude Code: “What are the most valuable CLI tools I could install for you, outside of the ones you already have?” The answer was surprisingly thoughtful and insightful, so I figured I’d share it here along with my own commentary. Here are 10 tools, ranked by how useful they’d be for an AI coding assistant.

Continue reading on batsov.com

#reading-list #tools #ai #terminal