1. 1
    • Deploying: Basic webaps - compiled go binaries w/ supporting files and python services
    • Provisioning: Ansible (cloud modules)
    • Configuration Management: Ansible (various modules including pip)
    • Engineering Team: 3, all responsible for maintaining ansible playbooks (in a git repo)
    1. 1

      Alta3 Research does. It has been a workhorse for deploying training environments (I do side work for them).

      They have a nice video on how openstack worked well for them and cut costs.

      1. 2

        Is it just me or is the title sentence difficult to parse? Is this a correct interpretation of the author’s intent:

        Having a habit of not finishing your side projects means you are a busy person; not an unproductive one.

        The author never came back to the word “productivity” or what that means to him in relation to side projects so I don’t feel like I can say with convection that my re-wording is correct.

        1. 3

          No. The interpretation is: “Having a habit of not finishing your projects, side projects or not, means you are just burning time, not producing something tangible you can point others to when they ask of your achievements.”, where tangible artifacts is one view of productivity, in particular in academia, but also for example when using your github as your resume.

          Related ideas are “the perfect is the enemy of the good” and “release early, release often”. I think focusing on “finishing things” encourages you to keep the scope small and work in increments. And I do think this makes for better use of your time.

          Or as they say in the theme song of The Ship Show: “What is the main purpose in life?” “To ship, of course.”

          1. 2

            Which variant? Factor perhaps? It’s the most like a modern FORTH dialect that I’ve found in recent times.