Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "pedantry"
-
Golang tutorials trying to explain the difference between concurrency vs parallelism be like "Oranges are different from oranges. Oranges are juicy while oranges are juicy. They are not to be confused, u newb"1
-
Correction: oligarchy, not "democracy".
Unless you mean it in the classical sense of the word, where "people" is not as broad a term, given how **citinzenship** was an exclusive status in the ancient city-states that developed these concepts.
However, even in that case -- which I find highly unlikely -- I'd argue that oligarchy is equivalently if not moreso applicable as an accurate description of said form of government.
Every few years, you (probably) go and vote _not_ for whomever better represents your interests, but rather for whomever seems to be the lesser evil: the 'best of the worst', if you will, out of a series of horrible candidates you absolutely do not trust.
That is undemocratic; no semblance of power is vested in us, much less "supreme power", and we cannot speak of anything even remotely alike to popular sovereignty within this context. By which I mean, we have overlords rather than "representatives".
And this, altogether, does beg the question: why do we parrot these terms as if they were ever a faithful description of anything? Have we no capacity for language, perhaps?
Appropriately enough, it's bollocks all the way down. -
Poorly built software is the other side of the coin of over-engineered software. They both exist because users carelessly use software products. By not exercising the code enough, or system failure not costing the business more penalties than they can bear, incompetent developers will continue to get away with building things haphazardly –not as relates to tech stack, but the nitty-gritty implementation details they gloss over without adequately thinking through
Because of this, there doesn't seem to be sufficient incentive for thorough planning –what could be referred to as over-engineering. Those fancy pedantry in code mostly goes unnoticed by the end user. Of course, this doesn't apply to big corporations in most cases. It's usually unexpected to see elementary bugs in them3