Timeline for Thousands of errors!
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2016 at 15:10 | audit | First posts | |||
| Jun 29, 2016 at 15:10 | |||||
| Jun 21, 2016 at 7:33 | comment | added | tsuma534 | @FlorianPeschka I was amused when I saw that in one of our older projects the filepath was correct just because someone mistakingly used $_SREVER instead of $_SERVER | |
| Jun 21, 2016 at 7:31 | comment | added | Ewan | security holes do complicate the question significantly. As you say, you are probably legaly required to fix these. But what if they are known about and signed off as acceptable? | |
| Jun 20, 2016 at 20:54 | comment | added | Jules | +1 - mostly. The only thing I disagree with is that you have a missing item in your list: unreported security errors. I have never seen an application of the type described that doesn't have at least 1 if not actually hundreds of security holes (the last time I worked on a site that looked like this, each and every one of hundreds of pages contained SQL injection bugs). These should be fixed on discovery without requiring specific clearance for each and every one - get blanket clearance for all of them. | |
| Jun 20, 2016 at 16:46 | comment | added | NoseKnowsAll | @Ewan I think it would be worthwhile to highlight "On a legacy app which is going to be replaced" in your answer. I agree with what you said if the system will soon be replaced. However, on a legacy app that will still be used for several years/decades, I think it is laudible to improve the overall codebase (if not to make your job easier, then to make the job for the next guy easier). | |
| Jun 20, 2016 at 14:09 | comment | added | Nzall | @GER In this context it actually is a viable tactic. The web app is being deprecated in a few months anyway, so any effort invested in trying to improve it beyond fixing bugs would be better spent on fixing more bugs. | |
| Jun 20, 2016 at 13:58 | comment | added | GER | @NateKerkhofs I was hoping that stood for a technical term, but that makes sense to just get the requests done. | |
| Jun 20, 2016 at 13:33 | comment | added | Ewan | like aglie but more so | |
| Jun 20, 2016 at 13:22 | comment | added | Nzall | @GER "Just [expletive] Do It" which means to eschew normal standards and testing and other things and just get a fix in without caring whether it's done in a maintainable and readable way. | |
| Jun 20, 2016 at 13:08 | comment | added | GER | Please clarify ... JFDI ... | |
| Jun 20, 2016 at 9:38 | comment | added | Dennis Jaheruddin | Indeed be very cautious in what you touch, This immediately came to mind: xkcd.com/1172 | |
| Jun 20, 2016 at 8:04 | comment | added | F.P | "mistakes which are now features" - oh, the joy... | |
| Jun 19, 2016 at 14:57 | history | answered | Ewan | CC BY-SA 3.0 |