418 reputation
213
bio website lordzoltan.blogspot.com
location Colchester, United Kingdom
age 34
visits member for 2 years, 8 months
seen Apr 3 at 16:25

A Senior Developer with JobServe in the UK. Just finished the initial release of the JobServe Android App - 'Jobs & Career Search', which uses the JobServe Web API which I also developed. I have been a professional developer since March 2004, but started learning back when I was 5 or 6, writing BASIC on the ZX Spectrum.

Skills

C#, Javascript, C++ and (passable) Visual Basic. ASP.Net MVC, the .Net type system and runtime, dynamic code generation and usage (getting good at ANTLR at the moment), and I'm a fierce bugslayer. A particular strength is finding and extracting frameworks to promote reusability.

I bore people on Twitter, too, as @RealLordZoltan.
I RTFM to learn something new, I comment my code, I type with both hands, and I validate my arguments.


Jan
10
awarded  Popular Question
Aug
27
awarded  Popular Question
Aug
26
awarded  Nice Question
Aug
8
awarded  Yearling
Oct
30
comment Suggested HTTP REST status code for 'request limit reached'
I went with a 429 in the end - it's in the draft spec but I seriously doubt it'll end up being used for anything else.
Oct
30
accepted Suggested HTTP REST status code for 'request limit reached'
Aug
29
answered Actions and Controllers managing strategy in MVC apps
Aug
8
awarded  Yearling
Jul
26
revised Should I charge a client for mistakes that I made?
added 5 characters in body
Jul
26
revised Should I charge a client for mistakes that I made?
Exemption to my rule based on whether it's your choice or not.
Jul
26
awarded  Nice Answer
Jul
25
awarded  Editor
Jul
25
revised HTTP Response Header for a unique Request ID for REST service
Added link to related question on SO
Jul
25
comment HTTP Response Header for a unique Request ID for REST service
Actually, no I haven't, looks like I misinterpreted the spec's definition of 'message-header' as being a specific header and not a BNF rule. Hmmm...
Jul
25
comment HTTP Response Header for a unique Request ID for REST service
Yes it is an option. But something feels hacky about an enveloped response like this. Consider a json operation returning a string; now it's returning a type with two members and clients have to do more work to get their data. Not very restful! I have found a header in the spec that might do it, I'm posting an answer...
Jul
25
answered Should I charge a client for mistakes that I made?
Jul
25
asked HTTP Response Header for a unique Request ID for REST service
Jul
11
awarded  Critic
Jul
11
awarded  Citizen Patrol
Apr
27
awarded  Teacher