Warning: Long scary post ahead I’ve written about one application I’ve worked on before here and here. To put it simply, my company inherited 130,000 lines of garbage from India. The application was written in C#; it was a teller app, the same kind of software tellers use behind the counter whenever you go to … Read more
Take a look at onBeforeUnload. It wont force someone to stay but it will prompt them asking them whether they really want to leave, which is probably the best cross browser solution you can manage. (Similar to this site if you attempt to leave mid-answer.) <script language=”JavaScript”> window.onbeforeunload = confirmExit; function confirmExit() { return “You … Read more
To help with answering, here is more about the anti-pattern comment: it is overused, introduces unnecessary restrictions in situations where a sole instance of a class is not actually required, and introduces global state into an application From: http://en.wikipedia.org/wiki/Singleton_pattern For more on this you can look at: https://www.michaelsafyan.com/tech/design/patterns/singleton Here is a great ending to the … Read more
I assume the answer is largely because why are you catching it if you can’t handle it? Why not let whomever can handle it (or whomever is left with no choice but to handle it) log it, if they feel that it is log-worthy? If you catch it and log it and rethrow it, then … Read more
Patterns are complex All design patterns should be used with care. In my opinion you should refactor towards patterns when there is a valid reason to do so instead of implementing a pattern right away. The general problem with using patterns is that they add complexity. Overuse of patterns makes a given application or system … Read more
There is nothing wrong in concatenating two strings with +. Indeed it’s easier to read than ”.join([a, b]). You are right though that concatenating more than 2 strings with + is an O(n^2) operation (compared to O(n) for join) and thus becomes inefficient. However this has not to do with using a loop. Even a … Read more
Some projects have all data twice. Once as domain objects, and once as data transfer objects. This duplication has a huge cost, so the architecture needs to get a huge benefit from this separation to be worth it.
If you define patterns as anti-patterns just because there are some situations where it does not fit, then YES it’s an anti pattern. But with that reasoning all patterns would also be anti patterns. Instead we have to look if there are valid usages of the patterns, and for Service Locator there are several use … Read more
I’ll make my point very clear: a singleton with parameters is not a singleton. A singleton, by definition, is an object you want to be instantiated no more than once. If you are trying to feed parameters to the constructor, what is the point of the singleton? You have two options. If you want your … Read more
Second Class Citizens – test code isn’t as well refactored as production code, containing a lot of duplicated code, making it hard to maintain tests.