Founders Problems
This week we did some amazing stuff at MAXroam which I will talk about in another post but needless to say it was huge, Database changes, server changes, store changes and construction of new Api’s
Obviously the workload was intense.
With this kind of a migration as you know problems pop up all the the time.
Well now we are almost done with only a few more small bugs to squash on Monday.
The team including me have put in almost 20hrs days Tuesday to Friday this week and here lies a dilemma.
No matter how brilliant the team are (and they are) they are never the founder, its not their first born, they have to sleep, rest, live their lives
Whereas me?
I will keep going until its finished 48hrs no sleep? bring it on
Anal attention to tiny bugs? bring it on even further.
I work with an amazing bunch of people who completed some amazing stuff this week, Angelina, Niamh, Chris, Sean, Jason and Jaroslav all of whom went above/beyond the call of duty this week and showed true backbone.thank you so much guys
Me, I am just the idea’s guy.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=66d02d49-17f9-4e2a-adc5-113d1b373a8f)
well the reason they would even consider doing something like that is because you write posts like this. Its only a few words but they probably mean more than anything. It ain’t always about the money to people
Hey, Pat! Listen to your body and watch your health. Your mind might want to run another mile around the pitch but your body needs a break, especially if you’re sweating in the rain–something that tells me I’m headed for a down day.
You continue to give me reasons to watch you and learn from you. They are as lucky to have you as you are to have them
keith
Something which is often overlooked in software developers is their pride. It’s not something that you are ever asked in interviews, it’s not something tangible but it is an important part of a developer.
Most non-techies just know that software developers “work in computers” or “work in IT”. It’s an all encompassing beige box definition.
What people don’t realise is the close relationship between a developer and their code.
Sometimes to make a release date, we’ll hurt our code, by writing something hacky just to make it work. We promise ourselves as soon as it’s been released we’ll come back and fix it properly, as we don’t like to see our code in pain. We want to be proud of our code.
It’s this relationship that makes a release date so special. Our baby, our pride and joy, is going to be presented for all to see. This is why a release is so important to developers.
A release is a public representation of the developer.
There is another aspect to binge working, coming up to a tight release schedule, and that is whether you respect (but more importantly like) your boss.
This could be your development manager or the founder of the company. If you are not respected (but more importantly liked) then it is more than likely that the developers will not put in the extra effort required to get the software out the door, and the project will fail.
So if you manage a team who do put in that extra effort, you can be sure they respect you (and probably like you).
Pat,
luckily it’s not your case.
When you find a developer leaving office everyday at 5.30pm, watch out… Best developers do it for fun and don’t leave the battle field until everything is working fine
@John Great point about pride – something that is frequently absent (not just talking about developers either).