Foresight rocks (or, laziness as a career-enhancing move)
So, the vice-president looks in to my office and says, “We had a really good show at $tradeshow. So good that we sold out of books. So we told some people we’d extend the web-ordering discount on our site for another month so they could get the show discount. Can you do that?”
Five minutes later, I look in to his office, and say, “Sure, it’s done.” Because a year and a half ago (or so), I let my laziness guide me.
See, I’ve learned that hardwiring things only creates headaches for me. With a small company, you can change a policy by talking to two or three people, which means you can turn on a dime. That also means I could have fifteen little requests to tweak stuff on the website on a daily basis. Hand-coding those changes (hardwiring them) means that I get snowed under by this sort of thing. So sometime around the first time I was asked to implement a discount process for the website, I hardwired it first (so it was working,) then went back and re-did it so that anything that could possibly be manipulated (discount rate, date range, range of titles it applies to, precedence, whatever) was a database field, and the discount process got everything from the database. Because basically, I’m too lazy to hand-code all that stuff every time someone asks.
The “spring discount” ended last night, whenever the server’s clock rolled over midnight. (Something else to consider—that server’s clock doesn’t bear much relation to any actual location. It seems to have its own uninhabited time zone in the mid-Atlantic.) But with one database query this afternoon, it was extended to the end of July. And, because I’m lazy, I look good because I can make changes that quickly.
I tell you—Laziness, Impatience and Hubris. I’ll make it yet. Now, about that final project…
Update: How did I let myself write, “was lazy”? It’s the last day of class and I haven’t written the final paper…
Now playing: Little Wings from Five Stories by Kris Delmhorst