Lou Franco: code, apps, and writings

follow: @[email protected]

Posts

Finding My First Open Source Contribution

Write While True Episode 48: Start a Collaboration

What Makes a Good First Vibe Coding Project

Reducing Technical Debt: Top Five Coding Resources

26 for 26 in January

Blind Sketching

Re-Onboarding Via Tech Debt Payments

Making Happiness a Priority

2025 Blog Roundup

Vibe Coding vs. Vibe Engineering

Fuerte Y Suerte

Perfection Is Not An Accident

22nd Blogaversary

Use Motivation To Program Your Environment

2026 4DX: Fourth Discipline

Write While True Episode 47: Write Useful Books

Improving My Social Connection Index

LLMs Are Good At (some) Languages

Page-o-Mat Can Make Smartnote Page Templates

How Digital Journaling is Better Than Paper

How Digital Journaling Is Worse Than Paper

Mimicking Work-like Accountability

2026 4DX: Third Discipline

2026 4DX: Second Discipline

2026 4DX: First Discipline

Experiments for 2026

2025 Retrospective

November 2025 Blog Roundup

Protecting Myself

Dependency Maintenance vs. Supply Chain Attacks

Thankful for Randomness

My Current (late 2025) Interleaved Reading List

Interleaved Reading

Moats and Fast Follow For Vibe Coded Projects

It’s not Debt if You Don’t Care About the User

Workshop: Eight Questions to Ask About Your Tech Debt

How I Learned Pointers in C

Using Fuzzy Logic for Decision Making

Moving from React to HTMX

Early Thoughts on HTMX

Dev Stack 2025, Part X: networking

Dev Stack 2025, Part IX: tooling

Dev Stack 2025, Part VIII: uv

Dev Stack 2025, Part VII: Sqlite

Dev Stack 2025, Part VI: Bulma

Dev Stack 2025, Part V: VSCode and Copilot

Dev Stack 2025, Part IV: HTMX

Intrinsically Safe

Dev Stack 2025: Part III, Django

Dev Stack 2025: Part II – Linux

Changing my Dev Stack (2025), Part I

NaBloWriMo 2025

Code Coverage Talk at STARWEST

Algorithmic Code Needs A Lot of Comments

Tech Debt is Caused by Correct Behavior

Make a Programmer, Not a Program

Teaching Your Book Before You Write It

My “Show HN” Follow-Up for “Swimming in Tech Debt”

Describing Tech Debt to Vibe Coders

Marketing First When Writing a Book

Finding Functions That Are Risky to Change

How to Get Changes Through QA Faster

How Product Managers and Engineering Teams Can Work to Together To Tackle Tech Debt

The Infinity-X Programmer

February 2025 Blog Roundup

The Central Question of a Code Review