The problem is both (1) knowing what you want, and (2) specifying what you want.
(1) is hard enough and a necessary prerequisite to (2) which, even so, is even harder than (1).
Good, documented software is the accumulated knowledge of people who (1) knew what they wanted, (2) implemented it, and (3) communicated how it works. AI can ease the building of such software but does not make the process trivial.
Take some existing code and bundle it into a zip or tar file. Upload it to Gemini and ask it for critique. It's surprisingly insightful and may give you some ideas for improvement. Use one of the Gemini in-depth models like Thinking or Pro; just looking at the thinking process is interesting. Best of all, they're free for limited use.
Wanted to try more of what I guess would be the opposite approach (it writes the code and I critique), partially to give it a fair shake and partially just out of curiosity. Also I can't lie, I always have a soft spot for a good TUI which no doubt helps
I don’t think the built environment is that determinative. I live in a car-dependent suburb. Walk Score 2.
My neighbor knows the whole street. She knows the garbage men. It’s because she wants to. When I run into her outside, she chats. She walks her dog and chats with dog owners and anyone else she sees.
Easy relationships are available at the grocery store, post office, etc. I’ve been seeing some of the same people working at Costco for years. I don’t know them. It’s not the built environment. I’d need to take effort to build a relationship with them. My neighbor would. I’m simply not so inclined.
This is an incredibly important point - you could remove the car entirely, even make you dependent on others (as you're dependent - or were before self checkout - on the Costco clerk) - and you still would have the disconnect.
Hardship can force it more often, perhaps, but that is accidental and secondary.
In all the times I've traveled on forms of "mass transit" (airplanes, subways, trains) the only time I've ever really talked to someone was at the seat-together dining on a long-distance train. Otherwise you can sit next to someone for 20+ hours and never say much more than "excuse me" if you need to use the restroom.
(Another counter to this is kids, if you have kids and there are kids anywhere within screaming distance, they will find each other and immediately be best friends. Parents get dragged along - https://www.bluey.tv/watch/season-2/cafe/ )
It's absolutely the built environment. Your Costco example is a clear example. you drive to Costco, you walk in, grab generic packaged goods without needing to really talk to anyone, and then go to the checkout and use the automated kiosk to make your purchase.
There's no reason to have a human interaction, so why would you bother getting to know the cashier? You're never going to build a relationship with the cashier precisely because of the environmental structure.
Contrast that with walking down the street to a local store that one of your neighbors owns. I bet you would already have a relationship unless you chose not to. Why? Because you'd also see them at your kids birthday party, or you'd see them at the bark down the street, or out on a walk.
I made the choice at Costco to not build a relationship with anyone. There's a guy standing at the entrance checking memberships. I've seen him for years. I don't know him. I don't use the automated kiosk if I have several items. I see some of the cashiers for years. I'm cordial but I don't chat them up. One woman who has been there for years chats with me a bit; I'm cordial but don't reciprocate a ton.
There's a corporate supermarket owned by a Dutch multinational not far from me. I see some of the same employees there every week. One of them loves people and recognizes me. I could stand around and chat with him if I wanted. But I don't want to.
I made this choice. Someone who wants to build relationships chats with people. Folks like that chat with people at the grocery store, on the airplane, waiting in line, etc. Often it leads to nothing, occasionally it leads to something. But the point is, they practice it. I don't. The built environment is not stopping it. Not being in a "local store that one of your neighbors owns" has nothing to do with it either. Plenty of relationships are built in corporate chains.
I think this is fundamentally incorrect, and the way we live today and the problems we experience bear this out. It's not about individual choices you make to engage with a cashier at Costco, it's about the opportunities to engage and where they occur. You're still talking about a forced connection you have to decide to make at the checkout line, and ignoring that you never see that person again in a different context, like in your own neighborhood or at your local restaurant.
Socialization isn't a choice one makes, it's supposed to be organic. The fact that you have to choose and make decisions around interacting with other people proves my point.
> doesn't have a button to navigate to the parent folder.
Command + Up Arrow, which is also visible if you click on the "Go" menu. There is also a toolbar button that shows the entire set of enclosing directories; offhand I can't remember whether this is visible by default. There is also "View -> Show Path Bar" which shows all this information at the bottom of the window.
> I have literally no idea how to get to my home directory
Go -> Home, which shows a shortcut key for this, Command-Shift-H.
> Externalities lead to users downloading extra gigabytes of data (wasted time) and waiting for software, all of which is waste that the developer isn't responsible for and doesn't care about.
This is perfectly sensible behavior when the developers are working for free, or when the developers are working on a project that earns their employer no revenue. This is the case for several of the projects at issue here: Nix, Homebrew, Cargo. It makes perfect sense to waste the user's time, as the user pays with nothing else, or to waste Github's bandwidth, since it's willing to give bandwidth away for free.
Where users pay for software with money, they may be more picky and not purchase software that indiscriminately wastes their time.
If I'm traveling for work, I'm working all day. At the end of the day I often just want to rest in the hotel room, especially if I take my dinner in a restaurant.
Typically I don't watch the hotel TV though, as I don't want to figure out what channels are on it and I probably wouldn't want to watch them anyway. If I watch anything it will be on my iPad.
Physically it is very taxing. Snow is heavy, and the movements aren’t typical of daily activity. Even for a modestly sized property it can take awhile.
Years ago it was remarkable for software to have docs built-in as Emacs does.
Then for many years it was standard for software to have help files, and it seemed anachronistic for Emacs to loudly proclaim it is self-documenting.
Now in the Web and LLM age, much software doesn’t even try to have built-in help or even much documentation, and it’s again remarkable that Emacs is self-documenting, especially the part of Emacs that users can program.
> Then for many years it was standard for software to have help files, and it seemed anachronistic for Emacs to loudly proclaim it is self-documenting.
Emacs' notion of self documentation refers to something slightly different than the fact it has online help files. The help facilities can query the Lisp runtime for things like functions and keybindings. These update dynamically as the system is reconfigured. The result is something that isn't quite as cleanly presented as an online help document, but has the benefit of being deeply integrated into how the system is actually configured to behave at the moment. Very cool, and very much dependent on the open source nature of emacs.
Consolidation frees up real estate, allowing new businesses to open. Where I live, old supermarkets are now farmers’ markets, trampoline parks, and health clubs, and an old car dealership is a church.
reply