- /
- Archives/
Archives
2026
September (3)
- What to Do When the Team Is Too Small and Hiring Is Frozen
- What a Senior Engineer Owes Their Reviewer
- Abandoning Code Review in the Age of Agents
August (24)
- Speeding Up LLM Work on a Single Codebase
- My Feature Planning Method: Iterate in Parallel, Then Pass Forward
- Scaling Yourself Horizontally: Attention Does Not Scale, Leverage Does
- The Apprentice Problem: Where Does New Judgment Come From?
- Bus Factor One by Design
- Continuous Research: Deep Research on a Loop
- Solo Is a Team Size: When Humans Still Earn a Seat in the Agentic Era
- Six Months with OpenChamber
- You Are the Bottleneck: What to Do When Your Coworker's LLMs Outproduce Your Review
- You Cannot Out-Review a Machine by Hand
- Iterating on Agent Skills: The Loop That Keeps Them Improving
- Anger Is a Tactic: How to Deal With People Who Use Aggression to Get Their Way
- Getting Noticed in the LLM Flood: Compete on What Cannot Be Generated
- Teach Your Agent Skills to Use Tools That Render
- What the Author Brings When the Model Writes
- Attention Engineering: Your Attention Is the Bottleneck
- My Philosophy
- Whoever Ships First Decides
- Distributed Product Management: Cheap to Decide, Costly to Undo
- What I've built and what I need: July 2026
- The Cost of Work You Did Not Choose
- Who Maintains the Slop?
- Zero Touch Engineering
- The Code You Will Never Read
July (11)
- My AI Workflow: The Skills Are the Part That Compounds
- Model Collapse: When Code Models Train on Their Own Output
- Rolling Out the Unread Review
- Verifying Code Without Reading It
- You Already Review Code Without Reading It
- Issues Are Free Now: Send the Implementation, Not the Idea
- Who Resolves the Merge Conflict? Why the Bot and the Author Are Not Interchangeable
- Feature Parity Is Not a Moat: Compete on What Does Not Clone
- The Acceptance Gap: Why an LLM Solution Is Not a Shipped Solution
- github-board - A kanban board for any GitHub search
- llm-augmented-workflows - A config-driven automation engine for GitHub, powered by opencode
June (20)
- Defects Flow Downstream, Fixes Must Flow Upstream
- Read the Commits, Not the Manual: What OpenClaw's Git History Reveals About Scaling a Project
- Team Maturity Explains the Friction, the Foundation Predicts the House of Cards
- The Pull Request Queue Outgrew You: A Triage Layer for Open Source Maintainers
- Learn the Foundation, Not the Syntax: Why Low-Level Languages Still Matter When the Machine Writes the Code
- What I've built and what I need: June 2026
- AI-Maxxing and Resistance Are the Same Mistake: Optimize Attention, Not AI Quantity
- Keeping Up With AI Is a Losing Strategy
- Loops as Files: The Scheduling Layer Skills Forgot
- When a Closed Decision Reopens: Breaking the Scope Relitigation Cycle
- The Codebase Gardener: Keeping a Codebase Sane When Teammates and Their Agents Pull in Every Direction
- The Self-Evolving Repository: Automating a GitHub Project End to End with LLMs
- Bringing Everyone to the Same Level: How Skills and LLMs Collapse Code Quality Variance
- When Engineers Disagree on Best Practices: Surviving the Forming Stage
- Managing Many Concurrent LLM Agent Sessions
- slack-cached - Cache Slack threads, channels, and users to a local SQLite database
- Developer Trust Profiles: Earned Scrutiny for Automated Code Review
- The Importance of Context When Interacting with LLMs
- The Merge Gate: Do You Need a Human to Approve Your Pull Requests?
- Rethinking Code Review in the Age of LLMs
May (13)
- Scaling the LLM Agent Company
- ghx - A CLI for agentic code reviews on GitHub
- The Backlog Is Not a Dumping Ground: Managing the Backlog of a Large Software Product
- What I've built and what I need: May 2026
- Software Engineering Teams in the Age of AI: Smaller, Sharper, Intentionally Imperfect
- The case for static priorities
- The Shifting Bottleneck: From Writing Code to Questioning Everything
- Code Factories: The RollerCoaster Tycoon Perspective
- Code Factories: The Stock Market Perspective
- Code Factories: The World of Warcraft Perspective
- Code Factories: Or How I Learned to Stop Worrying and Build the Belt
- Code Factories: The StarCraft Perspective
- task-stack - A persistent task stack that lives in your system tray
April (3)
- gh-cached - Browse GitHub issues and PRs without burning through your API rate limit
- Profit-as-a-Service
- The Future of Code Review: How AI Makes Human Review Obsolete
February (2)
- The Survival of the Smartest: Exploring Darwinian Software Development
- What Changes When Coding Agents Are Infinitely Parallel
January (5)
2025
December (6)
- GlobaLLM: Automated Open Source Contribution at Scale
- The last commit
- LLM conversations viewer
- Readability index
- The merge conflict
- The repository
November (4)
October (1)
September (3)
August (7)
- Effective vs efficient
- Slow git under WSL
- Slow network under WSL
- Company offboarding
- Feedback
- Daily review
- Weekly review
July (1)
May (1)
February (1)
January (2)
2024
November (1)
October (1)
September (1)
August (2)
July (1)
June (4)
2023
November (1)
2022
December (1)
April (2)
January (3)
2021
December (8)
- Learning - 2014
- Learning - 2015
- Learning - 2016
- Learning - 2017
- Learning - 2018
- Learning - 2019
- Learning - 2020
- Learning - 2021
July (2)
June (2)
May (1)
April (1)
March (7)
2020
December (2)
November (3)
October (1)
August (1)
July (1)
April (1)
March (38)
- Resume filtering
- Data profiling
- Time series forecasting projects
- Writing with simple vocabulary
- R&D developer
- Adding habits to your life
- Tech lead
- Documenting a process
- Recognizing processes to follow
- Superficial loss rule
- Why I avoid reading books
- Dealing with negatives thoughts
- Data used to do time series forecasting
- Reading technical books
- Reading fiction books
- Timestamping all the things
- Selling stocks during a crisis
- Apparition of language
- Internal voice
- Systematically apply processes
- Tools I use at work
- Writing articles
- Wearing a face mask against COVID-19
- Criteria for using a library in a project
- Reducing your error rate
- Extracting someone's beliefs from their writings
- Assessing a dataset quality
- Skills most used at work
- Adding tests to a project with no tests
- Making others more productive
- The most important part of a meeting
- List outdated packages using poetry
- Mypy and implicit namespaces
- Useful code refactoring
- Quickly recording notes using VS Code
- Rough project size estimation
- Visual Studio Code templates
- Read more books
February (51)
- Smarter people than you
- Improving the performance of a slow click CLI
- Slow python imports
- Determining if you are a low performer
- Pytest with tests files with similar names
- Identifying python files with no coverage
- User demo walkthrough
- Working on the wrong task
- Accelerate slow pytests
- Introducing mypy in code with lots of issues
- Knowing your users
- Rotten Tomatoes ratings exporter
- The definition of value in business
- Writing documentation
- IMDb ratings importer
- Writing good documentation
- Visual Studio Code Emoji extension
- Onboarding users on your library
- Learning topics that are overwhelming
- Ways to measure intelligence
- Omnifocus "ofocus" format
- Writing one article per day
- PHP semantic versioning checker
- Reading one Wikipedia article per day
- Anki recorder
- Tracking my readings
- Questions and problems articles writing process
- PHP code coverage verifier
- Chrome tabs count
- How to lead a large AGI company
- Healthy software company
- Photo geolocation
- Keeping a site up to date while highlighting changes
- Vocabulary gradient
- Data anonymizer
- Good execution of a project through consensus instead of leadership
- Measuring success
- Visual Studio Code Run Me extension
- Productive meetings
- Knowing what your users need without having users
- AST in python
- Working on the most important task
- When to abandon pull requests
- Reinventing the wheel
- Billionaire's life
- Great or acceptable software solution
- Process improvement
- Fighting over code style
- Repeating yourself
- Spread of corruption
- Thoughts tracking
January (31)
- Questions to think about a problem differently
- Tools I use daily and can contribute to
- Programmer commentary
- Using checklists to avoid mistakes
- Library management
- How I make complex decisions
- Solving problems with AI
- Writing everything down
- Complex and unpredictable binary strings
- What can cause learning inefficiency
- How often to review your own notes
- Why ask questions when few are answered
- Belief traceability
- Learning according to machine learning
- Picking the best material to learn a topic
- Identifying areas to improve
- Biology and genetics for AGI researchers
- Differences between brain and CPU
- Humans modeled as computers
- Answering your own questions
- Storing and updating large amounts of data
- Passive vs active agent
- A general characteristic of simple programs that are able to learn complex behaviors
- Will an AGI be superior to a large group of individuals?
- Organizing unread content
- How to prioritize which book to read
- AI coach for video games
- How to prioritize numerous tasks
- When to stop working on a task
- Determining a model usefulness
- Reducing our size for space exploration