Scott Sanzenblogger
Erratic Mess

Zen And The Art Of Version 1.1

May 28, 2008 08:42 by Scott

So I'm slammed at work right now.  We've got a tight deadline and limited resources with which to get it done.  Why is it, then, that instead of doing something right the first time, which will even most likely take less time to develop, I still tend to go the familiar (i.e., Basic style might as well be using GOTO everywhere) route and do things the way I initially learned fifteen years ago rather than doing things the right way?  I'm moving more and more towards the right way, but when really pressed for time I tend to do things from a more procedural approach rather than really thinking through the design.  I know it's a constant evolution, and I know I am still pretty new at what I am doing, but still ... you'd think that if I was thinking as I was working on something, "this is not the best way," that I would stop and do things the right way.  It probably has a lot to do with external pressures.  People are waiting on me for work to do.  Others are waiting on me for the job to get done.  I am rushed and, therefore, I am looking to get some work done as quickly as possible.  I'm not sure.  I can't be the only one who does this.

So the bulk of what version 1.1 of the apps will always be for me until I really get to the point where I can do things at least closer to the right way the first time?  Refactoring.


Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Related posts

Comments

May 28. 2008 22:05

Sarah

This actually reminds me of something. When we have a new compound to make as chemists, we do retrosynthetic analysis. We look at the final product and take it apart backwards to determine what compounds to use as starting materials. Is there not a certain "planning" thought process that can be used in your arena when you are presented with a new problem? Just curious.

Sarah

May 29. 2008 08:44

Scott

My entire job, other than management of others, is planning. I come up with an overall design, other people go about making that design into a final product. The planning actually saves time, which is what's frustrating about this "just get it done" attitude that I get. I know that it's probably a time saver to think things through first, but I still get that attitude that I need to get working on things and I need to get other people working on things if I really want to get it done. Then we end up redoing a lot of work and spending extra time with it in the long run. It doesn't always happen, but when you are rushed it can really happen more often because that's often how you learned (deadlines in school). It's just a mindset that I have to get out of so I can focus more about building a quality product in the first place. Hence the title of this post. Smile It's one of those things that improves with practice, like knowing when to stand up and walk around aimlessly to get your mind off shit.

Scott

May 29. 2008 09:13

ryan

That's not fun when the deadlines drive the architecture. I am all for getting things done fast but as you mentioned, a lot of rework goes into the "just get it done" programming. Sounds like you're taking the right steps though.

ryan

May 29. 2008 09:46

Scott

Hey, thanks for that. Yeah, I think a lot of it at this point is still just learning and getting better. I think that's key, though ... to keep learning. To take these times and learn from them to improve in the future. Hell, in the present too. I am really still finding out how to balance managing people and getting my tech related work done at the same time.

Scott

May 29. 2008 12:13

kevin

I give you two thumbs up in your effort to continually get better. I do the same thing but my deadlines are not ever set in stone here at the Ritz. I try to plan stuff out, even if it is just a basic outline.

But, I don't have to worry about managing other people too.

I know at least one person that hates to plan and just goes right in and starts to program. As a result, I have seen problems occur near release or on release that could have been prevented if a complete design was done up front. Don't get me wrong, I have planned stuff out and forgot things which bit me in the butt near release. I see problems less often if I plan it out. Plus I have a better understanding of what needs to be done.

now I am rambling...

kevin

Add comment


(Will show your Gravatar icon)  

  Country flag

[b][/b] - [i][/i] - [u][/u]- [quote][/quote]



Live preview

January 7. 2009 06:16