We put everything in code. We have several layers, but they if you're new you can start with the lowest level and make your way up to find out how things are provisioned and configured.
We're on AWS so we use cloudformation for provisioning and saltstack (https://saltstack.com/) for configuration management. Cloudformation templates are written using stacker (http://stacker.readthedocs.io/en/stable/). All AWS resources are built by running "stacker build" so nothing is done by hand. We have legacy resources that we're slowly moving over to Cloudformation, but more than 90% of our infrastructure is in code.
On top of cloudformation and salt we built jenkins (CI and docker image creations), spinnaker (deployment pipeline), and kubernetes (deployment target). The jenkins and spinnaker pipelines are also codified in their own respective git repos.
All the repos here have sphinx setup for documentation purposes and the repos tend to crosslink for references.
Do you feel there should be a better way for people to find and enjoy the limitless spectrum of music created by mankind, much of which is now available online in some form -- if you know where to look? Do you love 8tracks but think the product could be even better?
8tracks is the best place for people who care about music to create and consume playlists. Its crowd curated platform offers unprecedented depth and relevancy in a "lean back" fashion -- spanning every imaginable style, activity or mood -- and an unmatched opportunity for music discovery, with less repetition and a uniquely human touch.
8tracks ranks #3 in the US among internet radio listeners aged 18-34 (after Pandora and iHeartRadio) and reaches 8m MAU who stream 30m hours/month. Two-thirds of the music streamed on 8tracks hails from Independent artists and labels, and two-thirds of the music streamed is delivered to iOS and Android devices. Supported primarily by advertising sales, the business has operated at or near profitability for the last 3 years. Founded in 2008, 8tracks is backed by Index Ventures and Andreessen Horowitz, with offices in Mission Dolores (SF) and the Flatiron District (NYC).
The article only does a dip into the effects of strength training, but the more I research about strength & health the more I truly believe that strength (not big bulky muscles) is something everyone should strive for.
I tend to do a lot of work upfront (without committing) and then go back and split the work up into smaller commits with "git add -p". I commit often, so it's never a huge list of changes I have to split.
I do this so I can cherry pick commits into other branches (e.g., fixing a bug in my current branch and merging it back to master).
I'm curious about this as well. I've posted my skills on craigslist and sent stuff out to my friends, but I always receive requests from people who can only pay very little. Either that, or I'm not doing a very good job of advertising myself - which is a definite possibility.
It means MS Word screwed you over again, this time by switching from A4 to Letter while you weren't looking. Damn Americans and their Imperialist defaults! :D
I would highly recommend traveling without a planned timeline. I was in a similar state you were last August. I quit my job and booked a ticket to fly to Madrid, Spain. I didn't have a place to stay until the day before I flew out. This was how it went for every city I visited afterwards. I didn't book any travel or accommodations until the day or two before. It was awesome to take off or stay when I felt like it. It felt like I was in control of my life.
I spent the next two months traveling through Spain, Italy, France, UK, and Ireland. I met some of the most amazing people in my life and I still keep in touch with them. I went running with a bull in Valencia, scuba diving for the first time in my life in Nice, had the most amazing pizza in the world in Naples, and got my geek on with Roman history.
At the same time, this cured my burn out. I didn't think it would, but when you start using other parts of your brain to communicate and live with people who don't speak your tongue your mind opens up.
We're on AWS so we use cloudformation for provisioning and saltstack (https://saltstack.com/) for configuration management. Cloudformation templates are written using stacker (http://stacker.readthedocs.io/en/stable/). All AWS resources are built by running "stacker build" so nothing is done by hand. We have legacy resources that we're slowly moving over to Cloudformation, but more than 90% of our infrastructure is in code.
On top of cloudformation and salt we built jenkins (CI and docker image creations), spinnaker (deployment pipeline), and kubernetes (deployment target). The jenkins and spinnaker pipelines are also codified in their own respective git repos.
All the repos here have sphinx setup for documentation purposes and the repos tend to crosslink for references.