facundo_olano
Joined 14 years ago
Karma
872
Submissions
132
Member since
Feb 14
https://olano.dev/
View on Hacker NewsRecent submissions
Comment · 21 days ago
> If you want a reliable system you should know when to fail
I think the main problem is that most people pushing for heavy AI delegation either
1. Don’t really care about system reliability or 2. Don’t understand the difference between code and system, and assume that a system must be reliable if some automated checks pass
Comment · 1 month ago
Peter Chan was the concept artist for this game (as well as several other LucasArts and Double Fine ones)
Comment · 4 months ago
Most orgs never get to that scale
Comment · 5 months ago
Absolutely annoying to have it assuming that I want to use this when I type workflow in the prompt. Like thats not already a thing in half of the software projects
Comment · 5 months ago
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.