I've had some friends and acquaintances inquire about the idea of "code bootcamps" in Denver. I'm vaguely aware of them, but haven't really looked at them too closely. I've had some great experiences working with graduates of a bootcamp program in LA and wanted to review the Denver options to see what's available and how to hire from them.
These flowers were suggested by Denver Botanic Gardens as varieties that do well in Colorado and create blooms all year long to help pollinators. They were selected by monitoring for which varieties bees are particularly drawn to. I searched and found the local Rocky Mountain companies Botanical Interests and High Country Gardens sells seeds for many of them.
I like to bike for my errands and recreation, so I've thought a bit about how to best get around the Englewood area. I've been thinking about what routes are the best using these criteria:
- Connecting destinations (schools, retail, transit hubs)
- Crossing major car-oriented streets at safe locations (e.g. crossing Broadway on Dartmouth is easier than on Eastman)
- Minimized interaction with cars (e.g. biking on Dartmouth is generally better than Hampden)
I was pleasantly surprised today to find some maps and plans from the city of Englewood:
As a gardener in Denver I've heard of worm castings as a potential soil supplement/fertilizer before. I've been composting with a traditional aerobic/thermophilic system for a while. The research I've done recently is that worm castings or vermicompost is a much better fertilizer than traditional compost:
In April of 2017 the old Sports Authority headquarters in Englewood was sold for $15.7 million but at that point it wasn't well known who the purchaser was and who would inhabit the space. It turns out Earth Treks is one of the major inhabitants of the space and they had a big plan for the building. The Earth Treks climbing gym will open an Englewood location.
Disasters happen. When they do, are you ready to handle it with grace? In general people get good at handling events that they experience regularly, but high-risk disasters are managed so they don't happen often. It's not every day that power goes out at the primary data center, but when it does you want to be sure that your auto-fail-over actually works. You want to be sure your backups actually work.However, testing disaster preparedness often takes too much time time and creates little organizational value.
Once you've gone beyond a trivial number of Jenkins jobs you can get into a situation of not knowing which job does which thing. You might say "I know some job is running a query on a table, but which one?" in that case it can be helpful to search your Jenkins jobs.
Managing Jobs by script size
We have two strategies for managing Jenkins jobs: put short scripts into the job itself, but move longer jobs into code somewhere else.
Most jobs use the "execute shell command" Build Step. I also use and recommend the JobConfigHistory plugin to see how a job has changed over time (or who fixed/broke things). When the number of lines in your "shell script" section of the job gets over a maybe 3 or 4 I think it's time to move things to "real code" that is managed by a revision control system with more power than the JobConfigHistory plugin (i.e. git). So, we tend to put things into one of four places: R scripts, Pentaho jobs, Drush commands or bash scripts. All of the R scripts, drush commands and bash scripts are managed with git. The working checkouts of those directories are updated periodically (...by Jenkins jobs :)). So, if I want to grep that external code to see where a particular table is being modified it is very easy to do that. But...what about the one or two line shell scripts that are inside Jenkins jobs?
Searching Jenkins Job config files
First, you have to know about the Jenkins directory structure. The job configurations are stored in files called config.xml located in the Jenkins home directory (often /var/lib/jenkins/). So, if you have a job named production_deploy then the config file for it is located at /var/lib/jenkins/job/production_deploy/config.xml