facundo_olano

> 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

Peter Chan was the concept artist for this game (as well as several other LucasArts and Double Fine ones)

Most orgs never get to that scale

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

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/

A Makefile is good for this, and why not checking it into git?

Is there a recommended modern day, non mac specific, equivalent to those "Macintosh Human Interface Guidelines" linked at the beginning of the article?

Willing to accept AI agents can replace programmers

Not willing to accept ex-US devs can do a comparable job at half the price

I started with prelude[1], I wanted something batteries included to use as my main editor right away, but not as structurally different from vanilla as Doom or Spacemacs. Then after a couple of years I rewrote my config line by line looking at what prelude did and keeping only what I needed.

I’m happy with result, but this was 7 years ago so there may be better options than prelude to do something similar today.

[1] https://github.com/bbatsov/prelude

I built that feature (auto mark as read by scrolling) into my feed reader if you’re up to self host and curate your sources

https://github.com/facundoolano/feedi

I did try to build a public facing news aggregator with a similar ux but I couldn’t pull it off purely based on client side state (and I didn’t want to do user management)

> I’ve been using Magit at work because it’s what everyone uses.

Where do you work?

I have the same issue, the chronological nature of feeds kind of breaks this flow. It feels like there’s a missing piece, like a standard to browse older content from a blog. I Wrote a bit about this here: https://olano.dev/blog/web-anthologists/