Goals — Sprints — What are they good for?
I’ve done more reading than anything else this week. I would highly recommend you get a Safari Books subscription, if you haven’t already.
I didn’t accomplish much in my studies due to a hospitalization. However, I’m happy to be back out in the real world and it’s time to get back on my game.
I would not recommend allergic reactions, they make your hand do something like this:
This week I’ve starting ripping apart Terraform to see how I could deploy my infrastructure in the way I’ve configured it. I’m quickly finding roadblocks, like how any changes to certain files or resources will cause Terraform to rip down your entire Google Cloud cluster and rebuild it. The solution to that problem being to use Kubernetes so when I do a deploy that would effect a cluster then Kubernetes will move all the pods to another cluster, then move it back. It sounds all good in theory, we’ll see how Kubernetes actually handles it soon. I’m also coming across more realizations as I go, like will Jenkins be it’s own stand-alone instance, or should I have it somewhere else? How do I deploy kubernetes with a working service mesh (and can I even do that?). I still have a lot more studying and learning to go.
I also spent a lot of time trying to build a game plan for how I will continue my learning. If I’m not going to go to college right now, I still want some type of structure to abide by. After doing some reading, I’ve found that goals can deter or discourage people due to setting unachievable goals and missing the target. I read up on Sprints, which is where you get a learning period (a couple months) and then you have a month to reflect, and you continuously do this. I also tried to make my structure as close to the Agile Workflow as possible, even though my knowledge of it is lacking. I’ve only read a couple chapters in a book about it, however I know it will be used heavily throughout my career so I should familiar used to it’s structure.
Off of that above image, which the key thing I take is to constantly re-evaluate, I came up with this:
- Each Learning Sprint will be Four Months in Total (Example: Beginning August — End of November)
- Each Learning Sprint will have monthly re-evaluations to identify struggles, issues with methodology, and ways to fix anything that may have hindered progress to create a continuous development cycle.
- Every week a “Weekly Wrap Up” blog post will be made to discuss challenges, progress, or other misc. things
- Every week should compromise of one group activity, one social activity, two mentor sessions, and consistent working on projects.
Since I already have two mentors (and constantly looking for more) so that part is easy, thinking of mentoring sessions as classes. Each mentor session we accomplish covering a topic, and then I usually request to be assigned some work, a challenge, that I can complete until we meet up next week. Right now, I’m working on building a Turing Machine with one mentor, and learning DevOps tools with another.
The group activity can be anything from going to a meet up (Women in Tech, Kubernetes) or going to the meet up I’ve been hosting, called Noobs Group. Noobs Group is my way of forcing myself to get out of the house and actually work on projects, since sometimes at home it is easy to find other chores and things to work on. So far, I’ve been encouraging the other members to bring up topics they would like to learn about, and then in my free time (whenever that may be) I’ll research that topic, whether on Safari Books or taking a class, then we can cover it in the group. Hopefully this will expand my knowledge in other subjects.
The social activity is where things get fun, and I’ve been attempting to take one person out from my company’s R&D department to see where they started, what they like, and how they got to where they are now. It has been providing me with some groundwork on what to do, what not to do, and best practices to get where I’m going.
I’m sure this “fake college” structure I came up with will need reworking down the road, but for right now I’m learning a lot.
Also, GitHub! (https://github.com/s-christoff). I’m still very much figuring out GitHub, Git, and my own project. But, I hope I’ll eventually have something worth while to contribute. Currently there’s only one project, and it’s my terraform configuration.
Questions this week:
What is Consul? (How can it be used, why do people use it, is it useful, what tools are it’s competitors?)
Also, what is Docker Compose, why does it need to work with Kubernetes, why not just use Kubernetes in the first place? (http://blog.kubernetes.io/2017/08/kompose-helps-developers-move-docker.html)