When I decided to try to write a book, the only certainty I had was that I was not an expert on a lot of topics I wanted to write about. So I knew that to make sure I was writing a book that was correct regarding the industry standard I would need to study… a lot. For instance, I have a whole chapter dedicated on software developers: expectations for each phase of the career, the myth of the superhero developer and the “soft” vs “hard” skills.
As the years went by, I developed a framework to deal with my impostor syndrome in different scales it occurs. It is not something super complex or with a deep theoretical background, but it worked for me and I’ve been using it for the past year.
Writing is a good way to evolve your career. You can go deep in studies you are doing, can generate content to people that may be needing a more friendly view and it is a good way to gain visibility (thinking in future jobs). Once you decided to start a new blog, a doubt pops up: where am I going to post this content?
As I write this article, I am already talking from this world… the one we actually know so well. But I will try to explain, as best as I can, everything that I lived in this awesome week I spent in Portland at the Pycon 2016.
Many many moons ago, I wrote a blog post about what was like in my first 6 months at Stripe. Since then, a lot has happened including a whole pandemic and me spending every free hour writing my own book. Because of that and many more things, I never got to write a second piece to what I was initially hoping to be a once-a-year kind of blog post.
This month is my 4 year anniversary of my first job as a developer. During this time I’ve had multiple jobs (startups, big companies and open source projects) and changed countries and continents. I was able to learn a couple of things that helped me improve my career and I wanted to share them as a celebration of my anniversary and everything that came with this new life.
In April 2018 I started Udacity’s Nanodegree in Machine Learning Engineer. The classes are not cheap and many questions asked me the same thing: does it worth it?
This week I was asked to tell a little about how I became programmer (or at least, I’m in the process). I wrote this text to tell a little bit more about my story.
Leticia is a Brazilian developer who changed career to web development four years ago. She previously worked as an Oceanographer but caught the coding bug! Now she works as a developer at the payments solution company Stripe. She is a great example of a software engineer without a CS degree who has a successful career.
Being a software engineer at a new company—anywhere—is hard. The codebase is completely new, you have to adapt to new patterns (for both code and culture) and most likely the problem space is completely new to you too.
One year ago I started my new job as a Backend Python Developer. I have dropped a career, a profession and I almost drop my master degree. When everything happened, I think I didn’t understand the proportions that decision would have in my life. Now, one year later, I want to tell you a little bit about what happened this year.