i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
@eniko Quite honestly, I'd generally be happy with a piece of software that gets bugfixes and nothing else. The number of time some arbitrary update changes the UI for no reason and throws my whole workflow off...
-
@janxdevil @eniko The Neal Stephenson novel?
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
@eniko I'm ready for "move slow and make sure things don't break" app development again
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
@eniko But then the boss would have fewer people to manage, and be unable to justify his job. Most software changes are about employment for engineers, not necessity. Grr.
As a software engineer I want computer languages and frameworks that stay stable for decades rather than have a new release every year that obsoletes old programs and requires a rewrite. But I don't get to have that :(.
-
@eniko But then the boss would have fewer people to manage, and be unable to justify his job. Most software changes are about employment for engineers, not necessity. Grr.
As a software engineer I want computer languages and frameworks that stay stable for decades rather than have a new release every year that obsoletes old programs and requires a rewrite. But I don't get to have that :(.
-
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
@eniko I'm genuinely considering starting l collection of Android apps with the ethos off "The UI does! Not! Fucking! Change!"
Any feature additions are purely optional and of be default
No nag screens to promote the new stuff
-
@badtux @eniko I actually had to re-write large chunks of a program I wrote for a client because Haskell's ncurses wrapper just kind of... stopped being a thing.
Fortunately, I never liked ncurses to begin with and had abstracted much of it away. The code I'd written was fairly easy to retrofit into brick instead.
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
@eniko can we also get mobile operating systems that get more optimized and less resource hungry with every update so that devices can run for 10+ years before becoming obsolete?
-
i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding
@eniko Product: What's this ticket for, this one you're working on, it doesn't seen to be delivering any new feature? Why are we doing it?
Devs: It lets us delete a couple of thousand lines of no-longer-used code. Which will then no longer need to be maintained, tested, documented, ect ect.
Product: Great! That's what we like to hear!
-
P pelle@veganism.social shared this topic
