If you’re a senior developer, do you even remember your first job in IT? It was so many years ago... At some point, you might think that you already know all the stuff that you need. There is an occasional challenge on a project, but still, for some, it might seem dull… So how to deal with it?
Coming up with a definition who a senior developer is may be impossible due to the fact that for every person this will mean different things. However, there are some key qualities and capabilities that make senior developer a senior developer.
Starting out is never easy. This is a post aiming to present some of those struggles, shared by real people during one of the recent Meet.js, offer encouragement and support as well as some advice from those more experienced.
In the examples, the testing stack is Jest and Enzyme, but this pattern can be used in any other combination of test runner and renderer. I would like to show you the simple pattern that we are using in Selleo, and how it came to life.
‘A modern CTO is somebody who is a programmer that is also a business person.’ There are many misconceptions about who a CTO is and what are his responsibilities. A CTO is responsible for both long- and short-term needs of a company. He utilizes the business’ capital to invest, in order to reach the goals of the organization.
Choosing the right people may be a complicated task and at first, you may think that the more skilled developers - the better. This is not always the case and this article will answer the question why your teams should not consist only of top-notch engineers.
One-On-One Session (or O3 in short) is a really powerful tool used by many managers all over the world. It is a well-structured meeting in which a manager/team leader spends some time (usually 30 minutes) with each of his/her team member to discuss progress, strengths, weaknesses, goals and other employee-related matters.
