Reading makes a full man, conference a ready man, and writing an exact man / Francis Bacon
We’re using personification in Software Development. It’s really fun! The names which we’re using internally are not official and used only between developers. Of course we also have other official public names, but they’re boring.
If in most of the cases when you have a new task, you’re focusing more on opportunities to do it with all cost instead of finding obstacles and reasons why it cannot be done, then
A few teamwork rules that can save nerve cells of all in difficult moments. It happens so much work that some moments are forgotten. Therefore, it is important to create some set of rules, if
I’m certainly not the first one who faces obstacles in implementing changes in the organization from the bottom up and not the last one. I want to share some of my observations, conclusions and mistakes
Everybody speaks that documentation is important for development. In the end when a project accumulates hundreds of pages with documentation, nobody wants to update it because it’s boring, difficult and need time which cannot be
Several sets of goal criteria which help to make it clear and be achieved. Just a reference to remember. SMART S = Specific (context bound goal within defined scope of work) M = Measurable (easy way