Designing a tech interview for a software house has some challenges. Most notably we may not know the final client and their culture and technology stack. We’re also limited in time. Read how we can make the best out of it to be sure we’ve made a good decision hiring the candidate.
Inspired by the author’s main idea of “learning in public” I decided to do the same and publish my notes from this book
Collecting notes, useful resoures and ideas in an efficient way can be crucial if we want to learn effectively and create content. In the article I describe my way to do it.
Van Gogh said that “Great things are done by a series of small things brought together”. Same applies to engineering. We do small steps and learn based on them. On a day-to-day basis it may seem like no progress, but it accumulates over time giving amazing results.
Asking for help is difficult. But this is something we should learn how to do if we want to stay sane in our job
Quick decisions can make us stuck in a traffic jam. What does it have to do with software engineering? Every engineering field is full of decisions to make. And our brains are lazy and usually try to follow the easiest path. Read more how we can work against intuitive but irrational decisions
We constantly try to push forward and learn new things. But do we find time to stop and look behind to see how much we have achieved? It’s easy to overlook progress on a day-to-day basis, but when we look from afar it can be impressive!
Remote work is possible but requires certain habits and tools to be efficient. One of such tools is Slack. I share some useful advice on both private and organizational level how to make sure we communicate effectively and securely.
If we analyse a software industry and companies in it, we can distinguish two main types of companies: service-based and product based companies. Depending on which type our company represents, we may tackle the technical interview process differently.