ShaunCodeweaver

35 ms·

1.
by ShaunCodeweaver 13y ago
Very much this - though I've experienced this in other stacks. Would love to know the best way people handle this.
2.
by ShaunCodeweaver 14y ago
I totally agree, but even just the basics can be a great addition. What I find odd is even just simple things such as pre or post conditions don't appear to be used widely, let alone cool features built into languages such as Eiffel or D.
3.
Why are you not using Design by Contract?(codeweavers.net)
1 points by ShaunCodeweaver 14y ago|2 comments
4.
The Anti If Campaign(codeweavers.net)
2 points by ShaunCodeweaver 14y ago|0 comments
5.
by ShaunCodeweaver 14y ago
What lmm said is spot on. If your paranoid about null pointers in C/C++, use asserts or static analysis.
6.
by ShaunCodeweaver 14y ago
"Anyway, this gets used lots of times by my algorithm" You've got a missing class. The fact you're so concerned with testing it highlights this. The fact it's private I should be free to rename, add or remove parameters. If I did this to yo
7.
by ShaunCodeweaver 14y ago
This article is wrong in numerous cases. Testing private methods? Wrong. Don't do this. They'll be covered by your public API, if they aren't, delete them. If you need to test code that is private, you've got a missing abstraction. Pull tha
8.
by ShaunCodeweaver 14y ago
Care to expand givan?
9.
MVC is broken(codeweavers.net)
3 points by ShaunCodeweaver 14y ago|5 comments
10.
Auto updating browsers suck for developers... sort of(codeweavers.net)
1 points by ShaunCodeweaver 14y ago|0 comments
11.
Achieving More Isolated Unit Testing(codeweavers.net)
5 points by ShaunCodeweaver 14y ago|0 comments
12.
by ShaunCodeweaver 15y ago
Despite usually hating viewing slides without the presentation, I actually find this style very good for getting the point across. Hammer down and there are some good quotes/ideas in there.
13.
Recursively building a Web Service - using the same Web Service(codeweavers.wordpress.com)
1 points by ShaunCodeweaver 15y ago|0 comments
14.
Why treating build warnings as errors is important(codeweavers.wordpress.com)
2 points by ShaunCodeweaver 15y ago|0 comments
15.
by ShaunCodeweaver 15y ago
Exactly. Refactoring is the process of changing code without changing behaviour. If that means you change some tests so be it. There is no rule to say that you can't do this, but many devs seem to fear this.
16.
by ShaunCodeweaver 15y ago
That's right Colin. I completely agree, however if you break unit tests during a refactor, yet there is no functional change - bin the tests as long as you have end to end tests higher up. I should add that any new code you add should have
17.
Write unit tests? Start deleting them(codeweavers.wordpress.com)
7 points by ShaunCodeweaver 15y ago|4 comments