I think I would agree that most people don't like their experience of black coffee.
Whether that's because there is no coffee or brewing method out there that, when served black, would satisfy them, or because they've just not had the chance to taste what they would consider good coffee, of that I am not sure.
I think the analogy works well but you must understand the reason for flywheels, at least in cars. A flywheel in a manual transmission car acts as an energy storage and output smoothing device. An internal combustion engine delivers non-continuous power impulses, as explosion happens in the cylinder, the force pushes the piston down, which in turn pushes on the crankshaft which results in rotational power impulse. But these impulses happen separately which results in gaps where there is no force applied to the crankshaft. Without a flywheel, your car would vibrate badly, flywheel captures these impulses and delivers continuous output.
Diesel manual transmission cars have heavier flywheels because higher compression in the cylinder results in higher torque applied to the crankshaft, therefore you need more mass to store more energy. Heavier flywheel has more rotational inertia, thus this makes revving a diesel engine seem lethargic compared to a petrol car, the heavier flywheel takes more time to reach desired RPM, thus revving a car with a heavy flywheel results in slow RPM pick up.
A fairly recent trend is putting a bit heavier flywheel to even small petrol cars, this makes them harder to stall at the expense of driver's engagement, this combined with custom fuelling maps make new petrol cars really easy to drive but not really engaging. It is common to put a lighter flywheel to cars being raced, you get faster revs and better engine response at the expense of the engine being easier to stall.
Automatic transmission cars, at least those with a torque converter, also have a flywheel, but since the design of torque converter allows for non-direct engine-transmission coupling, most of the smoothing can happen inside the torque converter itself, thus the flywheel is extremely light.
A transfer case is something BMW calls the thing that attaches to the side of your transmission to provide power to front wheel shafts, this does not mean the car is 4WD. Yes, still confusing.
I use git like that. It's my backup solution. There's no logic to the commits. I just commit and push when I feel I've done enough that it would suck if my computer fails and I lose it.
I've done that when testing CI pipelines or pushing up minor tweaks to a personal project... but committing and pushing so often.. maybe OP was editing right in GitHub?
I was developing on one remote machine and running/testing it another machine. This is just a fun little learning/diversion project... I don't really care about it having a meticulous git commit history.
Honestly I keep things pretty simple. Just the fast outlining features and the "mirror"[1] is what I use the most to mirror the current "speedrun" on the top level for next day so when I come in I don't worry about what to start.
I think the problem is due to people coming to Vim after they've used an IDE and want an IDE like experience, that's how you end up with Lua module tracelogs when you open nvim and spend time fighting the tools rather than using them. I too went though that phase but in the end I realized that I actually just enjoy vim motions, if I have them in my IDE it's already good. I'm back to Intellij with ideavim plugin and it's been great so far. I know things like lazyvim made the setup more manageable but I've never tried it.
Yeah, I can't really go without the IDE like experience. I now have lazyvim and it seems it gives me IDE features or of the box. The only thing I expect to be a hassle setting up is debugging. But I'll see when I get there.
The amount of YouTube tech grifters support this claim. Any seriously skilled dev will barely have an audience but channels skimming the water grow to millions.
This article is too basic and does not introduce anything you'd encounter in a typical Go project. If you want introduction to Go testing I recommend just reading the official docs https://pkg.go.dev/testing and understanding how to write table driven tests - https://go.dev/wiki/TableDrivenTests.
Indeed. "Test driven development" is too big of a title for setting up such a basic project. And honestly I think a decent ChatGPT prompt will generate a tutorial that is clearer and more concise than this entire article.
