Archive

Oftentimes you hear people say that the first job is “just for the CV” - doesn’t matter how much it is of interest to you. I believe that being a junior does not mean opting for “wherever that will have you”, quite the contrary. With that being said, you'd have to prove your worth.

I love teaching myself new subjects. I have been doing it for the past 15 years, ever since I was 11. Having said that, I am a big believer in frameworks. Over the years, I have been working on a framework for learning a new subject: GAMP. Using this framework

I discovered how crucial it is to be well-rounded as a software engineer by learning additional skills. I believe every engineer should be able to tackle new problems, even if it means needing to ramp up to a new domain. That continuous learning mindset is what can set you apart.

Software engineering and writing are disciplines at odds with each other. But here are three ways that writing has helped me become better at my job.

My team inherited a system that stores its data on a file system, constantly being saved to Git, acting as a single source of truth. Is it better or worse than a database? The short answer is, of course, “it depends on your use case”.

I focused my research on the most popular web frameworks, such as Flask, Bottle, and Tornado. Eventually, I found and fixed a vulnerability in Python.

Remember the Equifax breach that happened 4 years ago, caused by an Apache Struts vulnerability (CVE-2017-5638)? I argue that it's quite similar in nature to the new log4j vulnerability, and moreover - it will happen again, in a different project.

We worked on Dryvo for over a year. We put our hearts and souls into it - and we failed. Instead of letting the code rot in a private repository, we chose to make it public and hope someone finds it useful.