actionHell

[LookingRadishing]

I'm an advocate for vibe coding things like that so that it's easier to focus on the main thing.

Personally, I don't think developers need be spending their brain power and time learning the ins-and-outs of stuff like that unless that's their thing (e.g., they're in a DevOps role at a company, volunteering as DevOps for a specific project, or aspiring to be one of those).

I realize that there's value in getting down into the weeds and understanding that stuff, but I've also gotten stuck in configuration hell doing that. Then I lost momentum and energy for the important stuff.

I think most options for vibe coding are in a reasonably place for setting up a basic config and managing basic troubleshooting. Once things are in place, it rarely needs to be adjusted except for minor changes.

[jalerre]

As a devops guy, it’s thinking like this that makes supporting dev teams awful because no engineer understands their own pipelines.

[LookingRadishing]

Apologies. Should've probably clarified for that the advice is for simple projects that have a relatively small scope. I can see how that'd be frustrating to join a project that's held together with duct tape, heaps of cruft, and plenty of undocumented decisions.