O
Olano
olano.dev · Personal blog · on HN since 2023
Olano writes about software design, programming languages like Gleam and Erlang, AI-assisted coding, and personal software.
What HN saysHN links it in discussions of software design and AI coding. The author commented to clarify that one post described a practice and was not advocating it.
15HN people shared it
2linked it in comments
40stories submitted
1.6Kstory points
5 months agolast shared
2023people per year2026
Most-shared posts
- 1Software Design Is Knowledge Building3 people · 426 points · first shared 2024 · 110 comments on HN
- 2Gleam, Coming from Erlang3 people · 233 points · first shared 2025 · 71 comments on HN
- 3Are We Living in a Simulation?3 people · 14 points · first shared 2024 · 4 comments on HN
- 4--dangerously-skip-reading-code3 people · 3 points · first shared 2026 · discussion on HN
- 5Software possession for personal use2 people · 199 points · first shared 2024 · 73 comments on HN
- 6A Pixel Parable2 people · 167 points · first shared 2024 · 19 comments on HN
- 7Augmentation / Replacement2 people · 5 points · first shared 2025 · discussion on HN
- 8Quick notes on a brief agentic coding experience2 people · 4 points · first shared 2025 · discussion on HN
- 9Tactical tornado is the new default2 people · 4 points · first shared 2026 · discussion on HN
- 10Code is run more than read2 people · 3 points · first shared 2023 · 1 comments on HN
- 11From RSS to My Kindle1 people · 169 points · first shared 2024 · 53 comments on HN
- 12A Note on Essential Complexity1 people · 159 points · first shared 2024 · 49 comments on HN
- 13Deconstructing the Role-Playing Video Game1 people · 144 points · first shared 2024 · 67 comments on HN
- 14My Software Bookshelf1 people · 39 points · first shared 2024 · 6 comments on HN
- 15Unit Testing Principles1 people · 22 points · first shared 2025 · 6 comments on HN
What HN people wrote when they linked it
facundo_olano · 2026-05-23
Author here. I'm surprised to see this surfacing now. I just wanted to clarify, since apparently the post doesn't do a good job at it, that what I discussed there is not a methodology I advocate for. The point of the post was: ok, since there are organizations mandating to maximize speed by reducing time spent on typing code (or even mandating to maximize agents usage), is there a way we can meet that requirement while still preserving the rigor somewhere else?
This was a follow up to a previous article[1] and the pair tried to express what I still think today (using AI daily at work): every time I use AI for coding, to some capacity I'm sacrificing system understanding and stability in favor of programming speed. This is not necessarily always a bad tradeoff, but I think it's important to constantly remind ourselves we are making it.
[1] https://olano.dev/blog/tactical-tornado/
jpc0 · 2023-12-01
GCC/LLVM want projects to use the latest version of their compilers and if they added all this be default it would break millions of projects compiles.
Those project maintainers won't just add a million flags to make "legacy project 224" compile, they will just use the last compiler it worked with for eternity.
https://olano.dev/2023-11-30-code-is-run-more-than-read/
See that article that's current trending on HN if your response is "they just just fix the errors" or something along those lines, many times there isn't any business case to spend man-hours on something that works fine and has worked fine for decades.