I'm currently building a retro styled home assistant control app running on a raspberry pi with a 3.5" touchscreen with all custom UI, and I'm making it vaguely win3.1 styled, complete with color themes including the famous Hot Dog Stand.
It's very satisfying to see these old UI styles - looks great on a crappy little screen. Not everything needs to be Material Design or whatever - it just takes up so much space!
I haven't looked much into snap but it seems very heavyweight from the few things I've tried, which downloaded what looked like an entire OS and filled up my disk and RAM. And the fact that you run `snapd` to install a package is just... odd.
I've built some skills to help work with multiple repos, but it's really annoying how e.g. repo-specific .claude/ configs are only read when you start the agent in the repo folder. There's a ton of low hanging fruit to improve dev experience.
Trying to parse your sentence, which is ambiguous...
You're saying that the manager-of-managers would argue that the number of PRs should affect perf ratings? Or the MoM would push back against the line managers who were giving ratings based on # of PRs?
The best strategy is to figure out what you are going to do after smoking weed before you smoke weed. So, draft your prompt and send it before lighting up.
I ported/rewrote a million-LOC medical imaging workstation app over the course of 2 years with a team of 6. We had a full feature matrix with an extensive manual testing plan from previous work.
Uninstalling a git hook isn't exactly rocket science. If you consider this user-hostile, you must have a terrible time using git in general, since it's not exactly the most noob friendly vcs.
This isn't a new observation by any means. You could literally have said that anytime in the last 3 or 4 decades about trying a mac when you're used to other systems.
And guess what? You can say exactly the same thing the other way around.
reply