War and Peace. Heard so many good things about it. Despite everything, went in not having super high expectations.
The whole book turned out like a reality tv show. All the characters had some petty drama that they blew out of proportion. Hundreds of pages where nothing really happens, people just complain or bad mouth other characters.
I had to stop half way through.
Totally get that. Just saying that different people want different things out of their jobs, and it’s a good thing that there are places where all of them can fit.
Isn’t that the whole point of hiring people that fit the company culture? I’ve worked at both types of places in different stages of my life. Both can feel good or bad depending on where you’re at. Don’t try to change the job to fit your needs. Find a different one.
I’ve worked on dev tooling in a fairly large company. Especially for cyber security, do not get a Mac. A lot of the tools are just different enough on a Mac that they will make your life much harder.
I would say it’s actually easier in many cases. Nix has really fantastic packaging tooling. You do have to learn a bit of the nix language, however (not become an expert).
The issue comes when trying to build from source. In most other distros, ou just follow the readme. In nix, you have to package it.
I wasn't trying to go into typing as much as using structs or objects when working with known data attributes. Sorry that it was a bit misleading.
The original actually went into using trees, sets, heaps, tries, etc., but it felt way too... ranty. After writing all that out, I realized that most of those other cases come up really infrequently, and that my biggest gripe was about not using structs or other pre-defined key container types. I thought it would be better to keep things short and focused.
Maybe I should re-write and publish a data structures edition.
I love the addition of dataclass. Makes refactoring such a breeze. If you need to extract some function, boom, you already have a class that you’re using everywhere.
My first guess would be emulation for apps that do not run on aarm by default.
A lot of OSS devs don’t want to spend time supporting a closed architecture. Especially some of the more privacy and openness focused apps that you’re running.
I’ve used pine64 boards for this. They have a few more options and are always available.
Yeah it does. I actually use nix as my base OS on one machine. But when I need to work on a project that will never be packaged with nix, and I need all the dependencies, it really becomes impossible to just use nix.
Nix makes an amazing bas OS, however.
I use it to share environments with a small team. Just have distrobox specific Docker files and we can all spin up the same distrobox environment locally.
We end up having a different base docker file (e.g. our distrobox one has editors and stuff), but we all share the same project specific docker file. That same project specific file gets used in CI/CD and deployment, but with a minimal base. So all in all, I would say it's even better than Vagrant because we run the same system in production.
That looks really well done. And a lot of stuff would be condensed by having viduals.
Doesn’t look like my preferred style… Maybe that’s why I couldn’t get into the book either 😅