I know there a bunch of other developers here.
Despite software being tinkered and compiled, like all the time;
someone somewhere has a vested interest in seeing that latest build you are putting together,
with expectations to see maybe a new feature, slick UI, a stat tweak, a satisfying cure to an age old an ailing bug.....
We hit the compile button and the computer locks up, we move away from our desks, stretch for the first time in hours, maybe hit the toilet (and if having a poop have at least - "1 ah-ha moments" of how to improve your code, and maybe hit the cafeteria, for a well-deserved tea-break and gear up for the next round with the code.
So naturally we meet those invested people and we get accosted by the age-old question moments after hitting that compile button.
It's like the equivalent of kids nagging are we there yet on a train journey,
or the buns are in the oven, and everyone is hovering around the oven.....They are going to be too damned hot to eat, you still HAVE to wait even after we take them out.......
Despite software being tinkered and compiled, like all the time;
someone somewhere has a vested interest in seeing that latest build you are putting together,
with expectations to see maybe a new feature, slick UI, a stat tweak, a satisfying cure to an age old an ailing bug.....
We hit the compile button and the computer locks up, we move away from our desks, stretch for the first time in hours, maybe hit the toilet (and if having a poop have at least - "1 ah-ha moments" of how to improve your code, and maybe hit the cafeteria, for a well-deserved tea-break and gear up for the next round with the code.
So naturally we meet those invested people and we get accosted by the age-old question moments after hitting that compile button.

It's like the equivalent of kids nagging are we there yet on a train journey,
or the buns are in the oven, and everyone is hovering around the oven.....They are going to be too damned hot to eat, you still HAVE to wait even after we take them out.......
Last edited: