bottd

I've been thinking along these lines too! My idea here is to use a receipt printer + scanner. In the morning the system prints a receipt with various widgets like weather, calendar, etc. The scanner takes in the marked up receipt at EOD to update the digital data and prepare for tomorrow's receipt.

The Kagi AI stuff

Not for everything. For code you own, yes this is often the case. For the majority of the layers you still rely on documentation. Take the project you mention going straight to source, did you follow this thread all the way down through each compiler involved in building the project? Of course not.

> If there is a need to comment the code all over the place, to me it means that the code is maybe not as good as it should be :-)

If good code was enough on its own we would read the source instead of documentation. I believe part of good software is good documentation. The prose of literate source is aimed at documentation, not line-level comments about implementation.

> Therein lies the problem. LLMs are not assistants.

Assisting a person and being an assistant are not synonymous. A cane assists a man while he walks. It is a stick. That's it.

This is somewhat self-fulfilling is it not? I fear my valuable employee may leave, so to protect myself in this situation I withhold resources I could have granted them. Said employees later realize they could get better and leave.

Do they do this notably worse than say a Spring boot API or a Vue frontend? I don't think this is a React thing. Those spaghetti projects would be so with or without React.

Hot reloading is pretty common now for React or other JavaScript projects

If you wanna access DOM you can't avoid JavaScript

Do you always feel this is the case? To me the go to single letter variables are very readable. Used so widely my eyes parse them like other symbols: =, &, +, etc.

I have yet to experience a role where workers are allowed to deliver while clocking less than 40 hours. 5 hours per week on salary is only if you do not tell management.

Not official, but I have been using this nix flake to get Claude desktop on Linux: https://github.com/k3d3/claude-desktop-linux-flake

You’re failing to separate work and labor.

I recently switched from using a basic git repo to home-manager.

You’re correct that the setup you describe gets you a lot of what Nix can provide. The main thing it is missing is Nix will also manage installing your software for you. I find managing both what my software is and how it is configured with a single tool to be very convenient.

This is all decided by business needs, not by engineer preference. If devs aren’t pulling the levers it is good to expose them in an accessible interface, not plaintext.