Custom command line shortcuts with Doskey

I’ve learned this nice trick from Petr Horáček aka Besir while working on Nakamotox. So the credit goes to him. You can define custom commands via doskey (only on Windows) and then invoke them via command line. It is quite powerfull, because you can define alias for command with predefined attributes, so it save you lot of repetitive typing. Steps: Open any text editor and define your shortcut commands @echo off REM example shortcut for docker-compose doskey dcdu=docker-compose -f docker-compose-dev.yml up doskey dcdd=docker-compose -f docker-compose-dev.yml down Add path to file with commands to registry: open regedit go to \HKEY_CURRENT_USER\Software\Microsoft\Command Processor define AutoRun enter path to …

Continue Reading

Proč vám to tak trvá?

Můj překlad vtipné a výstižné odpovědí na zásadní otázku, proč jsou softwarové projekty téměř vždy tak brutálně pozadu. Originál zde: http://www.quora.com/Engineering-Management/Why-are-software-development-task-estimations-regularly-off-by-a-factor-of-2-3 Krásná analogie Pojďme na pěší tůru ze San Fransica do Los Angeles za kamarády. Půjdeme podél pobřeží a na mapě vypadá trasa následovně. Cesta je dlouhá zhruba 400 mil, průměrná rychlost chůze jsou 4 míle za hodinu, takže když půjdeme 10 hodin denně, tak za 10 dní tam dojdeme. Ne? Jednoduché kupecké počty. Zavoláme kamarádům, ať rezervují místa v restauraci na příští neděli v 18h večer, oslavíme náš triumfální příchod. Kamarádi se už těší! Druhý den hned ráno vyrážíme na …

Continue Reading

Asshole Driven Development

I’ve recently stumbled upon a book called “Say no to assholes” (Link to blog post in Czech) and it immediately reminded me of my past job. I don’t want to slander anyone, I just want to share it as a warning and encouragement. I worked there for about a year, which is enough time to know how Asshole Driven Development works. Basically there is an asshole in the leading position demotivating everyone. What is surprising about it is that although employees complain every day, lot of them stays in the company. They are under motivated, pretending to work and their boss is pretending to pay …

Continue Reading

Why not to work overtime

If you get some amount of work done in 8 hours, will you get done double if you work 16 hours?  This is of course an extreme case, nobody can work for 16 hours and still maintain focus. But some manageres and developers do think that when in need they should work long overtime hours.  The project is almost reaching its deadline, but it is far from being finished. Your boss or your client (or even yourself) urge you to get it done ASAP. So you decide to get up very early and go to bed very late, in order …

Continue Reading

The value of beautiful code

During my rather short period of Pair Programming I have learned something valuable, but there is also something I’ve learned after that. Michal Tehnik left the company and I continued to work on code we wrote and then refactored and polished together several times. It is probably the best piece of code we have now in our code base 🙂 We did not have the time to finish it, so it was my job to that.  I needed to add some need features and fix few bugs. I could have done it in two ways. One way was to do …

Continue Reading

Git productivity tips

During pair programming with my colleague Michal Těhník I watched him using git. Here are few things I learned from him. Use git number Git number allows you to use numbers instead of file names. If you for example need to diff some file, or add it to commit, you no longer have to copy paste the filename or type it by hand. You just type something like “git add 1“. Git number can be combined with other git commands.  For example: git number diff 1 Installation Instructions (Windows) Download files from Github Extract to desired folder Add that folder …

Continue Reading

On pair programming

Several times I programmed in pair and I want to share my experience with it.  What are the main benefits of pair programming? The code is of better quality, because there is always the other person watching over your shoulder and seeing what you have overlooked. Wikipedia says that defect rates are about 15% to 50% lower. There is a synergy of ideas. When you work on your own, you might get stuck easily. This rarely happens when working in pair. When you don’t know how to do something, the other probably knows it. Or you start talking about it …

Continue Reading