22,030 reputation
14486
bio website thehungersite.com
location United Kingdom
age 46
visits member for 3 years, 9 months
seen 12 hours ago
experienced software engineer with many years in the industry, mostly c++ for large-scale, high-reliability systems.

2d
answered Git, semantic versioning and how it fits into (my) a typical development timeline?
Jan
28
comment Algorithm for merging multiple rows of data
TBH sort then merge is such a common idiom a programming language was built around it :-)
Jan
28
answered Algorithm for merging multiple rows of data
Jan
28
comment Leaving intentional bugs in code for testers to find
Lol. "my, err, friend would like to know...."
Jan
23
awarded  Enlightened
Jan
23
answered Designing a REST api by URI vs query string
Jan
22
comment Kernel mode web servers: A clever optimization or a security nightmare?
@usr Http.sys is a relatively new thing, introduced in Windows Server 2003. I'm pretty sure its there so you can run many web API services listening on port 80 simultaneously.
Jan
22
awarded  Nice Answer
Jan
22
answered Kernel mode web servers: A clever optimization or a security nightmare?
Jan
21
comment Architectural / Application Practices to guard against 'breaking changes'
@dougajmcdonald 2-weekly sprints are overrated, and if they get in the way of producing working code, then they are downright broken. Ditch the dogma, pick a longer "sprint" in your case and/or leave the UI to the next iteration after finishing the APIs. Remember Agile is not about blindly following any rule, make your own rules that work for you.
Jan
21
comment Architectural / Application Practices to guard against 'breaking changes'
Having used EF in a project, adding it to a project that has lots of changes is a disaster - if you have multiple streams of development (as you will) merging the bloody edmx afterwards is a nightmare.
Jan
21
comment Architectural / Application Practices to guard against 'breaking changes'
@dougajmcdonald as it is, there is no easy way to accommodate major changes except rolling up your sleeves and getting on with it :-)
Jan
21
comment Architectural / Application Practices to guard against 'breaking changes'
Surely completion of a collection of stories (eg update UI, logic, DB) should leave it in a working state - what else is needed after all! In terms of stories, the story should be "add functionality" and that is them split into 3 tasks - update UI, update Logic, update DB. Never try to use 'breaking' and 'nonbreaking' as you never want a nonbreaking story that turns out to have breaking consequences.
Jan
21
answered Architectural / Application Practices to guard against 'breaking changes'
Jan
20
awarded  Good Answer
Jan
20
comment How to make significant technical decisions given very little time
@Flot2011 though if you have a MBA, you stay where you are and send all your troops to fight either hill. If they all die, oh well, you get more troops and continue but this time saying that your experience as a general makes you so much more ... deserving of monstrously more salary.
Jan
20
awarded  Nice Answer
Jan
20
comment How to make significant technical decisions given very little time
There is no 'best option' in many cases, you could write it as a PHP webapp and it'd work. Or you could write it as a Qt program and it'd work. It could be a openGL game-interface UI. All of these are acceptable choices, the trick is to choose one and then set about making it work. Do not paralyze yourself with doubts once you choose something.
Jan
20
comment How to make significant technical decisions given very little time
Re: #1. Nobody likes a whiny loser, so just highlight you've done the best you can against impossible circumstances, then you look like a go-getting team-playing pro-active winner! Management likes that kind of thing. Incidentally, there are many reasons why the big rewrite doesn't work, the choice of one tech over another is usually the least problem.
Jan
20
answered How to make significant technical decisions given very little time