
About NSIDC: The mission of the National Snow and Ice Data Center is to make fundamental contributions to cryospheric science and excel in managing data and disseminating information in order to advance understanding of the Earth system. NSIDC is a trusted source of cryospheric data and services, and is a leader in research and development within this field. We enjoy a broad stable funding base which collectively supports our infrastructure and provides growth in numerous technical fields.
We are, and have been for the last 25 years, a NASA Distributed Active Archive Center (DAAC) responsible for archival and stewardship of cryospheric data. We also provide data access tools, documentation, processing services, and cryospheric expertise to the public.
This job: This is a new role at NSIDC intended to bridge between our Software Development, Operations, and System Administrations groups. You'll be expected to help evolve our infrastructure, including automated software deployment, software/system monitoring, and operations. Problems you might tackle include: Evolving a centralized logging/visualization infrastructure, positioning the software group for a shift towards processing and data storage in the cloud (a NASA goal), building out a local container orchestration platform, evolving our CI/CD infrastucture, and much more. Our software stack is mostly Python, Javascript, and Ruby. We deploy to vSphere VMs using Puppet, and most new software deployments today are done with Docker.
Personal pitch: Because we are part of a university, we know private industry can offer you a higher salary. However, we offer a starting benefits package that we feel stands out. The university 401(a) plan contributes 10% of gross pay. 22 vacation days, 15 sick days, and 10 holidays a year. UC Boulder insurance benefits are excellent. UC Boulder offers a significant tuition benefit for faculty (that's you), and a smaller benefit for your dependents. Come work here and get your Master's/PhD! Paychecks come once a month, which may be unusual for some. Top of the bill, for me, is the office environment and people. Our current location is dog-friendly, we have shared offices (usually 2-3 in an office) with openable windows (!), and you'll be surrounded with people who care about the work, the overall mission of NSIDC, and learning in general. Our developer group is usually running a book club (currently reading about Elm and just finished "Kanban in Action"), and anyone interested is welcome. You'll likely work directly with people who go to Antarctica every year. Finally, Boulder is beautiful. We have so many trails, everyone loves dogs, and we're about 2 hours from world-class skiing.
Posting: https://nsidc.org/about/jobs/devops-administrator
Application: https://jobs.colorado.edu/jobs/JobDetail/?jobId=15411
Afterward, assuming you have the basics of Kanban under your belt, I would recommend reading "Kanban Maturity Model" by David J. Anderson and Teodora Bozheva. It goes into great detail on specific Kanban practices, but it's hard to recommend this book unless you already have a good grasp of the basic concepts.
- Writing a book is a huge undertaking - make sure that you have the time to do it.
- Find a good environment to write the book in - if you have kids/pets/others that will interrupt you, try to find somewhere else to do the writing - Marcus Hammerberg (the co-author of Kanban in Action) wrote his in coffee shops, with the side effect that he gained 10lbs, so factor that in.
- Try to pause on blockers if you can - time spent on coding/writing does not always result in the equivalent amount of book being produced.
- Check what the tech landscape for your book's subject is like - if it's very fluid then plan around it - since I started my book, Node.js was forked to create IO.js, Node Webkit was renamed to NW.js, IO.js merged back into Node.js, and then Electron emerged on the scene and now overshadows NW.js (which is ironic given that they have something of a shared history).
- Keep your editor informed - I've had quite an eventful 18 months and it helps to let them know what's going on in your life.
- Writing a book is a great feeling when you see your name as a published author.
I think the one takeaway is that it is like doing a dissertation whilst also doing a job - ask yourself if you can commit to that. If you can, great. And find the right motivation too, because you are putting at least a year of your life into this project.