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 p...

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 peo...

"You should have a Team Spirit" - you could hear this from the team building trainer. It is funny because they usually works alone but I agree with them. I believe that a good team is precondition for a success: be together if some members of the team are at Bratislava and others at California, where is the Team Spirit? Probably somewhere deep in Atlantic Ocean common goal we have ours personal goals but in the team work we need to agree on one common goal. This team goal must be written somewhere in the team room where everybody could see it every day. It is very good sometimes re-ensure that everybody understands the goal the same way respect we are human beings and without mutual respect we are just wasting our time and only pretending team spirit pleasure to work together usually we spend more then 8 hour a day together and if it is painful it cannot lasts for a long time good mix different personalities and skills which complete each others are very wel...

I have been thinking about very complex and sophisticated test at least 20 questions, but finally I have shrunk it to only one test question: On Sunday evening ask yourself: "Am I happy to go Monday morning to work?" a) Yes, I am happy and I am really looking forward - 1 point b) No, I am unhappy, I am under stress or I am scared  - 0 point Now calculate points. Result: 1 = you like your job 0 = you don't like your job, repeat this test next 3 weeks, a then calculate cumulative result; if it still 0 you should change your mindset or job P.S.: My result is 1, what about you?

Never lie in CV I asked one candidate about technology mentioned in his CV and he did  not remember what it is. It is a shame. If it is accidental or intentional it does not matter. It is bad. Sometimes IT guys make CVs nicer, they list a lot of technologies because HR people just compare buzz words and if you have not right words in CV you cannot pass to next round. That is partly true, but do you really want to work for a such company? Maybe it is reasonable to prefer company with a more technical approach. I think it is better to be honest and do review of CV with respect of reality. If you have changed one annotation or corrected one xml in a Spring project that does not mean you are a Spring expert or somebody somewhere in application uses a Hibernate does not make also a Hibernate expert from you or you first time compiled a Linux kernel you are definitely not a Linux expert. Please just think about it and never lie in your CV.