chuckm

4 ms·

1.
OAuth Demystified for Mobile Application Developers [pdf](research.microsoft.com)
2 points by chuckm 12y ago|0 comments
2.
by chuckm 14y ago
Looks like there are a few positions: http://www.google.com/about/jobs/search/#q=%22architect%22&#...
3.
Continuation Passing Style Revisited, Part One(blogs.msdn.com)
1 points by chuckm 16y ago|0 comments
4.
by chuckm 16y ago
Straight off the bat the most glaring problem with that statement is that Linq is not part of C# Parts of it are. Query expression keywords[1] are defined in the C# 3.0 Language Specification (see 7.15 Query expressions)[2]. [1] http:/
5.
by chuckm 17y ago
"TDD is clearly not a cure all" Who said it was?
6.
by chuckm 17y ago
A lot their "training" seem designed to weed out those who lack specific innate traits I don't think it's entirely about innate traits. There's a lot of training that occurs before going to some these schools. For example, in the Army you
7.
Return of the Real Programmer(enfranchisedmind.com)
5 points by chuckm 18y ago|8 comments
8.
Subsuming Packages and other Stories(gbracha.blogspot.com)
1 points by chuckm 18y ago|0 comments
9.
Newspeak Prototype Escapes into the Wild(gbracha.blogspot.com)
1 points by chuckm 18y ago|0 comments
10.
by chuckm 18y ago
Unfortunately the writer makes it seem like all Asp.net developers use just the visual designer and the pre-made tools. How did you reach this conclusion? I don't see any mention of the visual designer or pre-made tools in this article.
11.
by chuckm 18y ago
It seems like you're still using some form of automation to find bugs, regardless of whether these would be classified as unit tests, correct?
12.
by chuckm 18y ago
I’ve never seen Kent Beck as a crazy rules person. I think his comment from stackoverflow demonstrates this: I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confi
13.
by chuckm 18y ago
I disagree. I think comments are often overused but I'm not convinced that code and tests are expressive enough to always convey why functionality exists. For example, sometimes limitations in third party dependencies force you into adding