All the focus on Chef over the last few years has paid off — I have officially joined the Professional Services team at Chef Software, where I will be working as a Consulting Engineer. (I was actually already part of Chef’s extended Professional Services team through my previous contracting relationship .. but having direct access to product and support insiders at Chef will be so more beneficial when helping customers). Job description here.
I’m really excited for this new opportunity, and that I will have more opportunities to lead training programs, and to travel; two of my favorite things!
And of course, helping to fuel transformation to the devops way is a big passion of mine. This is more than just changing the tools companies use, or the methodologies — it is all about development, QA and operations teams working together, treating operations like a software project, including automated testing of changes to infrastructure, and the ability to rapidly deploy all code changes, frequently and safely, through an automated pipeline.
As far as I am concerned, my job over the years in operations was always to Automate All The Things, as best I could; the tools have just gotten better, and infrastructure has gotten to the point where everything needs to be scripted and automatically tested, in order to operate reliably and at scale. It is a no-brainer.
I had a blast at the Chef Community Summit held at Chef Software’s HQ in Seattle, over the last two days. This year three smaller summits are being held, one in Seattle, one in NYC and one in the UK, and the smaller size made for better open space discussions. We still had some international attendance.
Although the open space discussions were great, the highlight for me was Hack Day. On Monday evening I wasn’t sure what I’d be working on — unlike everyone else who seemed to have something in mind. But then I remembered that I had submitted a Chef issue (bug report) in 2015, and on checking saw that it had been accepted as something that should be fixed, but had not yet been worked on by anyone. So I decided to fix it 🙂
Funny enough, I submitted the issue only steps from where I wrote the code to fix it. At the time in early 2015, I was co-leading a Chef Fundamentals training class in a conference room on the same floor at the Chef Software HQ, and something one of the students had done, highlighted the issue I reported — which had to do with data bag naming and ability to search data bags with particular names.
The first thing to figure out was the correct approach to fix the problem. I had suggested a way to fix it in my issue report (don’t allow those particular data bag names on data bag creation), but a Chef employee had suggested something else (a way to support those data bag names). I dug into the code and found that the other suggestion, although it sounded good, was not really feasible; I discussed it with him and others, and they agreed. Which was good, because my fix was a pretty easy way to solve the problem.
At the time of writing this post my fix has not yet been merged — the first submission of code + unit tests was approved, but then I discovered a second place where a similar fix had to be done, and have since submitted the code and unit tests for that too. The second check-in needs to be reviewed.
Still, I am confident that I will soon officially be a contributor to the Chef codebase, however minor a contribution it is 🙂 One has to start somewhere. And soon will also contribute to the web docs at http://docs.chef.io.
I took the 4th exam, for the 3rd badge, last night – Deploying Cookbooks, and I passed, completing all the requirements to be a Certified Chef Developer :). (As before, 80% was the pass mark).
I’m looking forward to the ‘Auditing with Inspec’ exam being available, so I can become a Certified Chef Architect — it is supposed to be released in summer 2017.
So far I’ve passed Basic Chef Fluency, and Local Cookbook Development (parts 1 & 2). One more badge to go .. I’m going to do Deploying Cookbooks next, it looks like a far easier option than Extending Chef. You have to complete three badges in order to become a Chef Certified Developer.
The material is fairly easy for me, I’ve been working with Chef configuration software since 2012, and have trained with Chef Software, Inc. to be a trainer for their Fundamentals (now called Essentials) training course. But, like with the AWS exams, things are constantly changing, so you have to keep on top of your game.
It was time to re-certify as an Amazon Web Services Solutions Architect Professional as the certification lasts 2 years. I passed!
Keeping up is challenging as AWS is currently adding new features to their services at a rate of over 1,200 per year .. and it is a tough exam.
Here’s a sample question from this exam. For the original test I had to answer 80 similar questions in 170 minutes. Fortunately the recertification test only asks 40 questions, but in only 80 minutes — so just 2 minutes to answer each long question usually involving multiple services, with subtly different and usually seemingly plausible sounding options to choose from. And sometimes multiple correct options have to be chosen.
I finished the recertification test with 16 seconds to spare, and no time to review!
After being known as Sandi my whole life, I am embracing my given name – Sandra. As a result, I’ve updated the URL of this site to sandratiffin. The old URL, sanditiffin, redirects here.
Sandra is a female name, which is often used as a short form for Alexandra or Cassandra. Alexandra is a feminine form of the male name Alexander, which is a romanization of the Greek name Αλέξανδρος (Alexandros). It is generally interpreted to mean “protector of man” or “defender of man”.
The professional exam is a *lot* harder than the associate exam .. but after months of study, I took the exam yesterday and passed!
Today I took and passed the proctored exam, and earned a nice shiny badge to display on my website.