4 ms·
you stated the condition/assumption - that the goals are orthogonal I believe these are not - researchers publishing how to create good software and developers
by ikari_pl 2y ago
you stated the condition/assumption - that the goals are orthogonal
I believe these are not - researchers publishing how to create good software and developers creating software may be seen as goals as aligned as fixing an incident and publishing a post mortem, or as writing an RFC and implementing it. Or publishing a post on how you remodeled your infrastructure.
They diverge at some point, yes, but that's not orthogonal at all
- Kamq 2y ago> researchers publishing how to create good software I disagree that this is what researchers are doing (at least from my point of view). This is actually an area where I agree with the article, there's a gigantic gulf between researchers and practitioners. The things that academia puts out are not, generally, what I would consider to be good software. I think this fundamentally comes down to a difference in the definition of "good" between the two camps. So far as I can tell (not being an academic), the academic definition of "good" seems to revolve around software having certain provable characteristics. My definition of good software involves the software exhibiting useful characteristics. And those are, generally speaking, orthogonal. If not sometimes inhibiting each other. But, of course I would think this, I'm a practitioner. The academics probably have similar complaints about me.
- bryanrasmussen 2y agoI can see this is going to be one of those HN discussions that goes back and forth forever, maybe somebody should do some research on how orthogonal the goals really are!