Anti Mediocracy Manifesto for Software Development
61–70 of 110 posts
Re: Anti Mediocracy Manifesto for Software Development
#62Re: Anti Mediocracy Manifesto for Software Development
#63Re: Anti Mediocracy Manifesto for Software Development
#64I'll never understand comparing code to art. Not the first time I'm seeing it but for me it couldn't be further apart. There is no best way to make a drawing. There is no best way to make a movie. There is no best way to tell a story. There is no best way to make a painting. There is no best way to create a song. ... There is (almost?) always a best way to do a piece of code. Code has nothing to do with emotions. I'm…
Re: Anti Mediocracy Manifesto for Software Development
#65While 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…
> all natural distributions follow that curve No, they don't. Many approximate that curve. Others do not. For examples: "Bimodal distribution of flowering time in a natural hybrid population of daylily (Hemerocallis fulva) and nightlily (Hemerocallis citrina)" - http://link.springer.com/article/10.1007%2Fs10265-005-0241-3 . http://psychology.wikia.com/wiki/Bimodal_distribution lists other bimodal distributions: "the…
Re: Anti Mediocracy Manifesto for Software Development
#66Re: Anti Mediocracy Manifesto for Software Development
#67While 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…
But surely the purpose of the manifesto is to skew that curve to the right.
Re: Anti Mediocracy Manifesto for Software Development
#68While 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…
It's a choice, not a lifestyle.
Full enlightenment, or being a Buddha, is the realization all of this around you is Buddha Nature. Each individual is capable of attaining enlightenment in a single moment, given choice is made in very similar moments throughout the day. When you decide to believe it, you do so in a timeframe that is non-measurable. Like many people I know in SV, I believe we're running in a simulation. This belief could be viewed as equivalent to a type of enlightenment.
On the other hand, saints are beyond this reality and are "holy" in nature. Holiness means they have been re-integrated with the supreme wisdom, or all knowledge. Some call it the fucking oneness. Aldous Huxley called it the "burning brightness of unmitigated Reality". Technically, they are enlightened, but they are outside what we HERE can consider as Buddha Nature.
I liken these two concepts to security through obscurity. We don't know the proper protocols to realize that we are all the same thing and refuse to think about the fact we'll all be reintegrated into the brightness when it comes for us.
Re: Anti Mediocracy Manifesto for Software Development
#69For that matter, manifest != manifesto.
Probably English isn't the author's first language. I should forgive him and carry on, but a quick scroll reveals the words idiot and whiskey. TL;DR
Re: Anti Mediocracy Manifesto for Software Development
#70Earlier quoted context omitted.
you missed the point: The point is, if the requirements for a piece of code are so complex that you NEED to write a requirement analysis, that you NEED to do anything other than plan out your code, and write it, than your software is already too complicated. You need to narrow the scope. Lots of small systems is better than one large system.
There are domains wherein the software is inherently this complex and requirements analysis is unavoidable. This is particularly true when decomposing one large system into small systems. Someone needs to be the systems engineer that determines how the pieces couple together and how overall system functionality is divided into the pieces. Requirements analysis is also critical when the software is coupled to particul…