taway2012
Joined 13 years ago
Joined 13 years ago
Am I mistaken?
The best orgs do a rewrite usually in the face of sea changes to the technology stack (e.g., containers vs. VMs) or business use (number of users is now 10X of original etc). Bringing key infrastructure in-house is also a decent reason, but the benefit of building expertise in an existing ecosystem vs. full rewrite should be carefully weighed.
You probably have read spolsky's article. It's quite dated by now, but it's still more right than wrong. http://www.joelonsoftware.com/articles/fog0000000069.html
However, I'm not convinced that void functions are better written in the guard-clause style. I think the intent of the code is better expressed with nested ifs. Of course, try to factor the ifs so that they're readable.
I'm saying this is more readable if the "do something part" is less than about 15 lines. Thoughts?
void do_something(input) {
if (!input.already_done()) {
// do something.
}
}Thank you vinkelhake for nailing the the real problem (exceptions) and bothering to check whether the stack overhead really exists.
Just wanted to chime in with a comment because HN doesn't show vote counts, so future readers will "see" my upvote on vinkelhake's comment.
I did this due diligence for a 10-user app. These guys have no excuse for not planning for a DDoS with a serious business.
>>> 'truthy' if None else 'falsy'
'falsy'
>>> 'truthy' if False else 'falsy'
'falsy'
>>> 'truthy' if 0 else 'falsy'
'falsy'
I had zero problems reading the print version.