Some of you seem to be missing the satire here.
It's well into Poe's Law territory.
Anti Mediocracy Manifesto for Software Development
31–40 of 110 posts
Re: Anti Mediocracy Manifesto for Software Development
#32Lost me here:
"Therefore, our true purpose is to express the intentions of our clients using as little code as reasonably possible, accompanied with lots of documentation and lots of tests (testing code and unit tests don't count as LOC). We should distrust every line of code written by ourselves as well as those written by others. The best code has 0 lines. Because in zero lines of code, there is room for exactly zero bugs."
Less code does not necessarily mean less bugs.
Re: Anti Mediocracy Manifesto for Software Development
#33A manifest against mediocracy in software developer by a PHP developer. Start with dropping PHP. SCNR
Re: Anti Mediocracy Manifesto for Software Development
#34While very idealistic and beautiful in a way as all manifests tend to be, we (along the author) tend to forget certain truths - the middle of the gaussian curve is fattest; all natural distributions follow that curve, and developers are no exception. Most of us, by definition, are mediocre. There's nothing that can be done about it. We should not shun, but rather embrace that. Not by deluding ourselves that if we fol…
Couldn't agree more with this. It's something I repeat at work almost once every week. Look I'm average, most of us at work will be average. The question is how to we design our processes to take that into account? instead of constantly pointing fingers for mistakes that happened.
Re: Anti Mediocracy Manifesto for Software Development
#35Lost me here: "Therefore, our true purpose is to express the intentions of our clients using as little code as reasonably possible, accompanied with lots of documentation and lots of tests (testing code and unit tests don't count as LOC). We should distrust every line of code written by ourselves as well as those written by others. The best code has 0 lines. Because in zero lines of code, there is room for exactly ze…
That depends on how you measure code. If you're talking lines or statements, sure, but if you're talking concepts then the code with fewer concepts expressed must necessarily have less opportunity for bugs, if the number of bugs per concept is held constant.
Re: Anti Mediocracy Manifesto for Software Development
#36Lost me here: "Therefore, our true purpose is to express the intentions of our clients using as little code as reasonably possible, accompanied with lots of documentation and lots of tests (testing code and unit tests don't count as LOC). We should distrust every line of code written by ourselves as well as those written by others. The best code has 0 lines. Because in zero lines of code, there is room for exactly ze…
That depends on how you measure code. If you're talking lines or statements, sure, but if you're talking concepts then the code with fewer concepts expressed must necessarily have less opportunity for bugs, if the number of bugs per concept is held constant.
" The best code has 0 lines. Because in zero lines of code, there is room for exactly zero bugs."
I read it as lines... I agree with what you're getting at, sometimes the concepts are a lot simpler and less prone to bugs when implemented in more lines of code.
Re: Anti Mediocracy Manifesto for Software Development
#37Magnificent, where do i sign?
Re: Anti Mediocracy Manifesto for Software Development
#38Is the proper term "Manifesto"? A Manifest is a list of things included in something, like a bill of lading.
Re: Anti Mediocracy Manifesto for Software Development
#39Re: Anti Mediocracy Manifesto for Software Development
#40While very idealistic and beautiful in a way as all manifests tend to be, we (along the author) tend to forget certain truths - the middle of the gaussian curve is fattest; all natural distributions follow that curve, and developers are no exception. Most of us, by definition, are mediocre. There's nothing that can be done about it. We should not shun, but rather embrace that. Not by deluding ourselves that if we fol…
One solution comes to mind: allow only the people who are >2 sigma above the average to design the software (i.e., be architects), and to do QA.