2013-05-05 - Developer's Life 46
-
Ninja-fixing a bug 10 minutes before the demo for client
- s-master
- 792
- 0
-
When a bug goes unnoticed during a presentation
- s-master
- 727
- 0
-
When a friend of mine asks me to fix his website built with Joomla
- s-master
- 983
- 0
-
When a misformed sql query actually returns me the correct results
- s-master
- 786
- 0
-
When a newbie suggests to add a new feature to project
- s-master
- 776
- 0
-
When a thing that worked on Friday no longer works on Monday
- s-master
- 733
- 0
-
When after a big update I test the new site with IE
- s-master
- 702
- 0
-
When after a productive day I'm so confident that I think I can handle parkour tricks on the way home
- s-master
- 676
- 0
-
When asked to lend a hand on a Friday afternoon
- s-master
- 807
- 0
-
When customer wants to change specification 2 days before pushing to production
- s-master
- 689
- 0
-
When I am asked about something from the 900 pages of documentation
- s-master
- 642
- 0
-
When I am asked to continue work of a newbie colleague
- s-master
- 709
- 0
-
When I am the only one to notice a bug on friday night
- s-master
- 757
- 0
-
When I apply a new CSS for the first time
- s-master
- 725
- 0
-
When I did a good job and the client is happy
- s-master
- 719
- 0
-
When I find a solution without searching Google
- s-master
- 653
- 0
-
When I find out that someone has accidentally overwritten my changes in git
- s-master
- 779
- 0
-
When I go off for the weekend while everyone else is still trying to fix bugs
- s-master
- 1.020
- 0
-
When I launch my script for the first time after several hours of development
- s-master
- 6.718
- 0
-
1
-
When I manage to replace 200 lines of the algorithm by only 10 lines
- s-master
- 716
- 0
-
When I notice I was editing production code and I quickly correct my errors
- s-master
- 889
- 0
-
When I realize that I have been blocked for two hours because of a forgotten semicolon
- s-master
- 883
- 0
-
When I return to development of my code that wasn't commented
- s-master
- 747
- 0
-
When I see someone commit 500 files to fix one bug
- s-master
- 653
- 0
-
When I show the boss that I have finally fixed this bug
- s-master
- 771
- 0
-
When I start coding without doing analysis first
- s-master
- 699
- 0
-
When I try a solution without reading the docs first
- s-master
- 724
- 0
-
When I try to fix a bug at 3 in the morning
- s-master
- 803
- 0
-
When I'm deploying code to production
- s-master
- 765
- 0
-
When I'm told that my code is broken in production
- s-master
- 816
- 0