5 ms·

> If your business doesn't need step 2, then what are we complaining about? Hacky, non automated, low quality, not tested, hard to maintain, slow code. Remembe

> If your business doesn't need step 2, then what are we complaining about? Hacky, non automated, low quality, not tested, hard to maintain, slow code. Remember, we are at step 1 of "First do it, then do it right, then do it better." Business rarely needs refactorings and performance improvements, until they do, and things turns really ugly when they do, because they've been focusing on shipping "good enough" crap instead of focusing on the actual "continuous improvement" they claim to do.

hbrn 4y ago
> Hacky, non automated, low quality, not tested, hard to maintain, slow code Have you seen truck drivers complaining they are forced to drive old trucks and not brand new Ferraris? If low quality code gets shit done, why would company invest into high quality? Delivering goods in Ferraris might be hell of a fun for drivers, but it's a stupid decision for a trucking company. How confident are you that your high quality will pay off? When exactly will it pay off? How confident are you that your measurement of "high quality" is not biased? How confident are you that your teammate's perception of "high quality" is not just chasing new hype? > Business rarely needs refactorings and performance improvements, until they do, and things turns really ugly when they do Sure, and that's why it's your job to prepare for it. Not by creating "high quality" code in advance, but by creating low quality code that is malleable.
- TurboHaskal 4y ago
  > Have you seen truck drivers complaining they are forced to > drive old trucks and not brand new Ferraris? No. Where I come from, truck drivers own their own trucks and are pretty happy about them. What they do complain about, however, is people telling them how to do their job. > Not by creating "high quality" code in advance, but by > creating low quality code that is malleable. Nah, I don't think I will. You can have fun maintaining low quality code. I'll just move somewhere else where these instant gratification, feature oriented "minimalist software engineers" are challenged and cannot smear their spaghetti code in whatever they touch.
  - hbrn 4y ago
    > Where I come from, truck drivers own their own trucks and are pretty happy about them And you're free to write your own software in whatever way you want. But when you're working for a business, the end goal of your code is to create value, not to brag to your friends about fancy dependency injection framework that you used. > I'll just move somewhere else where these instant gratification, feature oriented "minimalist software engineers" are challenged It's not about instant gratification, it's about building business that can survive in the market. Creating as much value as possible with as little cost and risk as possible, long enough to survive and become profitable. In fact, it is very far from instant gratification: I have a list of 100 items I personally want to do, and I only get to work on 10-20 of those. But today I'm mature enough to realize that my personal wants can be at odds with business needs.

hbrn 4y ago

> Hacky, non automated, low quality, not tested, hard to maintain, slow code Have you seen truck drivers complaining they are forced to drive old trucks and not brand new Ferraris? If low quality code gets shit done, why would company invest into high quality? Delivering goods in Ferraris might be hell of a fun for drivers, but it's a stupid decision for a trucking company. How confident are you that your high quality will pay off? When exactly will it pay off? How confident are you that your measurement of "high quality" is not biased? How confident are you that your teammate's perception of "high quality" is not just chasing new hype? > Business rarely needs refactorings and performance improvements, until they do, and things turns really ugly when they do Sure, and that's why it's your job to prepare for it. Not by creating "high quality" code in advance, but by creating low quality code that is malleable.

TurboHaskal 4y ago
> Have you seen truck drivers complaining they are forced to > drive old trucks and not brand new Ferraris? No. Where I come from, truck drivers own their own trucks and are pretty happy about them. What they do complain about, however, is people telling them how to do their job. > Not by creating "high quality" code in advance, but by > creating low quality code that is malleable. Nah, I don't think I will. You can have fun maintaining low quality code. I'll just move somewhere else where these instant gratification, feature oriented "minimalist software engineers" are challenged and cannot smear their spaghetti code in whatever they touch.
- hbrn 4y ago
  > Where I come from, truck drivers own their own trucks and are pretty happy about them And you're free to write your own software in whatever way you want. But when you're working for a business, the end goal of your code is to create value, not to brag to your friends about fancy dependency injection framework that you used. > I'll just move somewhere else where these instant gratification, feature oriented "minimalist software engineers" are challenged It's not about instant gratification, it's about building business that can survive in the market. Creating as much value as possible with as little cost and risk as possible, long enough to survive and become profitable. In fact, it is very far from instant gratification: I have a list of 100 items I personally want to do, and I only get to work on 10-20 of those. But today I'm mature enough to realize that my personal wants can be at odds with business needs.