My DevOps Story

by
Anshal Savla

DevOps is a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). The main characteristic of the DevOps movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and infrastructure management. I am exicted to learn about this field.

Week 1
  • Class was introduced to DevOps.
  • Got on Slack and Trello
  • Initialized Git repo
Week 2
  • Installed and configured Docker in class.
  • It is fascinating how light weight docker is in comparison to virtulization and how it can be used to run micro services.
  • Created Book review page and added inforamtion to security/theory.html
Week 3
  • Leanred about built tool and how it can be used to automate different build processes
  • Added sources to security/theory.html
  • Updated journal/savla.html
Week 4
  • Learned about build and deploy piplines
  • Reverted git commit which rolled back journlas folder
  • Fixed styling in security/theory.html
  • Fixed Journal styling
Week 5
  • Very informative lecture by guest speaker from Stack Overflow.
  • Rolled journal/savla.html to new menu
Week 6
  • Very informative lecture by Tom from Google.
  • He talked about Web Search and Scheduling. He works in the team that handles 'Join' on the database, which sounds easy but is pretty complicated when scaled to millions of nodes that are accounted during a particular google search or inside gmail.
Week 7 - Spring Break
  • Took the week of:)
Week 8
  • Lecture by Joe West, CTO of BounceX. He Talked about the following principles.
  • Business is the thing: We must give thought to cost, business and purpose before resorting to the tools instead of using t hem just because they are cool.
  • Rightsize toolchain: It is importnat to understand where the optimization is worth.
  • Productivity is the best practice: We must try to automate things that are done repeatedly and take much of our time.
  • Document and rehearse: Documentation is essential. Rehearsing critical events makes us better equiped at handling the real scenarios.
Week 9
  • We did code review in class.
  • Read up on AWS IAM roles.
Week 10
  • Wrote review for chapter 4 and 5 for book- The Machine that changed the world.
  • Read up on integration of AWS API with AWS Lambda to help cloud team deploy the plagiarism checker
Week 11
  • Read chapter 7 of -"The machine that changed the world and wrote a summary"
  • Excited to graduate :)
Week 12
  • Finished book review.
  • 🎤 ⬇️ 👏🏼 👏🏼