kathlam

Why would they hide shipping expenses?

It's clear we've all wrestled with GitHub actions and Jenkins in some shape or form. Debugging them can feel like being in an escape room, without any clues.

I work at Trunk.io and we have a tool called CI Debugger. It helps you understand your workflows. Instead of getting lost in logfiles and commits, you can pinpoint where things are bogging down or going haywire. It can give you a clearer picture of what's happening under the hood. Like having a heat map for the CI/CD processes.

I’d be more interested in ways to teach kids to think. What are some good books/tools/games for that?

When merge queues are still not enough, you need merge graphs.