←back to thread

177 points foxfired | 1 comments | | HN request time: 0s | source
Show context
charlie0 ◴[] No.43618176[source]
This is exactly what happens when Product completely takes over the dev. team and they aren't given any control over their craft. Dev. team should always have x% amount devoted to things by devs for devs.
replies(1): >>43618226 #
bb88 ◴[] No.43618226[source]
Fixing other's shitty code doesn't push the needle -- particularly in an industry that strives to get customers to open their wallets and shell out hard currency.

If a company's ultimate goal is to extract money from people, then developers who can extract money faster (even if their rendering/loading algorithms suck) will get rewarded better than those who don't.

That's why enshittification is a thing (and actually come to think of it, not new either). It might be a dev that learned from product leadership that, "I could fix these 13 lines of code. But you know, our company could also sell a 'PRO' version subscription for $5 a month which provides the fix..."

replies(1): >>43618272 #
Spivak ◴[] No.43618272[source]
Yeah, it's sad but this is the reality. Caring about your craft is for your passion projects / hobbiest endeavors. Once your beautiful software meets the reality of the real world and business it all falls apart— you can either take a mindfulness approach and just come to accept it or let it drive you mad.

The goal is to write not-bad code. You're not trying to do shoddy work on purpose but good enough is good enough.

replies(4): >>43618538 #>>43618949 #>>43619135 #>>43622986 #
1. int_19h ◴[] No.43618949[source]
It doesn't have to be this way, though. We as a society choose to accept this state of affairs. Should we?