Reputation
1,932
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
6 13
Newest
 Yearling
Impact
~75k people reached

Oct
19
answered Intellectual Property cost
Oct
19
comment Make a big deal out of == true?
@AttackingHobo, that's one of the pitfalls of not having boolean types in a language and/or not using a class to provide the exact behavior wanted.
Oct
19
comment What's the most absurd myth about programming issues?
@Walter, but you can have 9 babies in 9 months and a little-league baseball team in 7 years.
Oct
19
comment Are null references really a bad thing?
@dash-tom-bang, comparing their relative difficulty isn't relevant. Isn't it easier to debug garbage data when it isn't getting clobbered with null references along the way? And don't you figure having to mentally juggle the pathways through null-reference checks makes the debugging work harder? Why add the extra null-reference checking code to begin with? Because it's the way K&R did it? Why is it important to spend time and effort adding, testing and debugging null-reference checks when we don't have to? What are we buying with that investment?
Oct
18
answered Make a big deal out of == true?
Oct
18
revised Make a big deal out of == true?
edited tags
Oct
18
revised Are null references really a bad thing?
edited tags
Oct
18
revised Should one use pseudocode before actual coding?
edited tags
Oct
18
revised Should one use pseudocode before actual coding?
edited tags
Oct
18
comment Should one use pseudocode before actual coding?
@Thorbjørn, ah. As in "seamless integration". Until you said "visible seam" it's what I understood. Then I thought you might mean seams as defined in Working Effectively With Legacy Code (informit.com/articles/article.aspx?p=359417&seqNum=3). In any case, modeling the problem's domains during the analysis and design phases not only result in cleaner objects than using TDD alone, such models can benefit other projects with the same domains.
Oct
18
answered Are null references really a bad thing?
Oct
18
comment Should one use pseudocode before actual coding?
@Thorbjørn, that last comment doesn't make sense to me. Saying "interfaces get the best when you do the tests first, and the actual code later" seems to be pro-TDD. In a new project there is no working implementation to retrofit to a new API. And please tell me what you consider to be a seam as it seems like we're not in agreement on its definition.
Oct
18
comment Is the agile approach too much of a convenient excuse for cowboys
@Oddthinking, the PM is supposed to be a grown-up, managing the company's time, money and staff to see the project through. The backers are willing to risk their investment, but if he knows he has a car wreck in the making, he owes it to them to protect their investment by making chances of a wreck less likely. He also owes it to the rest of the team who deserve to have a successful project on their record instead of a failure. If he's got developers who are like undisciplined kids, either he changes the process to protect the company from them, or he replaces them.
Oct
18
comment Should one use pseudocode before actual coding?
@Thorbjørn, TDD doesn't dictate where seams should go (but then again, neither does pseudocode). It's used to ensure they have a sensible interface, and follow-up changes to the codebase are tested. It's up to programmers to follow sound design principles and techniques to determine where seams should go and their type. Perhaps using, user stories, use cases, CRC cards, data-flow diagrams, sequence diagrams, modeling, etc.
Oct
18
revised How common are “bandage” fixes?
edited tags
Oct
18
revised Should one use pseudocode before actual coding?
edited tags
Oct
18
answered Should one use pseudocode before actual coding?
Oct
18
comment How do I report software vulnerabilities found in an open source library that are widely used but have a dilapidated team structure?
ørn, forking the project should be the last resort as the codebases could be diff'd and exploits worked out from them.
Oct
18
revised How do I report software vulnerabilities found in an open source library that are widely used but have a dilapidated team structure?
edited tags
Oct
18
comment How do you know when to stop adding features?
@fearoffours, You can always find ways to make your own work better. The point is to find out from the users how to make it work better for them. Solve real obstacles. Smooth real rough spots.