Hacker News new | past | comments | ask | show | jobs | submit login

A lot of software developers are awful story tellers, and what they end up using for abstractions sounds like something George Orwell would cook up.

And when those developers discover TDD, then their code spends multiple pages saying nothing at all. Oof.

I think deep down most of us intuit that this is a problem. We will persue an articulate but not particularly bright candidate and pass on someone who quickly arrives as the solution without showing any work.

But we let in people with good verbal and poor written skills and they create deserts, their code is so dry. No, I don't want you to explain to me again how great your code is. I just want to be able to follow it without using a debugger. Because maybe this bug isn't even in your code and I just want to make a determination and keep moving.




What's wrong with Orwell's style of writing? I found him to be simple and direct.


I think he meant NewSpeak. But maybe what he was thinking is actually "portmanteau".


No I meant newspeak. If you name everything in an app with noncommittal things and then use them in different spots to mean different things, you end up with code that has to be memorized to be understood.

As someone more eloquent said, they are so afraid of making a bad decision that they try not to make any at all. Everything is named neutral words like 'context' or 'options', the verbs are neutral too, and there are other code flows that use the same name with different data.

As a general rule, if you would describe a code flow out loud in plain English, and not use any of the nouns or verbs that appear in the code, someone has ruined that piece of code.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: