[GEEK HUMOR - except it's true] Programming Sucks

2,023 views
Skip to first unread message

Darren Munt

unread,
May 3, 2014, 9:01:01 PM5/3/14
to intoitsap...@googlegroups.com

“… everything is broken because there's no good code and everybody's just trying to keep it running. That's your job if you work with the internet: hoping the last thing you wrote is good enough to survive for a few hours so you can eat dinner and catch a nap.”

 

http://stilldrinking.org/programming-sucks

Carsten Eckelmann

unread,
May 3, 2014, 10:25:03 PM5/3/14
to intoitsapphirecoast
Thanks Darren,

I feel totally vindicated by this article. All our clients and employers should read this. Also everyone who wants to tell me about the new standard this or paradigm that should read this and take to heart ... EVERYTHING in IT sucks ... there are no exceptions ... except for this small beautiful piece of Lisp code I wrote back at Uni which could count words ...

But I also feel bad now because I understand this: s/camel/_/

Also this can't be stressed enough: "And that's just in your own chosen field, which represents such a tiny fraction of all the things there are to know in computer science you might as well never have learned anything at all. Not a single living person knows how everything in your five-year-old MacBook actually works. Why do we tell you to turn it off and on again? Because we don't have the slightest clue what's wrong with it, and it's really easy to induce coma in computers and have their built-in team of automatic doctors try to figure it out for us."

Beware anyone who wants to convince you that they know "everything about computers".

Kind regards,

Carsten Eckelmann



On 4 May 2014 11:01, Darren Munt <dar...@ardex.com.au> wrote:

“… everything is broken because there's no good code and everybody's just trying to keep it running. That's your job if you work with the internet: hoping the last thing you wrote is good enough to survive for a few hours so you can eat dinner and catch a nap.”

 

http://stilldrinking.org/programming-sucks

--
You received this message because you are subscribed to the Google Groups "IntoIT Sapphire Coast NSW - an informal IT and Business social networking group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to intoitsapphirec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Darren Munt

unread,
May 3, 2014, 10:30:30 PM5/3/14
to intoitsap...@googlegroups.com

> I also feel bad now because I understand this: s/camel/_/

 

I was hoping someone could explain that!

 

Carsten Eckelmann

unread,
May 3, 2014, 10:39:50 PM5/3/14
to intoitsapphirecoast
This is a substitution command string for the unix stream editor (sed). It is also used in the much more popular vi editor.

s/camel/_/

means: s = substitute / {what to find} / {what to substitute with} / {additional options}

The command as it was written in the article is incorrect in so far as "camel" would be taken literally and in the example the string "camel" was not present in the subject text "arrayReverse".

Instead the "camel" implies that "arrayReverse" is written using a convention called "CamelCase" which hints at the visual appearance of words with internal capital letters as looking like the humps on a camel.

The command then expresses that the correct syntax for the array reversing function is not "arrayReverse" but "array_reverse", the camel case substituted with an underscore.

....

I think I may be beyond saving ....

Kind regards,

Carsten Eckelmann



On 4 May 2014 12:30, Darren Munt <dar...@ardex.com.au> wrote:

> I also feel bad now because I understand this: s/camel/_/

 

I was hoping someone could explain that!

 

--

Darren Munt

unread,
May 3, 2014, 10:48:02 PM5/3/14
to intoitsap...@googlegroups.com

Well of course! Now that you explain it, it makes perfect sense.

 

Reply all
Reply to author
Forward
0 new messages