4 ms·
> Your job is supposed to be hard. you're an engineer! Please consider the consequences of your actions. My clients pay my wages and they are the ones who choo
by andybak 11y ago
> Your job is supposed to be hard. you're an engineer! Please consider the consequences of your actions.
My clients pay my wages and they are the ones who choose what my priorities should be. Where are these mythical developers who get to choose how long to spend on optimising working code without any financial imperatives? Outside of hobby projects there's always someone counting the pennies.
- amag 11y agoOnly in this specific case it's exactly one line of code. Unless your hourly rate is obscenely high it is essentially a free optimization.
- verytrivial 11y agoI agree, but this is a moral imperative, not a financial one. And before you say "it's immoral to spend the client money on things they don't want", you're right. Your job is to convince the client it is "worth" it.
- 746F7475 11y agoSo, what have you done to improve the situation?
- andrewingram 11y agoMy philosophy: As a professional, you should always consider the user of your product to be your client, whether they're paying you or not.
- bobwaycott 11y agoAs a consultant, my clients do not dictate at all what my priorities should be. I work with them to identify what their priorities are, what they'd like to see done. I train them to value performance and quality, not the lowest bottom line. I also train them to learn how to identify performance and quality. I give them feedback on their ideas/priorities, and always include my own suggestions for platform/software maintenance/improvement/enhancement. I'm their consultant and vendor, not their employee. I probably take this to a weird degree for some, but I actively think about my client's software quite often, and frequently toss ideas their way whenever they hit me. You'd be surprised how often those ideas--which I thought were cool, hence the sharing--come back later as something they want. It's just basic sales. Of course, I'm always building large, custom projects from scratch, not taking on projects that ask me to optimize "working code without any financial imperatives". On the other hand, when I identify a part of their software that can gain performance or some other kind of improvement—say, some dependency has improved that will ease X, making priorities Y and Z easier to implement—they listen to me and put it in their list of priorities. Everybody wins.