Lubo Drobny

Such a simple question: is it done? And these are very common answers: Yes, but I need to finish documentation. Yes, code is ready, however I have to add some junits. Yes, but I need to fix some bug I have found this morning. ... Admit that something is not done looks hard for us and it is very common that we are trying to make things look better. Therefore we have started using of Done-Done, which simply means that it is really done and there is no further work to do on the subject. In other words I can confirm that I do not need to spend any effort on the task. So, is it this post done? Yes, but I need to check spelling...

I am talking about size of the company you working for. Usually people who are working for small companies are dreaming about big corporations and opposite. Big corporation workers want to work for smaller company. The reasons are obvious:  there are plus and minus for both visibility in corporation you are typically anonymous, only few people really know you. It is possible to spent a month by doing almost nothing and nobody cares. On other hand if you are top performer - again nobody cares. The average is enough. In small company usually everybody knows each other and work of each team member is visible across whole company. So if you did something wrong everybody knows it and it could have bad consequences, you cannot hide yourself in anonymous mass stability typically we consider big companies more stable and reliable, but if big company is going down the result is more painful and you are is not good position to find a new job if hundreds guys like you are in the same posit

developer I am 100% convinced that an everybody should start like a developer. Simply just do a real programming, get the hands dirty with a code.  Who never does this, never understands ... sw designer designs some parts of a software application: DB tables, OOP classes and interfaces, test cases, re-factoring, framework integration and communication. Usually prepares the skeletons or the code templates and best practices for the developers technologist typically a kid playing always with a new toys, usually executes evaluations. Must be very fast learner with large technology overview. Curios, critical, technology evangelist consultant/specialist particular technology or process expert, very often supports more teams or companies tech writer clearly documents all aspect of a software product by leveraging appropriate tools and techniques integrator integrates all pieces of the system nicely together, also smoothly integrates a whole system with a customer's envir

During the first years of my career I tried to avoid management positions and I always chose a technical career path. The main reason was that I met so much not so good managers and I did not want to be like them. I focused on a technical challenges. Of course sometimes I had to do some management stuff: couching of juniors, technical project and product management. That time I found out that I must be more Leader than Manager. Today I am a SW Team Leader and I enjoy this job. So what is the difference between Leader and Manager? Leader has the vision -  manager just copy with eyes on bottom line If you want to lead, you need to know exactly where you would like to go, you need to see the horizon and be the original. Leader motivates, empowers, delegates and trusts -  manager does command&controls Do not act like parent with children. If you have in your team the pushovers, send them back to the kindergarten. Micromanagement, it is totally obsolete. Leader sees people - man