Trunk based, eh? Yeah, we do that on a couple teams where I’m at, too. I like the philosophy, but force pushing the same commit over and over as you’re incorporating review feedback is antisocial, especially when you’ve got devs trying to test your changes out on their machines.
I’ve only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I’ve never found it worth the trouble personally
Highly recommend throwing –patch on any git commands you’re used to using. You will have the prettiest, most atomic fkn commit, I’m serious people will love you for it.
I mean many people won’t care, but the quality folk will notice and approve.
Since transitioning to work, but still keeping a notebook, I use the following. Colours based entirely on what pencils/highlighters I had when I first started taking notes at work.
<span style="color:#323232;">Assigned work Blue
</span><span style="color:#323232;">Ad hoc Orange
</span><span style="color:#323232;">Errors Pink/Red
</span><span style="color:#323232;">Solutions Green
</span><span style="color:#323232;">Actualizing Yellow
</span><span style="color:#323232;">WTF Purple
</span>
bees sometimes fly, like flies, but not exactly like flies; though they do fly. Bees do. Well, flies also fly, but differently. Not that differently if you don’t care about such distinctions, but pretty differently if you do. I wish I could fly. That last one wasn’t a bee fact. It was a me fact.