• 0 Posts
  • 90 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle
rss





  • Unix has had a long running convention of separation between "operating system" and other files, so you can blow away something like /opt or /home without making your system unbeatable.

    If you stick stuff under /usr/bin then you have to track the files especially if there are any conflicts.

    Best to just add another path, I use ~/bin because it's easy to get to and it's a symlink from the git repo that holds my portable environment, just clone it and run a script and I'm home.



  • Oh sorry that was badly written, I compile my own kernel and run lxc on top of that, with debian base userspace otherwise.

    Then kvm on top for really different stuff.

    For my server it's debian on the bottom with zfs file serving raidz2, and on top of that 1 kvm for debian docker containers, and 1 kvm for freebsd jails which actually hosts most of the services I care about, docker is fallback if they're a pain to set up.










  • That's not the problem.

    Software used to be an artisan job, a skilled engineer carefully sculpts a solution for a problem.

    Management didn't have much to add there, or visibility, this was a world-breaking problem for them, where was their value?

    The solution was issue-tracking, make every line of code a bureaucratic nightmare, ensure panopticon-like visibility for everything, that guaranteed the manager was always in control.

    Progress slowed to a crawl, that's fine, you just need to hire more developers, hundreds, they scale, right?

    Good programmers stick to startups because large companies are just well-paying torture firms. I wouldn't go back to Google for any amount of money, but I'll do a startup almost for free, because they let me write code.