4,201 reputation
21533
bio website devadept.com
location Scottsdale, AZ
age
visits member for 2 years, 7 months
seen 21 hours ago
stats profile views 212

twitter: @mr_eking


May
13
comment Paid vs ads-based Windows Phone app
Don't forget in-app purchases.
May
10
comment Scratch - why do schools teach students a language that is not used anywhere else?
@NimChimpsky I think you're grossly over-estimating the practical benefit people can get from an introductory programming class, regardless of language. The best programming language to use for absolute beginners is whatever lets them learn beginning programming concepts best. Let's not fool ourselves, nobody is going to get a job as a Java programmer after taking a 'intro-to-programming' course in Java as opposed to Scratch.
May
10
comment Scratch - why do schools teach students a language that is not used anywhere else?
@NimChimpsky I think it's incredibly easy to learn because I've seen kids learning by using it, first-hand. Even kids who had already tried other text-based languages that are supposedly easy to learn, like Python, found Scratch way easier and more fun to use.
May
10
comment Scratch - why do schools teach students a language that is not used anywhere else?
Scratch is good at teaching young children how to think like a programmer. Java (and the like) can be good at teaching adults how to get a programming job. Two completely different purposes.
May
8
awarded  Nice Answer
May
8
revised Is Entity Framework only for Asp .NET / Asp. NET MVC?
small grammar and spelling fixes
May
3
comment Is the use of JUnit feasible for a short duration project of around 3 months?
If I had a dollar for every time I saw a 3-month project that "will never be worked on again" still in production 5-years later, I'd be rich.
May
3
answered Is the use of JUnit feasible for a short duration project of around 3 months?
Apr
27
comment Empirical study on activity distribution of a programmer?
That's not an empirical study. It's not even a study. It's a survey. Big difference.
Apr
23
comment What is the best way to prove that in-code documentation is greater than extensive external documentation?
@jordan.peoples I agree with you that before/after screenshots of code is silly. Huge waste. That's what source control diffs are for. But there can definitely be a place for external documentation with UI screenshots, too. Even for developer documentation. Somehow I get the feeling your boss probably won't want to get rid of external documentation altogether (and he probably shouldn't). But you could make a convincing argument against code screenshots. That would at least make the process a bit easier. But, 'the developers won't read the docs' is never good a reason to toss them completely.
Apr
23
comment What is the best way to prove that in-code documentation is greater than extensive external documentation?
@jordan.peoples Yes, but as bad as screenshots of code are, you seem to be advocating something just as bad (doing all documentation in-line with the code). "In-code" documentation is not better or worse than external documentation; There are uses for both. You ask 'what is the best way to prove in-code documentation is better'? Perhaps it's not better at all.
Apr
23
comment What is the best way to prove that in-code documentation is greater than extensive external documentation?
I can't imagine why anybody would want screenshots of code, or in-code comments describing the UI. Neither seem particularly useful.
Apr
22
comment Is it possible to reach absolute zero bug state for large scale software?
40,000 pages of documentation for 400,000 lines of code, with practically unlimited budget, and it still wasn't error free. Multiply that by 50 (to get in the 20-million lines of code range that the question refers to)... I can't imagine the effort it would take to make that kind of code-base bug free.
Apr
22
comment Is it possible to reach absolute zero bug state for large scale software?
While the original question didn't do so, I'd like to point out that there's a gigantic difference between 'theoretically possible' and 'practically possible'. While a bug-free 20-million-line code base is arguably theoretically possible, it's almost certainly a practical impossibility, in today's market. Who knows what the future holds.
Apr
21
comment Is it possible to reach absolute zero bug state for large scale software?
@JohnR.Strohm I'm not sure why you think the 'message flow modulator' program, a program with 556 lines of code, has anything to with a question regarding a theoretical 20 million line system. Except, perhaps, to demonstrate that however hard it was to prove the correctness of the tiny program, it would be astronomically harder to prove the correctness of a massive one.
Apr
12
comment How many regression bugs from refactoring is too many.
@StephenC Thanks for completely misunderstanding the point. :-) Nobody's trying to control language use. Words have definitions for a reason. Especially in a technical field like ours, proper usage of terminology is useful. It's worthwhile to fight against the tendency to say 'well, everybody else misuses the term, so I might as well too'. Remember when terms like 'unit test' and 'Agile' and 'REST' had fairly well defined meanings? We could actually have productive conversations on the topics. Now those words are misused so much as to become worthless. Perhaps 'refactor' has joined them.
Apr
12
comment How many regression bugs from refactoring is too many.
Those who understand the difference between 'refactoring' and 're-engineering' should recognize that the difference in meaning is significant and important. We should not condone the use of 'refactoring', with the implication that behavior doesn't change, when what we mean is 're-engineering', with the implication that some behavior may have changed, and some bugs may have been introduced. If we water down the meaning of 'refactor' to mean simply 'I changed some code', then we will have lost the use of a good term. Common usage notwithstanding.
Mar
27
comment Should Repositories return IQueryable?
Your answer would be more useful if you provide a brief summary of the post you're linking to, instead of merely linking to it.
Mar
17
comment Kiln - Mercurial and Git limitation
Have you tried it?
Mar
9
comment Extreme Programming Daily Commits
I agree with this sentiment. Time of day should have nothing to do with when you commit your code. You commit whenever you have added a working subset of code, and you want to save your progress and move on. If that happens to be at the end of the day, so be it, but you should have been committing your code throughout the day to begin with.