If someday it produces messy but actually reliable code my opinion will change, but at this point, it's just too early (not saying it will ever work, but one can hope)
Certainly you have non-techncal managers that are making more money than you and do you think they do more work? Certainly some do but I doubt all.
Caring about the customer is caring about the product. Caring solely about profit is what enshitifies products.
How is that focusing on the product?
Focusing on the product means solving problems for your customers, exactly what you said they should be doing
You're both arguing for the same thing
I was hoping that dichotomy of sacrificing product for profit or profit for product would help but I'm unsure. Multiple people seemed to have misunderstood but I'm also unsure what was confusing. Frankly I'm having a hard time understanding how they reached such a dramatically different interpretation.
It could be, but it cost my company a billion dollars over almost 10 years (not exact numbers, but close enough) to rewrite our current product from scratch. If you work on trivial projects you can throw away code at will. However for a lot of projects the cost to rewrite is so high that the business cannot afford to throw away code that works. The business needs new features so they can sell upgrades and make more money. The whole reason they were willing to pay that billion dollars over a decade is the old codebase was bad enough that adding new features became expensive and hard - the rewrite was an investment to make adding more features cheaper in the long run.
Which is why engineering a good product is important. People who make the product technically good pay for themselves in the long run when the business gets an idea. This is very important to business as well.
The engineer’s job is to care deeply about the technical aspects of doing well by the customer.
> Care about your customers and what problem they are trying to solve and be involved in figuring out how to make solving those problems a profitable endeavour.
This is, in fact, what I'm arguing for.What I mean by "the product" is making sure it is solving what customers need. And to be clear, by "customer" I mean the people that actually buy it, not share holders.
> All code is throwaway, all code is worthless, solving real needs, wants and pain points for customers is the real source of value.
It is not. You can replace code, but you cannot just throw it away and continue to solve problems. That by definition makes it not worthless.And again, I fully agree we should focus on needs, wants, and pain points. What I'm trying to argue is if you'll forgo that for making profits. Clearly this is what big tech companies are doing. They're shoving in things that are half baked, people don't want, and solve no problems. But they do it because it increases share prices. I'm saying, don't do that
This is the dumbest idea in tech. Please don’t listen to this advice. If you’re just starting your career I’m begging you not to laser focus on coding widgets better for the sake of it.
Care about your customers and what problem they are trying to solve and be involved in figuring out how to make solving those problems a profitable endeavour.
All code is throwaway, all code is worthless, solving real needs, wants and pain points for customers is the real source of value.