@solitaire @erev Jesus, I had completely forgotten "tits or gtfo." Every now and then I get hit with a reminder of how much more pervasive that kind of thing was as little as 10-20 years ago and it throws me for a loop.
chamomile
@agressivelyPassive @technom That's a self-fulfilling prophecy, IMO. Well-structured commit histories with clear descriptions can be a godsend for spelunking through old code and trying to work out why a change was made. That is the actual point, after all - the Linux kernel project, which is what git was originally built to manage, is fastidious about this. Most projects don't need that level of hygiene, but they can still benefit from taking lessons from it.
To that end, sure, git can be arcane at the best of times and a lot of the tools aren't strictly necessary, but they're very useful for managing that history.
@SubArcticTundra Because the flavor goes into the water! That's why soup broth tastes good. Try chopping up half an onion, boiling for 10 minutes in a pot with enough water to cover them, then taste the water.
@LoamImprovement @jarfil The egg is being used to form a sauce - you limit the heat it gets so that it doesn't curdle. Classic carbonara is done with fatty pork like guanciale, so you get a sauce that consists of rendered fat and cheese with egg holding it together and making it creamy.
@kid TL;DR: If you have a secret variable in your CI/CD pipeline and it's written to a file that subsequently gets artifacted, anyone who can access that artifact can also read your secret variable.
Feels like a "no shit" moment but I guess I can see how someone could make this mistake in a more complicated setup than the example in the blog.