3 ms·

I mean the problem is that you're both probably right. You SHOULD add in tests and security, but you also very likely DON'T have time. Good code can be structu

I mean the problem is that you're both probably right. You SHOULD add in tests and security, but you also very likely DON'T have time. Good code can be structured in a way that it's not going to be a nightmare to add in considerations of this nature further down the line, but with this sort of environment of "speed > everything" else, they're not likely to let you implement code well either.

gozur88 9y ago
>I mean the problem is that you're both probably right. You SHOULD add in tests and security, but you also very likely DON'T have time. But by doing the things that people can see and skipping the things they can't see you're effectively just lying when you produce a schedule. You don't do automated tests because it's a fun way to kill a Friday afternoon - you do them because they free you up to work on new functionality. So you're not really saving yourself time by not doing them. These kinds of projects are almost always disasters. Invariably the problem is someone in middle management undersold the cost to the people above him. There's not enough time to write the app properly, so they borrow time off the end (with interest) to make it look like things are progressing to the deadline. So you finish the first 90% on schedule and then flail around on the next 90%.