Challenge Accomplished?
5 months ago, I set a challenge to write 5 apps in 5 months. They weren’t meant to be industry game changers or startups or even well written. They were just meant to change the imposter syndrome mindset and get me writing more code.
5 months later, I have written 2 functional apps, I have a functional frame work for another, and I have another that I have decided to throw out the window. And I am ok with that. Nothing that I came up with was life changing, and at the end of the day, it made me realise just how much I don’t know when it comes to programming, setting up a server, and overall architecture.
So, I took stock. What would it take for me to step up my game and become a formidable presence in the tech sector?
A team with different levels of experience and backgrounds
When I started my first real developing position, I was so eager to get in and get coding, I didn’t really stop to think much about the structure or composition of the team. While a dev team with one senior and two juniors gave me a lot of exposure to code, it also meant that the senior didn’t have the resources necessary to cultivate two growing developers, nor would I have the opportunity to extend my knowledge to someone more junior.
A manager who is driven by the quality and growth of the team
I have published a fair amount of code at this point. Some of it probably shouldn’t have been. The buggy stuff was fixed by a more senior dev. Getting a junior to see the error of their ways is time consuming and sometimes arduous, but not teaching them how to fix it creates technical debt in the long term and results in stagnation, for the dev and the team.
A Computer Science degree
Having a Computer Science degree may not be the end-all be-all, but it does have its place. This is especially true when it comes to infrastructure, algorithms, and cryptography. Not everyone wants, or needs, a degree in Computer Science or Engineering, but based on the classes I have taken, the knowledge is absolutely relevant, instantly applicable, and gives a better general understanding about what is going on under the hood and architecturally. As a woman in tech, I am, undeniably, held to different standards than my male counterparts.
So, while technically I didn’t complete the challenge, it gave some pretty invaluable insights and goals.
In November, I started working with a new team which has developers of all levels. Some are autodidact, some are from bootcamps, and some have higher level degrees in Computer Science. They are culturally diverse, and are growing in gender diversity. I am responsible for creating quality code, and the CTO has time to explain architectural choices. As a result, I ask more questions and am included in higher level discussions.
In January, I will start a Masters in Engineering with George Washington University in Cybersecurity Policy and Compliance.
Never underestimate the outcome of a personal challenge.
5 months later, I have written 2 functional apps, I have a functional frame work for another, and I have another that I have decided to throw out the window. And I am ok with that. Nothing that I came up with was life changing, and at the end of the day, it made me realise just how much I don’t know when it comes to programming, setting up a server, and overall architecture.
So, I took stock. What would it take for me to step up my game and become a formidable presence in the tech sector?
A team with different levels of experience and backgrounds
When I started my first real developing position, I was so eager to get in and get coding, I didn’t really stop to think much about the structure or composition of the team. While a dev team with one senior and two juniors gave me a lot of exposure to code, it also meant that the senior didn’t have the resources necessary to cultivate two growing developers, nor would I have the opportunity to extend my knowledge to someone more junior.
A manager who is driven by the quality and growth of the team
I have published a fair amount of code at this point. Some of it probably shouldn’t have been. The buggy stuff was fixed by a more senior dev. Getting a junior to see the error of their ways is time consuming and sometimes arduous, but not teaching them how to fix it creates technical debt in the long term and results in stagnation, for the dev and the team.
A Computer Science degree
Having a Computer Science degree may not be the end-all be-all, but it does have its place. This is especially true when it comes to infrastructure, algorithms, and cryptography. Not everyone wants, or needs, a degree in Computer Science or Engineering, but based on the classes I have taken, the knowledge is absolutely relevant, instantly applicable, and gives a better general understanding about what is going on under the hood and architecturally. As a woman in tech, I am, undeniably, held to different standards than my male counterparts.
So, while technically I didn’t complete the challenge, it gave some pretty invaluable insights and goals.
In November, I started working with a new team which has developers of all levels. Some are autodidact, some are from bootcamps, and some have higher level degrees in Computer Science. They are culturally diverse, and are growing in gender diversity. I am responsible for creating quality code, and the CTO has time to explain architectural choices. As a result, I ask more questions and am included in higher level discussions.
In January, I will start a Masters in Engineering with George Washington University in Cybersecurity Policy and Compliance.
Never underestimate the outcome of a personal challenge.
Oh yeah! This is so awesome, Sarah! <3
ReplyDeleteLove this! What a year!
ReplyDeleteThat's really awesome, Sarah! Glad to read that your forging your own path with such ferocity!
ReplyDelete