My Journey
More than ten years in IT is quite a long time. During that period, I had ups and downs, made mistakes, and achieved some important milestones. There were moments when I thought, “I will leave this crap behind, find peace in the mountains in a small cabin, and become a shepherd.” – true story. :)
I also had times when I was overworked and couldn’t even look at code anymore. Now, I know my limits, and these signals are red flags for me – they mean I’m pushing myself too hard. I’ve also learned how to handle these situations, as they can be dangerous and lead to burnout.
On the other hand, I’ve met incredibly smart and inspiring people, worked on many interesting problems and projects, and grown both personally and professionally. I’ve learned how to manage my time more effectively, handle stress, and set boundaries with challenging people. I’ve even learned how to resolve conflicts peacefully (I haven’t had many conflicts, but they eventually happen to all of us because we are human). This kind of stuff can be really helpful, not only professionally.
I want to share my experiences and maybe offer some guidance so that younger colleagues can learn something useful and avoid my mistakes, perhaps managing their careers better. My career wasn’t bad, but with the knowledge I have now, I would have made some different decisions.
Different Times
When I started my career, I believed that almost anyone could become a software engineer, and at the time, that was mostly true. The market was growing fast, there was a high demand for specialists, and it was relatively easy to get a job if you had some programming knowledge. However, back then, the internet had far fewer learning resources, and gaining that knowledge without proper guidance was incredibly tough. Currently, as I’m writing this, the situation is quite the opposite.
For Regular and Senior Colleagues
For more experienced colleagues, I want to share technical topics. For example, I’d like to write about micro-frontend architecture. For backend developers, I can explain CSS, which can feel unpredictable and frustrating when you don’t understand how it works – I was in that position once too.
I also want to write about topics such as how to create an npm library, how to handle deployments with monorepos, and more.
I also plan to write tutorials – not only to help others but also to solidify my own understanding of interesting topics. Hopefully, my writing will benefit others as well. Finally, I want to post about annoying problems that are hard to find solutions for online – but only when I actually manage to solve them myself.
Summary
To sum up, I want to write about important matters to me, and hopefully, it will benefit others. Maybe I will confront different ideas and views in discussions on social media or in comment sections (I will work on them soon). Sharing experiences and thoughts with respect for other people is something that I really enjoy. This post was very general, and if you’ve read to this point, I truly appreciate it! :)
So, my next post will definitely be technical (if you don’t want to miss it, subscribe!). Most likely, it will be related to Astro.js – it’s a really cool framework, and I love working with it. The current website is built with Astro, and although I’m still learning it, I can already share some useful information.
Have a great day!