Has there ever been anything more damaging to trunk based development than the trunk based development website? The comments here are 99% trash www.reddit.com/r/Experience...
Mate, we have like 5 websites; if it's a big deal to copy and paste the header HTML (which changes what, once a year at most?) and deploy them in a reasonable time, I don't think adding some byzantine technical solution will improve things.
I've lost count of how many times I've seen engineers build a complicated, woolly house of cards for "shared components", "component libraries", etc., all in the name of a standard look and feel, DRY, and it is almost always a total shit-show
New chapter for Learn Go with Tests: 🎉Working without mocks 🎉 This chapter introduces fakes and contracts, which can bring a lot of benefits to your test strategy quii.gitbook.io/learn-go-wit...github.com/quii/learn-g... #golang #tdd
