mattacular

Counter-point: Doesn't make it hard to read at all, definitely not "egregious" as it's a very common style to find for informal writing all over the internet.

Author's own style is certainly refreshing and welcome over LLM slop that dominates most HN posts now.

Also it doesn't even matter if the rare company making a high quality product long enough to get a positive brand rep is incentivized to sell out (although I don't disagree with you that is a pressure to act in short term interests) thanks to this great thing called: private equity!

I pretty much assume every smart home device capable of doing this is doing it already.

Nothing gets connected to wifi. If temporary connection is required it gets a random one time use guest network SSID and pass that I remove after. (Yes they can collect and send setup metadata during this temporary access period but sometimes it is a worthwhile tradeoff)

Snowflake defense

The problem to me is, if people slowed down enough to carefully review and also rewrite model output in their own words (even if we're not counting code output), then what you have is a tool that probably makes you slower overall instead of much faster. I don't think that is a bad idea per se, but it is generally the opposite of how you're expected to perform with AI tools.

"Byte-for-byte"

What are some traditional automated refactoring tools that can do stuff like those tasks from the example?

For one made by a real band check out Sturgill Simpson's cover

A lot of software engineers do still care how software is produced. That's a good thing!

That's how JWT is designed to work

Code cannot and should not be self documenting at scale. You cannot document "the why" with code. In my experience, that is only ever used as an excuse not to write actual documentation or use comments thoughtfully in the codebase by lazy developers.

Test automation is kind of like a religion. It is comforting to believe that the solution to code is more code.

I find it to be more difficult. Especially if I can't pane the files in view comfortably (ie. beyond 2 or 3 it gets significantly harder to work across them).

Some frameworks or coding styles really lean into having lots of tiny files. That necessitates a more complicated directory structure for the project. Locating files eventually tends to requires search capability rather than being able to look through the tree in a sidebar.

None of this is "hard" per se but I find the opposite is nicer to work with typically.

That settles it