🐥 YellowDuck.be

🔗 Comprehension debt - the hidden cost of AI generated code

2026-04-19T13:00:00Z

Comprehension debt is the hidden cost to human intelligence and memory resulting from excessive reliance on AI and automation. For engineers, it applies most to agentic engineering.

There’s a cost that doesn’t show up in your velocity metrics when teams go deep on AI coding tools. Especially when its tedious to review all the code the AI generates. This cost accumulates steadily, and eventually it has to be paid - with interest. It’s called comprehension debt or cognitive debt.

Comprehension debt is the growing gap between how much code exists in your system and how much of it any human being genuinely understands.

Unlike technical debt, which announces itself through mounting friction - slow builds, tangled dependencies, the creeping dread every time you touch that one module - comprehension debt breeds false confidence. The codebase looks clean. The tests are green. The reckoning arrives quietly, usually at the worst possible moment.

Continue reading on addyosmani.com

#reading-list #golang #tools #ai

🔗 11 software development best practices in 2026

2026-04-19T08:00:00Z

Discover essential software development best practices to enhance code quality, efficiency, and maintenance, featuring principles like DRY and YAGNI.

Best Practices for Software Development in 2026

Software development is a constantly evolving field, and adopting the right practices can significantly improve the quality and maintainability of your code. Here are some of the best practices that you should implement in your software development processes in 2026:

DRY (Don't Repeat Yourself):
Reducing repetition within your codebase enhances clarity and minimizes maintenance efforts.

YAGNI (You Aren't Gonna Need It):
Avoid implementing features until they are necessary. This practice helps in keeping the codebase clean and manageable.

KISS (Keep It Simple, Stupid):
Aim for simplicity in your designs and implementations. Overcomplication can lead to more bugs and harder maintenance.

Continue reading on www.netguru.com

#reading-list #development

🔗 Tower 16 for Mac (Beta) — Introducing AI commits ✨

2026-04-18T17:00:00Z

Say goodbye to tedious commit messages! Tower 16 for Mac introduces AI Commits, allowing users to generate commit messages and descriptions effortlessly using AI right from their Git client. With the new Generate button in the Commit Composing area, I can stage changes and click to get instant suggestions for commit messages. Tower 16 also supports two AI providers—Claude Code and OpenAI's Codex—which I can configure in the new AI tab under settings. I can even create custom prompt presets for my team's specific commit conventions, ensuring consistency and clarity. The update includes handy features in the Working Copy view, and improvements such as clickable URLs in the License View and better performance with large branches. Overall, this beta makes my Git workflow smoother and more efficient!

Continue reading on www.git-tower.com

#reading-list #tools #ai #announcement #git #mac

🔗 Production query plans without production data

2026-04-18T13:00:00Z

This article examines how PostgreSQL 18 introduces enhancements for managing optimizer statistics without the need for production data. The features pg_restore_relation_stats and pg_restore_attribute_stats enable users to inject statistics directly into the catalog tables, facilitating the creation of test environments that mimic production systems in terms of query planning and execution.

By using these functions, developers can export statistics from a production database and reproduce them in development or testing contexts, improving the accuracy of performance assessments. This capability addresses the challenges posed by differing row configurations in production and CI environments, allowing for reliable query plan validations and potential optimizations based on real-world data distributions.

Continue reading on boringsql.com

#reading-list #development #database #best-practice #postgresql #testing

🔗 mickamy/sql-tap: Watch SQL traffic in real-time with a TUI

2026-04-18T08:00:00Z

sql-tap is a real-time SQL traffic viewer that functions as a proxy daemon and terminal user interface (TUI). It captures and displays queries from PostgreSQL, MySQL, or TiDB without requiring application code changes, offering features like query inspection and EXPLAIN commands.

Installation is straightforward across different platforms, including Homebrew, Docker, and building from source. Users can start the proxy daemon and connect their applications seamlessly to view live SQL traffic through the TUI or web interface, with options for real-time monitoring of N+1 and slow queries.

Continue reading on github.com

#reading-list #database #tools #devops #sql #terminal

🔗 SFQ: Simple, Stateless, Stochastic Fairness

2026-04-17T17:00:00Z

Stochastic Fairness Queuing (SFQ) offers a method to effectively manage workloads in distributed systems by utilizing a fixed set of queues. By hashing customer identifiers to this limited number of queues, SFQ mitigates the negative impact of noisy neighbors while maintaining O(1) performance for both enqueueing and dequeueing requests.

The proposal combines SFQ with shuffle sharding and a best-of-two algorithm to optimize request handling further. This approach enhances customer isolation from noisy neighbors, ensuring that service degradation does not persist, even during resource contention.

Continue reading on brooker.co.za

#reading-list #pattern #best-practice

🔗 AI and the Ship of Theseus

2026-04-17T13:00:00Z

Because code gets cheaper and cheaper to write, re-implementations are becoming more common. This post highlights considerations regarding copyright implications when AI-generated code is involved, especially concerning licensing like GPL versus more permissive options.

The emergence of AI-generated code may lead to many software projects reappearing under different licenses, raising questions about copyrights and authorship. This situation may ignite renewed debates around copyleft and permissive licenses, with advocates stressing the value of open sharing against those who prioritize licensing enforcement.

Continue reading on lucumr.pocoo.org

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

🔗 AI code review tools: what works, what doesn't, and how to set it up

2026-04-17T08:00:00Z

AI code review tools excel at catching mechanical issues like security patterns, formatting violations, test coverage gaps, and code smells that humans miss when fatigued. However, they consistently fail at architectural decisions, business logic validation, and recognizing when correct code represents the wrong approach.

The practical setup involves choosing a tool based on infrastructure constraints, configuring it to reduce noise, and establishing a workflow where AI reviews first to handle surface-level checks. Human reviewers then focus on depth—architecture, business logic, and strategic fit—making reviews faster and more focused rather than replacing human judgment entirely.

Continue reading on madewithlove.com

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

🔗 Writing a PDF parser in PHP from scratch

2026-04-16T17:00:00Z

PDFs can be notoriously complex, presenting significant challenges in extracting data. Driven by my previous struggles with existing libraries like smalot/pdfparser, I set out to create a more robust solution. After two years of intermittent development, I launched the prinsfrank/pdfparser, aiming for a PHP library that allowed straightforward contributions and full typing for objects. Initially tough, the project gained momentum when I re-engaged in late 2024, culminating in the release of version 2.0, which now includes features like positional context and image extraction. I'm even tackling encrypted PDFs next! This journey underscores the intricacies of PDF parsing and the ongoing demand for better solutions in this space.

Continue reading on prinsfrank.nl

#reading-list #pdf #development #php

🔗 Think of Pavlov

2026-04-16T13:00:00Z

Every interaction functions as a conditioning event that shapes how others perceive working with you. People treat most encounters as repeat games, meaning each conversation trains colleagues on what behavior to expect and whether they should bring problems to you in the future. Consistent tone, timing, and feedback patterns determine reputation and effectiveness far more than any single moment of being right. Hard feedback delivered skillfully can motivate, but the cumulative effect of how you respond—whether with curiosity, dismissal, or excessive solving—establishes the feedback loops that define your influence.

Continue reading on boz.com

#reading-list

🔗 Google Sheets integration: Elixir data management guide

2026-04-16T08:00:00Z

This article presents a practical guide to integrating Google Sheets with an Elixir application using the Phoenix Framework. It outlines the steps to extract, organize, and analyze data from a Google Sheets spreadsheet for attendance and ship usage statistics in a gaming context.

By implementing Google APIs for both Sheets and Drive, the post provides insights into creating a seamless data management experience. Detailed snippets of Elixir code are provided to illustrate the interaction with Google Sheets, data manipulation, and how to set up a Phoenix application for real-world applications.

Continue reading on www.curiosum.com

#reading-list #development #database #elixir #phoenix

🔗 Thinking Elixir Podcast 299: Don't Paste That Into Your Terminal

2026-04-15T17:00:00Z

The EEF needs your support for a major security grant, Hex.pm completes its first security audit, José Valim drops a massive Tidewave update, and we discuss the ClickFix supply chain attack that hit Axios, and more!

Continue reading on podcast.thinkingelixir.com

#reading-list #elixir #phoenix

🔗 The 2-minute Claude code upgrade you're probably missing: LSP

2026-04-15T13:00:00Z

Right now, every Claude Code user is running without LSP. This means searching for definitions is akin to using grep, leading to delays and inaccuracies in large codebases. Enabling LSP changes everything; with it, queries like asking where processPayment is defined return precise results in 50 milliseconds, compared to 30-60 seconds without it. LSP separates language intelligence from the editor, making it more efficient. It opens up advanced capabilities such as automatic error correction and precise code navigation, eliminating the frustration of traditional text searches. Enabling it is straightforward and takes only a couple of minutes. You add a flag in your settings and install the relevant language server binaries. This transforms how you interact with your code, enhancing accuracy and speed significantly.

Continue reading on karanbansal.in

#reading-list #development #tools #best-practice

🔗 How to optimize SonarQube for reviewing AI-generated code

2026-04-15T08:00:00Z

AI-generated code can introduce various quality issues, including technical debt and security vulnerabilities. This post emphasizes the need for a stricter quality gate and quality profile tailored for AI-generated code within SonarQube Cloud.

The recommended approach includes designing a custom quality gate that increases coverage requirements and limits code duplication. Additionally, establishing a custom quality profile will help maintain code readability and enforce stricter validation rules, ensuring that AI-generated outputs meet higher standards.

Continue reading on www.sonarsource.com

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

🔗 The part of the SDLC nobody talks about, and many companies don’t do properly

2026-04-14T17:00:00Z

The most overlooked part of the software development lifecycle (SDLC) is decommissioning. Many companies neglect or mishandle this phase, leading to significant costs and inefficiencies. For instance, zombie resources like forgotten databases or unused virtual machines waste an estimated 30% of cloud spending. Despite the common belief that removing resources doesn’t add value, failing to do so increases financial, operational, and security burdens over time. Proper decommissioning requires a clear process with a checklist to ensure no resources are left behind. This includes reviewing service usage, notifying teams, disabling alerts, and thoroughly cleaning up all related components. Ignoring this crucial phase creates unnecessary costs and complicates infrastructure management.

Continue reading on blog.danskingdom.com

#reading-list #development #best-practice #devops #sysadmin

🔗 AshTypescript Typed Channels

2026-04-14T13:00:00Z

AshTypescript enables the generation of typed TypeScript event subscriptions using Ash PubSub's publications. This functionality allows developers to handle server-pushed events in a type-safe manner over Phoenix channels, enhancing the client-side experience with well-defined payload types.

To implement typed channels, developers can utilize AshTypescript.TypedChannel for applications that push events to clients. Using transformation functions and specifying event types in the channel module, the TypeScript types are generated, which promotes a seamless integration between the server and the frontend application.

Continue reading on hexdocs.pm

#reading-list #typescript #frontend #elixir #phoenix #announcement

🔗 Spec-driven development: From vibe coding to structured development

2026-04-14T08:00:00Z

Spec-driven development (SDD) offers a structured approach to coding, focusing on writing specifications before coding starts. This method counteracts the limitations of vibe coding by ensuring that the AI has a solid foundation to work from, minimizing bugs and architectural drift.

Tools like GitHub's Spec Kit, Amazon's Kiro, and Fission AI's OpenSpec enhance this process by formalizing the workflow and generating artifacts to guide development. By emphasizing a persistent specification that serves as the source of truth, SDD allows for more coherent and compliant code output, especially in complex environments like payments systems.

Continue reading on zarar.dev

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

🔗 18 months of code, gone. Here's what we learned.

2026-04-13T17:00:00Z

We developed this product for over 1.5 years, closed clients left right and center, and now we're throwing everything away.

In case you don't know me (or Autonoma), we're no strangers to pivots. Funnily enough, we pivoted like 4 times already (enterprise search, documentation generation, coding agent, QA testing platform). The reasons are beyond the scope of this article. In all cases, we knew bugs were painful, we just didn’t know what was the best way of solving the problem.

On our last pivot, we actually started getting customers and raised a round from one of the biggest names in the industry. We hired a team of 14 (as I’m writing this article) and started closing clients left right and center. So why would we take such a drastic decision over something that’s working for many customers? Well, many reasons. That’s why I’m writing this article.

Continue reading on tompiagg.io

#reading-list #development #testing

🔗 Fixing full recompiles of Elixir caused by Claude code

2026-04-13T13:00:00Z

At work, many of us were having a persistent issue where our Elixir app was having to do a full recompile very frequently, despite not having touched the dependencies, mix.exs, and so on. We were finally able to narrow it down to affecting the people who use Claude Code and Mise together (it may affect ASDF users as well?).

Continue reading on tylerayoung.com

#reading-list #elixir #phoenix

🔗 Slow down to speed up

2026-04-13T08:00:00Z

In today's AI-driven world, there's a powerful counterintuitive principle: slowing down can lead to faster outcomes. This isn't just philosophical fluff; it's based on Daniel Kahneman’s System 1 and System 2 thinking. While AI excels at rapid execution and pattern matching, the crucial first step of clearly defining what to build remains a distinctly human task. Flawed assumptions propagate quickly in the age of fast prototyping, leading to worse outcomes and accumulating technical debt. I learned that deliberate slowness, whether through writing down requirements or running pre-mortems, allows for better decision-making before launching into rapid development. AI can enhance both speed and thoroughness, but I have to know when to harness each effectively. Ultimately, embracing this balance is essential for sustainable innovation in any tech environment.

Continue reading on www.theengineeringmanager.com

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

🔗 Claude Skill incoming! Generating Postman collections with AI

2026-04-12T17:00:00Z

This article discusses the introduction of a Claude Skill designed to facilitate the generation of Postman collections from Rails controllers. This tool automates the documentation process, ensuring that QA teams can quickly access up-to-date API documentation without extensive manual effort.

The skill scans existing Rails controllers for essential data such as routes, actions, and parameters, producing a comprehensive Postman collection in JSON format. While there are limitations regarding its accuracy, particularly without RSpec specifications, the skill effectively reduces the burden of manual documentation in fast-paced development environments.

Continue reading on thoughtbot.com

#reading-list #development #tools #ai #announcement

🔗 Good CTE, bad CTE

2026-04-12T13:00:00Z

CTEs (Common Table Expressions) are a popular feature among SQL developers, often used to simplify complex queries. However, their actual performance and optimizations have significantly changed in PostgreSQL 12, shifting from always being treated as optimization fences to more flexible handling of CTEs.

PostgreSQL 12 introduced several optimizations regarding CTE handling, allowing non-recursive, side-effect-free CTEs to be inlined and treated as subqueries. This change improves query performance by enabling predicate pushdown and better index usage, while also providing control over CTE materialization when needed for specific use cases.

Continue reading on boringsql.com

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

🔗 Building a blog with Elixir and Phoenix

2026-04-12T08:00:00Z

This post describes building a blog using Elixir and Phoenix with server-side rendering, NimblePublisher for markdown processing, and Tailwind CSS for styling. The setup uses no database, compiles all posts at build time, and achieves fast performance through pre-compiled HTML generation.

The blog runs on a self-hosted Dokploy instance on Hetzner with bunny.net as a CDN, featuring automated CI/CD through GitHub Actions and rolling deploys that complete in 30 seconds. Additional features include RSS feeds, XML sitemaps, blog post redirects, and comprehensive SEO metadata with Open Graph and Twitter Card tags.

Continue reading on jola.dev

#reading-list #frontend #best-practice #elixir #phoenix #devops

🔗 Two soups, two cookies

2026-04-11T17:00:00Z

Is the difference between something that works and something that feels right just about the ingredients? I discovered this when I made two soups using the exact same ingredients. The first soup was boiled conventionally, resulting in bland flavors. The second was roasted, allowing the natural sweetness of the veggies to emerge. This simple change in process transformed the dish from decent to exceptional.

Similarly, my wife enhanced her cookies by paying attention to details. Browning the butter added depth, varying chocolate sizes created texture, and resting the dough improved flavor integration. These adjustments, while optional, made a substantial difference. This approach parallels software development. Many can replicate features and UI, but they miss the critical processes—user feedback, bug fixes, and frustrations—that shape a product's quality. In essence, it’s not just about the ingredients; it's about the care and processes that lead to truly great outcomes.

Continue reading on liamhammett.com

#reading-list #development #best-practice

🔗 Getting started with Paraxial.io for Elixir

2026-04-11T13:00:00Z

This guide will walk you through setup for Paraxial.io. Most features require a paid account. If you are on the free tier, email support@paraxial.io to request a 2 week free trial.

Application Secure

Asset management - A full inventory of all your Elixir projects

Network Scans - Determine which ports are open on your web server

Code Scans - Source code (SAST) and dependency (SCA) scanning

GitHub or GitLab App - Get security feedback in your pull request

License Scans - Determine which open source licenses are in use

App Audit - A runtime inventory of all your dependency versions

Exploit Guard - runtime detection of deserialization exploits

Bot Defense

Ingesting HTTP traffic

Rate limiting - Ban IPs that do too many login attempts

Honeypots - Ban IPs that submit a fake form

Blocking data center/cloud IP attacks

Banning bots scanning for .php routes

Continue reading on docs.paraxial.io

#reading-list #http #elixir