Ranter
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
Comments
-
One could criticise the first paragraph for not including women without attempting to understand it. That invalidates the whole idea.
-
Disagree that a spec should be created before a program in all cases. Might have been sensible back in the day, but not now.
Clock cycles are not more valuable than my time. -
@AlmondSauce: The creation of specifications facilitates re-writing programs when programs are written poorly, as well as ensuring that the program functions as intended.
For all programs, that a program is used by millions of men implies that the performance of this program should be maximised. Some companies, e.g., Google, have failed to maximise the performance of computer programs. -
@varikvalefor it's interesting that the meaning of the word has changed from gender neutral to usually meaning an adult male. But it doesn't matter which way you meant it: my point remains either way.
-
Am I just retarded. I can't make sense of first two paras grammatically. It just fucks with me so hard.
-
@3rdWorldPoison it's not easy reading but it's not fucked up either. You need to concentrate a little to understand it.
It says that you can compliment anything you don't understand, but to critique something, you must at least try to understand it.
You critiquing it for being hard to understand means that you tried to read it.
Related Rants
For all things, for all men, that a man compliments a thing does not imply that this man at least attempts to understand this thing. However, for all men, that a man criticises a thing implies that this man at least attempts to understand this thing.
For all computer programs, that a computer program is terrible implies that scrapping the current implementation of this computer program and beginning anew may be the best method of fixing this computer program.
With few exceptions, for all programming languages $l$, given sufficient effort, $l$ source code can be human-readable.
The UNIX philosophy never became outdated.
For all computer programs $p$, $p$ should be written sufficiently well that the author of $p$ can be prideful of $p$.
For all computer programs $p$, a specification for $p$ should be written before $p$ is created.
For all good computer programs, a good computer program can run on terrible hardware.
Every clock cycle is valuable.
rant
programming
advice