642 reputation
410
bio website
location England, United Kingdom
age 28
visits member for 3 years, 4 months
seen Aug 11 at 7:22

Software developer, company director and guitarist.

Experience in C#, C++, Java, SQL, various embedded systems, assembler. Enjoy work with algorithms, distributed computing, anything clever or inventive.

Familiar with various frameworks, technologies and methodologies; ASP.NET / MVC, WPF, MVVM, strong OOP, design patterns, DI, XML / XSLT, WCF, low-level network protocols, some COM, MFC, unit testing, code optimization and other low-level fun bits.


Apr
11
awarded  Yearling
Feb
21
awarded  Nice Answer
Apr
11
awarded  Yearling
Apr
11
awarded  Yearling
Jan
4
comment C++ for C# Developers
As a quick point, I would say there's plenty of C++ that's basic. Distinguishing pointers/references and C++ templates can make your head spin at first, but when it comes down to it there are still classes, cout and simple ways to achieve simple goals
Jan
3
awarded  Quorum
Jan
2
awarded  Student
Nov
2
awarded  Enlightened
Nov
1
comment Should we attempt to review all our code?
Automated tools are great, but turn useless unless you have the time and resource to maintain all the tests as up-to-date.
Oct
3
awarded  Nice Answer
Oct
3
answered How to handle 'external' dependencies in scrum?
Oct
3
comment Should we attempt to review all our code?
Is that an average? Limiting a complex review to an hour seems strange, and if there's not that much to review.. well I can't see how an hour a day would be workable?
Oct
3
comment Should we attempt to review all our code?
No it doesn't, I was being comprehensive and saying it's important
Oct
3
answered Should we attempt to review all our code?
Sep
6
awarded  Nice Answer
Aug
25
awarded  Commentator
Aug
25
comment What is the difference between a prototype and a production level solution?
@sJhonny - if you set out to throw the prototype away, then you should do so. However if you are efficient and thoughtful and aware of budgets etc, there is no reason to build a prototype with 'throwing it away' in mind, any more than you would expect to refactor most code in the future anyway
Aug
25
comment What is the difference between a prototype and a production level solution?
I agree that can happen. But what happens more frequently on projects I've seen is developers getting precious about code and for example a working prototype, suitable for production release, refactored 'n' times or thrown away just to follow some arbitrary set of criteria such as those set out above. Remember that software is being developed in order to make money for a business. It's not for love or to achieve inner peace. In the long term throwing away a dodgy prototype is a good idea, throwing away a good one can be a bad idea.
Aug
25
comment What is the difference between a prototype and a production level solution?
I think that's possible but depends on how the original prototype was developed. From a business perspective that could be an awful decision to make, depending on effort and viability of the prototype.
Aug
25
answered What is the difference between a prototype and a production level solution?