Reputation
626
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 11
Newest
 Pundit
Impact
~14k people reached

Jul
27
comment How do you explain a 'statement' in programming?
I think the phrase subject.verb(predicate) helps describe it in this case.
Jul
6
comment Bad practice - switch case to set environment
I love your first paragraph. Sure, you follow it up with... pointing out what the problems are... but the idea that "this is bad because blog XYZ said so" is the cause of more bad code than it actually prevents.
Jul
3
comment Is testable code better code?
@Telastyn In over 10 years of development, I never had a team that mandated a unit testing framework, and only two that even had one (both had poor coverage). One place required a word document of how to test the feature you were writing. That's it. Perhaps I'm unlucky? I'm not anti-unit test (seriously, I mod the SQA.SE site, I'm very pro unit test!) but I haven't found them to be as widespread as your statement claims.
Jun
30
comment Should you write your back-end as an API?
YANI is such an underused property of software development.
Jun
30
comment Should you write your back-end as an API?
These days, it's rather implied that an unqualified "backend API" refers to a web api. Sure there are others, but if something is going to be decoupled, it's probably going to use HTTP to pass messages. Guaranteed? No. Probably? Yeah.
Jun
26
comment Should you write your back-end as an API?
But we don't need the future. Even if YAGNI applies, we should consider... ummm. WDNITTA (We DO Need It This Time Anyway)
Jun
26
awarded  Pundit
Jun
25
comment Should you write your back-end as an API?
You say YAGNI applies, but my experience has been apps either get a UI rewrite every couple years, or everyone complains that they do need one. Sure would be nice if we didn't lose our busniess logic because a new front end technology has arrived.
Jun
5
comment Clean Code comments vs class documentation
Wow - change your document generator because it requires a couple extra lines of html for parsing? Let's not.
Jun
5
comment Clean Code comments vs class documentation
@l0b0 There is no such thing as temporary code. The code never gets refactored because the business was happy with the outcome and won't approve funding to fix it. Five years from now, some junior developer will see this code, you're not even using WizBug 4.0 anymore since you've replaced it with Bugtrocity v9, so "Bug123" means nothing to him. He now thinks this is how permanent code is supposed to be, and proceeds to be a terrible developer his entire career. Think of the children. Don't write temporary code.
May
17
comment Intentional misspellings to avoid reserved words
No, simply no. Your team is far, far more likely to rotate members slowly over time. You can plan for one person getting hit by a bus, but you can't plan for your entire team getting hit by a bus. Most code is written for maybe a dozen people ever needing to read it, half of them during code review.
Apr
29
awarded  Popular Question
Mar
13
comment Why do schools teach arrays over List?
"Most accurately represents how a computer works" - all code accurately represents how a computer works. You put in the code, and it works. Unless you're a terrible programmer like me, in which case it doesn't work. But that's another story.
Feb
25
comment Is it premature optimization to add database indices?
A lot of time when I think "oh we can add an index" I find I actually have the wrong query. Maybe that's just me.
Nov
6
comment Why do we use non-descriptive internal codenames?
I hope the Gandalf branch isn't the codename for a unit testing framework. Anything run through it SHALL NOT PASS!
Oct
10
comment Algorithms: How do I sum O(n) and O(nlog(n)) together?
Side note: you could use a hash table to do this in O(n) depending on memory requirements.
Oct
4
comment When writing object-oriented code, should I always be following a design pattern?
When you say design pattern, do you mean a named one with a wikipedia page and at least a few experts who recommend using it? Or do you mean your code should be designed in a way that allows it to be patterned after in the future?
Sep
30
comment Is creating subclasses for specific instances a bad practice?
Instead of having an if-else on the type, wouldn't they each just have their own behavior method to be called?
Sep
29
awarded  Yearling
Sep
29
answered Is creating subclasses for specific instances a bad practice?