Preface from me This is the translation of the original article in Russian about bad practises of IT interviews. To my astonishment I found almost all of them in the interviews that I've been taking for the last 6 months. The motivation for the current text is to attract attention to some bad
Intro The current article is the continuation of Task delivering workflow which represents a global view of team work organisation from the project manager point of view. It describes the interaction of developers with the code base to give a simple and effective way of code delivery from concept
Intro I want to present here a very simple but quite effective tasks workflow which can be used in smaller or middle IT companies or startups with no "heavy lifting" techniques and limited staff resources. The process here was tested for many years of leading such companies. Resources overview We
Motivation Here we talked much about why we need a dependency management library. Here is a short summary: avoiding much of boilerplate code controllable, centralised, predictable initialisation logic reusable resources without globals, manageable internal app state lazy initialisation easy
Motivation Recommendations about writing specification are very important because misunderstandings between developers and business owners are very common. The symptoms of that are known: the written code doesn’t meet the specifications because of information lack. In such situation
I came to the Go world from Symfony. Both things are amazing: if you are a “Symfony guy”, it’s like possessing limitless power in creating web apps of any complexity from small personal sites to a corporate software. If you are a “gopher”, you are also on a good side:
Our world is not ideal and actually we meet very few things that completely meet our expectations. If you develop for many years you might have noticed that your code gets worse with the time, either you look at it with more criticism or the continuous maintenance spoils initial good
