Re:Amazon built a new unit to fix its engineering culture
by ChadyWady on Wednesday September 21, 2022 @10:55AM
(#32926055)
I would check out <https://nixos.org/> if you're looking for a similar experience to Brazil.
My own opinion is that the Brazil had far too many running parts. I didn't like that reproducibility required the tool interacting with 3-4 different services, and I'm much more a fan of having the source code repository act as a single source of truth for reproducibility. Plus, using Brazil meant you had to use their entire tech stack, where GitLab/GitHub beat them by far.
Re:Amazon built a new unit to fix its engineering culture
by vamega on Wednesday September 21, 2022 @10:50AM
(#32925978)
Nix will get you most of this. It's got a learning curve, but I think it pays off and is not bad if you're familiar with the Brazil concepts.
Having to set up a million dependencies just to begin to start working on a codebase is a nightmare, and Brazil makes that easy.
Re:Amazon built a new unit to fix its engineering culture
by jonhohle on Wednesday September 21, 2022 @10:59AM
(#32926112)
I’ve looked into Nix at the previous company I worked for for exactly those reasons. I spent a bunch of time writing minimal dependency builders and artifact reuse for a maven monorepo where I had to tread carefully and not break the build. Nix seemed like a great way to get inter-repo dependent builds and dependency modeling.
Having self contained workspaces with all dependencies in any language, fine grained ability to replace any package with a local build, and the simplicity of package config (for most languages) was awesome.
Having to use _n_ language dependent build systems without interface pinning or reproducible builds since leaving sucked, imho. Checking out a package and running `bb` to get an artifact was just so satisfying.