Web Dev: A day in the life
Aaaaaah, it’s over. The marathon is over. And the Marathon is over.
In the world of software design and development, client-driven and event-driven software is the most demanding. That’s what I learned over the past few weeks.
Client-driven meaning you’re interacting directly with clients and you’re trying to meet their needs and keep them happy. That means last minute changes, responding to off the cuff comments and observations. It’s tough. The target is always in motion and essentially there is no end.
Event-driven meaning it’s for an event, an immutable date and time. Whatever you do or have it’s going to work when it’s supposed to or it’s not going to work. Either way, the event will come and go (thankfully, this will be the end).
FRIDAY NIGHT/SATURDAY MORNING
“Do NOT go back to sleep.”
He says when you wake up early in the morning or the middle of the night, don’t go back to sleep. (Once I would wake up at 3:14 every night. I’d wake up, look at the alarm clock and it would be 3:14. Every night for about a week. I’d always go back to sleep. Then one night I woke up at 4:13 and had no more late night wake-ups.) That “wee hours of the morning” time is so quiet. So much creativity flows in the quiet time, sacred time. Make something of it, y’know. He says, “You have an eternity to sleep.”
So I got out of bed and decided to get my wireless router up and running again. The plan being to do all of my race day trouble shooting from home because I had to change a setting at 4pm when the race would end and we’d switch to post-race mode. I was on the phone with Linksys and Verizon technical support for a long while.
They got me up and running and I connected to the work network.
Did some more testing.
4 PM – 10 PM
I fired up the laptop and went to the site for another check. And oh crap! Why was I seeing playback controls? They’re not supposed to show up until after the race. And I couldn’t see the production servers from home.
Anyway, parking wasn’t a problem on a Sunday morning. Parked across the street from work and Leika and I went in. I checked my files and settings and everything looked good. Still getting playback controls, though. Damn. (Later, I figured it was probably caching config files, despite my generated request strings. Or … whatev.)
It went on like that for a few hours. No big trouble but a lot of, “Hey, this thing is doing that. Those numbers look wrong. Maybe they changed something. Yeh, they did. Can you fix it?” Stressful. Leika and I hung out. I didn’t know what I was going to do until 4pm. Not really worth it to go home. Maybe I could nap.
I stowed Leika in the car while I walked somewhere (Five Guys) to pick up lunch. Took her back inside on the way back in. I almost got take-out from Hooters. Didn’t, though.
Got the day off on Monday so I decided to keep Leika for another day. Had big plans to go mtn biking, work on music, do some writing.
All in all, it was a success. I’m proud of how the app turned out. I can send you a link if you’re interested. It’s nice to be doing work that everyone can see. Definitely a learning experience. Next time will be a lot smoother and more stable.