Phrases that should set off an alarm in every software developers brain (blog.jonasbandi.net) 18 points by jbandi 16y ago ↗ HN In software development there are some requirements that should immediately trigger all available bells in your subconscious alarming system...
[–] bhousel 16y ago ↗ "This will probably never need to change"also"Nobody would ever want to enter something like that / use the system in that way"
[–] mustpax 16y ago ↗ Seems a little bit light on content. Yes, these are alarming phrases, but just listing four phrases does not necessarily make a noteworthy article.
[–] jws 16y ago ↗ "The multimaster replication will fail if two sites edit the same <redacted> at the same time, but that would never happen."
[–] jselzer 16y ago ↗ "Working with that library will take too long, we can do this faster if we just write it ourselves"
[–] diego_moita 16y ago ↗ "We don't have time to do automation / refactoring / code reviews now. Just make it work and leave it for later."
[–] dkarl 16y ago ↗ "Stop worrying about the users; if they want to keep getting paid, they'll use it."
[–] regularfry 16y ago ↗ "The client has agreed the ship date; I'll need your estimates by next week."
[–] locopati 16y ago ↗ "We're going to update one of our dependencies - it's just a minor dot release"
14 comments
[ 3.0 ms ] story [ 45.8 ms ] threadalso
"Nobody would ever want to enter something like that / use the system in that way"