isleyaardvark
Joined 17 years ago
Joined 17 years ago
Some of them were removed. And then put back. Then increased, then decreased, or otherwise changed depending on what Trump was thinking at 3am while making social media posts
I make a ton of backup copies. I rearrange the history to how I want before I share it (git history split is great). I keep my nonsense, others see a readable changeset. (Only downside is the occasional housecleaning of old branches, but after a while their usefulness diminishes.)
I’d add that almost all code is like that, if you mean you only write it once and only look at it again if you need to make a change. And with Tailwind you generally only need to look at the one component, instead of having to go to a separate CSS file to look, and then look through the codebase to see if that code is used anywhere else.