3 ms·
I realize we're beating this to death, but so what. It's never my priority, it's always my customers' priority. Here's my life right now: Customer is opening
by edw519 19y ago
I realize we're beating this to death, but so what.
It's never my priority, it's always my customers' priority.
Here's my life right now:
Customer is opening new warehouse in 2 weeks and calls me to change whatever software needs changed to split orders to print in the appropriate warehouse. I agree because I'm a masochist. I find 15,000 lines of code to do what I (and you too, probably) could have done in less than 1000. Most of it was clearly written by someone who had no idea what they were doing, much of it is never accessed, much of it has never run properly, and I have to do something. I rewrite what, in my professional opinion, must be rewritten. I workaround what I can, and I add what I need. I want it to work right the first time and I never want to come back (until new business requirements come along). I am usually very successful doing this, making changes during unit and system testing and finishing in a day or two.
I use to be bitter about cleaning up other peoples' mess because they were too lazy, stupid, rushed for time, or whatever. But no more. I've turned around my thinking to use all of this as a motivator to build solid business apps where no one ever has to go though this again.
<closing loop...> THAT'S what has motivated me to do my start-up.
I threw out my original example because it's a classic, it came to mind quickly, and most readers here, even the juniors, could understand it. I had no idea it would spawn such discussion. Nice talking to you.
- derefr 19y ago> I had no idea it would spawn such discussion. There's a good indicator that something will spawn a heated debate, and you pointed it out yourself: > and most readers here, even the juniors, could understand it. It's a bikeshed.