14 comments

[ 3.0 ms ] story [ 45.8 ms ] thread
"We'll be integrating everything at the end, just make sure your bit works"
"This data contract won't ever change..."
"This will probably never need to change"

also

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

Seems a little bit light on content. Yes, these are alarming phrases, but just listing four phrases does not necessarily make a noteworthy article.
"The multimaster replication will fail if two sites edit the same <redacted> at the same time, but that would never happen."
"Working with that library will take too long, we can do this faster if we just write it ourselves"
"We don't have time to do automation / refactoring / code reviews now. Just make it work and leave it for later."
"I read about this cool new language in beta...."
...and make it secure.
"Stop worrying about the users; if they want to keep getting paid, they'll use it."
"It will be done early next month."
"The client has agreed the ship date; I'll need your estimates by next week."
"The system must be completed tomorrow."
"We're going to update one of our dependencies - it's just a minor dot release"