News for hackers. Stuff that matters.
Re:Performance Excuses Debunked by onion2k on Thursday April 27, 2023 @10:59AM (#35729141)
you're an incompetent programmer

The problem with this line of reasoning, eg "if you write slow code you're incompetent", is that it applies to everything that programmers do - if you write slow code you're incompetent, if you write buggy code you're incompetent, if you write undocumented code you're incompetent, if you write untested code you're incompetent, if you write code slowly you're incompetent, if you write code that doesn't fulfil all the requirements perfectly you're incompetent, and so on for each and every measure someone dreams up to measure how good code is.

You'll very quickly find there are no competent developers.

Re:Performance Excuses Debunked by li4ick on Thursday April 27, 2023 @11:05AM (#35729247)
I mean, sure, this comment sounds nice on a web forum, but some of us have 0 hesitance bucketing others on a scale of competence. Looking at the state of software I interact with on a daily basis, I really don't care about being nice anymore.
Re:Performance Excuses Debunked by onion2k on Thursday April 27, 2023 @11:21AM (#35729471)
some of us have 0 hesitance bucketing others on a scale of competence

Sure, and what I'm saying is that there are many scales, and all of us are at the incompetent end of some of them.

Re:Performance Excuses Debunked by marcosdumay on Thursday April 27, 2023 @04:50PM (#35734375)
> some of us have 0 hesitance bucketing others on a scale of competence

Yeah, people like that exist... That has a strong and reverse correlation with competence.

Re:Performance Excuses Debunked by li4ick on Thursday April 27, 2023 @08:14PM (#35736087)
This makes absolutely 0 sense.
Re:Performance Excuses Debunked by brhsagain on Friday April 28, 2023 @01:33AM (#35737788)
The flaw in this point is, there are really only a handful of measures that actually matter: writing performant code, shipping quickly, delivering business requirements (really this is an official sounding way of saying "doing the actual thing the program needs to do"), and eliminating bugs.

The other things are just proxies for the real measures, that people made up, and in fact are often harmful to the main goal. Like "documenting code" and "writing tests" a lot of the time are just cargo culting to make people feel like they're being responsible and following "best practices" without actually improving the measures that matter. I think that the other unlisted metrics in your "every measure someone dreams up..." are likely to fall under this category.

There aren't an infinite number of possible measures like you're suggesting, there's a finite number and a rather small number at that. You can definitely be really good or really bad at quickly shipping performant bug-free code that does its job. The problem in this debate is that one side is completely ignoring one of these categories, and trying to claim that it's because they have to focus on the other categories, and that this is just an inevitable tradeoff, rather than that we lack the skill as an industry to do all of these things at an acceptable level. Being a good programmer may have more variables than being a good chess player, but I think the claim that there's no such thing as programming competence reductios to absurdum pretty quickly.

Re:Performance Excuses Debunked by jskdndkfm on Friday April 28, 2023 @02:42AM (#35738213)
100%. Just claim that documentation and tests are cargo cults, take up previous cpu and memory like it’s 1985, and pretend that your shite, undocumented, unmaintainable, untestable, shift-right code is perfect.

Working with your type sucks. Confidently incorrect all the fucking time.