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

Jul
3
comment If my team has low skill, should I lower the skill of my code?
I know learning is a constant thing, but is it really this developer's job to train his fellow employees? It really should be management's job to find the most appropriate training for them.
Mar
12
comment I want to publish an android app, but I'm afraid of software patents
Even if I was a lawyer I'd still put that at the top!
Feb
13
comment Detecting misusage of delete[] vs. delete at compile time
@James I believe he means "What good is detecting it if you can't change it anyway?" What good is detecting the problem if all you can do is complain that it's there?
Jan
7
comment Intentional misspellings to avoid reserved words
If you are using both klass and clazz that's a bad thing. You need to be consistent so they only have to learn it once. And ideally this is spelled out in the teams style guidelines too, so it's not much of a surprise.
Oct
3
comment What should my “large codebase sample” look like?
When comparing those two, I would also compare what the client wanted. If the client had one item for sale, and you built this awesome system capable of handling thousands of items, and all these bells and whistles, I'd be inclined to think it might have been overdone.
Oct
3
comment Why are interfaces useful?
+1 for the term "Well decoupled constructs"
Sep
18
comment Data structure: sort and search effectively
Isn't this more of an SO question? I would consider algorithms more for SO, while arguing with your fellows devs about algorithms more for this site.
Sep
1
comment I don't understand why algorithms are so special
I disagree with your first statement. I find there are some very awesome algorithms. For example, many hashing algorithms are just algorithms, but the ones that multiply by 31 to take advantage of the "bitshift and subtract" optimization, while still keeping a prime multiplier, I think those are awesome! I'm entirely fascinated by the brilliance that people are able to apply to our craft, in the same way that basketball players marvel at their superstars and the awesome moves they make.
Jul
26
comment How To Deal With Terrible Design Decisions
If someone insulted my work, I would ask for an apology. If they criticized it, I would not. I have had my work criticized on hundreds, probably thousands, of occasions; I have had it insulted very, very few times. If someone thinks that every criticism of their work is an insult, they have a serious problem. This applies to any line of work, or any social interaction ever. The same applies the other way: you have to criticize in a way that won't insult. There's no black and white terms of where you cross from criticism to insult, either.
Jul
5
comment Programming knowledge vs. programming logic
-1, your definitions simply aren't true. You can learn knowledge through experience, and you can learn logic from a book.
Jul
4
comment I've inherited 200K lines of spaghetti code — what now?
@kmote If the source files aren't human readable, how do you arrive at '200k lines', and that it's spaghetti code? I've worked with LabView in the past (not that I ever in a million years thought it would come in handy...) and don't see how it could have spaghetti code.
Jul
4
comment I've inherited 200K lines of spaghetti code — what now?
@mattnz Getting version control isn't like buying a Porsche. It's like getting a Porsche for free... and who wouldn't love a free Porsche to cart around their groceries?!
May
1
comment Writing commit messages as a solo developer?
For my solo stuff, I have my commit message before I work on something. I do a small thing (aim for 30-45 minutes... got a wife and kids here!), and commit it. Maybe you could call it commit driven development?
Apr
5
comment How do you maintain focus when a particular aspect of programming takes 10+ seconds to complete?
+1 for distracting you from distraction - fight fire with fire! That way you don't get fired!
Dec
14
comment How do quick & dirty programmers know they got it right?
Quoth the raven, nevermore: "Beware of bugs in the above code; I have only proved it correct, not tried it." A modern view if this would be "not tested it". Now the difference between the above and the programmers in the OP is that they didn't even take the time to prove it correct. But this alludes to the notion that even if you prove something correct, it doesn't prove that your code matches what you think you proved.
Dec
8
comment The importance of the length of a program?
I recognize that the number doesn't change, but you can't in your right mind look at a piece of code, add additional code, and say it is not more complex.
Dec
8
comment The importance of the length of a program?
@littleadv That's true, there are multiple definitions. I don't think there's a definition out there where adding additional code does not increase the complexity.
Dec
8
comment The importance of the length of a program?
I agree that size and complexity are linear in all cases. However, I do not believe you can make a 500kloc piece of software that is less complex than a 50 line piece of software. I refuse to believe there is a piece of code 10,000 times larger that is less complex or easier to maintain. 10 times? Maybe, depending on who wrote it and what the conditions were, sure. 100? Doubtful, but I wouldn't 100% exclude it. 500? Guaranteed to be more complex.
Nov
8
comment Analyzing a programming language
Wait, what? "Simple like C before delving into Java." You lost me at "Simple like C".
Sep
30
comment What does SVN do better than Git?
@DanRay I'd rather have that than my current firm's setup. The codebase is branched for every project, no matter how small. One file, one line change? Project, branch, have it sit in a code-review state and test state, and merge it afterword. I've done more merging in one year here than I have in the five years prior. :\