Phrases that should set off an alarm in every software developers brain

blog.jonasbandi.net

18 points·jbandi··14 comments

In software development there are some requirements that should immediately trigger all available bells in your subconscious alarming system...

Seems a little bit light on content. Yes, these are alarming phrases, but just listing four phrases does not necessarily make a noteworthy article.

"This will probably never need to change"

also

"Nobody would ever want to enter something like that / use the system in that way"

"We'll be integrating everything at the end, just make sure your bit works"

"Working with that library will take too long, we can do this faster if we just write it ourselves"

"Stop worrying about the users; if they want to keep getting paid, they'll use it."

"The client has agreed the ship date; I'll need your estimates by next week."

"The multimaster replication will fail if two sites edit the same <redacted> at the same time, but that would never happen."

"We don't have time to do automation / refactoring / code reviews now. Just make it work and leave it for later."

"The system must be completed tomorrow."

"It will be done early next month."

"We're going to update one of our dependencies - it's just a minor dot release"

"This data contract won't ever change..."

...and make it secure.

"I read about this cool new language in beta...."