Reputation
7,756
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
3 20 41
Newest
 Nice Answer
Impact
~257k people reached

Mar
3
answered Why are eval-like features considered evil, in contrast to other possibly harmful features?
Feb
16
awarded  Nice Answer
Sep
29
awarded  Yearling
Apr
28
answered Should we always DRY? Any edge case examples of when not to?
Mar
10
comment Design pattern for an ASP.NET project using Entity Framework
@SimpleFellow quite right. People are still doing fine with VBA too. I hear a lot of banks are still running software in COBOL. There's certainly no requirement to change simply because a technology is easier to use, cleaner and better designed, but that doesn't mean there is no compelling reason.
Feb
18
comment What is the “correct” way to store functions in a database?
Could you implement the function in PgSQL and run it as a DB task?
Feb
10
revised Is it actually worth unit-testing an API client?
A weird extra 's' I should have never added.
Oct
31
awarded  Nice Question
Sep
29
awarded  Yearling
Sep
6
awarded  Good Answer
Sep
5
comment What's wrong with comments that explain complex code?
On a day to day basis I use work in progress comments a lot too- they aren't there for the long run, but dropping in a TODO note or a short section to remind me what I was going to do next can be a useful reminder in the morning.
Sep
4
revised Communication/Updates between units of works/entity framework contexts, colliding with user changes
Added edit at the bottom.
Sep
4
comment Communication/Updates between units of works/entity framework contexts, colliding with user changes
Low user count and an EF back end suggest to me that you might as well update early and update often. I would also have some kind of polling facility to check when the last update was performed so that if User 1 is using the product and User 2 makes an update it can notify them and update their interface directly. I would be more worried about concurrency problems between users than between tabs on a single user's machine.
Sep
4
answered Communication/Updates between units of works/entity framework contexts, colliding with user changes
Sep
3
comment Does Play framework approach necessarily leads to confuse code?
The way to frontload this is actually to do some prototyping/playing around with the platform before you start, so that you know that it does the things you need and get the basics of it's idioms. That saves a lot of time in the long run. My experience with Rails has been that there is no maintainability problem with models and model code, the real problems arise from depending on gems that are subsequently deprecated/abandoned- after a while that starts locking you to old versions of everything.
Sep
3
comment Communication/Updates between units of works/entity framework contexts, colliding with user changes
Are the tabs open at the same time or can the user only see one at any given point? Normally tabs would be the latter, but I want to be clear.
Sep
3
answered Does Play framework approach necessarily leads to confuse code?
Sep
2
awarded  Nice Answer
Sep
1
comment What's wrong with comments that explain complex code?
@Christian is it? The first line references that statement, certainly, but beyond that it is a little broader as I understand it.
Sep
1
answered What's wrong with comments that explain complex code?