Untitled Coding Blog

Since 2020 was pretty much a year spent locked inside the house, eventually I was bored and didn't have much to do except to sit all day in front of a screen, I decide to try my luck at some big companies, at least to get my foot at their doorstep with some interviews. Now to apply for these companies and to actually get a semi decent chance to pass the phone interview, also known as the phone screening, you need to learn standard algorithmic stuff taught in the first years of university. This meant relearning a bit one of the most painful courses in university that I did, that "slaugthered"  many students, like "Programming and Algorithms" or "Algorithm design".  "Luckily" for me, I was stuck inside my house so I didn't really have anything better to do. I started with a book, the standard book for interviewing at these companies called "Cracking the coding interview". I pretty much finished it in around 6 weeks by reading 4-5

 I haven't really written here in a long time so it's time to write some new things. These are just some random common sense things that seemed to short to write about individually but seem really interesting and useful to me or other people 1. There is nothing fixed in software development, all things vary by circumstances and time Remember the documentation that didn't seem that important when you started the project, well after a couple of years one the application has grown and become really complicated, no one actually knows everything about the application anymore. So now you really need that documentation. What happens if you suddenly need much more people to develop the application because of some explosive growth? Without documentation, new developers will just look at the application like they look at a painting. This actually happened to me. Maybe in the beginning of a project, a technology really helped you a lot but as the project grew, it started making things