Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Re: Enterprise development: Its ok to say No!

by Abigail-II (Bishop)
on Dec 16, 2003 at 13:17 UTC ( [id://315048]=note: print w/replies, xml ) Need Help??

in reply to Enterprise development: Its ok to say No!

But I've come to the conclusion that its only the profi that I want to be and work with.

That's a short sighted view, and isn't acceptable in the long run. Topping the 'profi programmer' is the programmer who can shape shift from one class of programmer to another, and knows when to be what kind of programmer.

Anecdote: I work for a company that has written software since the early 70's (I've coworkers that have been with the company or its predecessor for 30 years). I work in a department that is actively maintaining software that was written in the 70's (lots of FORTRAN and Pascal code) - part of the software is an OS that was initially written in PDP assembler, was later emulated on top of VMS, SCO, and is now running on top of Linux and Windows; where it runs as a secondary OS. We know all about portability, extensibility and maintainability.

We recently had a problem. As part of the nightly back procedure, the secondary OS calls a Linux program. This program does some mounting and umounting of disks hanging off fibre-channel devices and then queries /proc to get an impression of what disk are available. Due to a bug in the fibre channel driver, once in a blue moon, this generates a kernel oops, causing the kernel to kill the program, which in turn causes the secondary OS to dump and restart itself. For a particular customer, this was reason to not take a new release into production.

There were several ways of approaching this problem. The 'profi' programmer approach would be to dive into the driver sources try to find the problem, and fix the driver. The problem is, you can't estimate how long it's going to take, as it requires to become familiar with the driver. The 'happy customer' programmer approach is to write a wrapper around the program that causes the kernel oops, which just restarts the original program if causes an oops.

In the end, we did both. I wrote a shell script wrapper, and we send that to the customer the next day. Customer happy. Later, we ripped a newer version of the driver out of a newer kernel and implanted it in the kernel we're working with, and luckely that fixed the problem.

What I am trying to say is that the bigger picture is important. Maintainability, portability, extensibility, it's all important. But in the end, what's really important is (happy) customers. If your customers aren't happy - they leave. If they leave, your product can be fantastic, you won't survive. A good programmer balances the customers wishes and the development group wishes into an ideal blend.


  • Comment on Re: Enterprise development: Its ok to say No!

Replies are listed 'Best First'.
Re: Re: Enterprise development: Its ok to say No!
by maverick (Curate) on Dec 16, 2003 at 17:55 UTC
    I see that as not so much of a 'shape shift' as 'knowing when a quick hack is the acceptable short term solution'. It's like saying, "this will keep you up and running for the immediate future, BUT it is not a proper solution"

    It's more like the profti is a superset of the qualities other types rather than a different species all together...

    The true headaches begin when the PHBs on a project try to coerece a Profti into a HCP because their ideas are poor and s/he isn't 'yes man'ing enough. /me winks at jeffa

    OmG! They killed tilly! You *bleep*!!

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://315048]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (4)
As of 2024-04-19 21:05 GMT
Find Nodes?
    Voting Booth?

    No recent polls found