Re:I Launched My Startup Yesterday, This Is How The Hectic D...
by makira on Tuesday January 24, 2012 @03:34PM
(#3506610)
Whenever I push a new version of an app, I always do it in the morning after having slept a good night.
It's very important to be alert and able to react in case something goes very wrong. Launching after being up 20 hours is taking risks for no reason.
Re:I Launched My Startup Yesterday, This Is How The Hectic D...
by james-fend on Tuesday January 24, 2012 @03:53PM
(#3506718)
Live and learn. I prob won't make that mistake again as I just woke up from a crash nap and trying to catch up on blog comments..
Why would James launch at 5:30 AM after getting no sleep? This sounds like a good way to make mistakes, make it hard to keep up with issues that come up, and generally make the day seem hectic when it maybe didn't need to be (and in fact wasn't). Was there a mission critical launch deadline? Were there key users to be gained at 5:30 AM? Instead, he took a three hour nap during business hours, with emails and bugs accruing that needed "immediate attention".
In fact, it doesn't sound like a very hectic day to me at all. A three hour nap in the middle of the day? An hour long victory lunch? Those sounds like the wonderful rewards of having a flexible (read: no) schedule. James worked hard leading up to the launch day, for sure. But on launch day, he spent one to two hours writing two emails, and one hour fixing a certificate bug. 3 hours. The rest was spent refreshing logs and being excited. Fun! Not hectic.
Aptly, "THE DAY'S RESULTS" is a large, prominent chart with... one data point.
What am I supposed to be interested in here?