Reputation
649
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
9 19
Impact
~19k people reached

  • 0 posts edited
  • 1 helpful flag
  • 84 votes cast
Nov
25
comment learning on the clock
and letting programmers learn for some hrs @work might even be cheaper than both paying salary AND the costs of training
Nov
25
comment learning on the clock
I hadnt noticed that interpretation on Hiring for passion, which I see frequently in job posts. If the employer didn t just say it but actually supported it with some time during working hrs, Ill take 'hiring for passion' any day though over the others,
Nov
25
asked learning on the clock
Oct
4
awarded  Popular Question
Jun
19
awarded  Teacher
May
29
awarded  Popular Question
May
11
awarded  Popular Question
Mar
25
accepted Are developers expected to have skills of business analysts?
Mar
24
revised Are developers expected to have skills of business analysts?
deleted 37 characters in body
Mar
24
revised Are developers expected to have skills of business analysts?
added 103 characters in body
Mar
24
asked Are developers expected to have skills of business analysts?
Mar
12
awarded  Yearling
Jan
8
comment cost trade-offs for deploying changes to prod, stored procs vs. LINQ
It seems like you're talking more about worst-case cost than probability? If you're proposing that cost cannot be calculated without risk -- then can risk be calculated without cost?
Jan
8
comment cost trade-offs for deploying changes to prod, stored procs vs. LINQ
@Jarrod, I reworded the title to be consistent with the question as written, which remains to ask about trade-offs, rather than an absolute "which is best".
Jan
8
revised cost trade-offs for deploying changes to prod, stored procs vs. LINQ
added 249 characters in body
Jan
8
revised cost trade-offs for deploying changes to prod, stored procs vs. LINQ
edited title
Jan
7
awarded  Quorum
Jan
7
comment cost trade-offs for deploying changes to prod, stored procs vs. LINQ
+1 but not marked answer since it doesn't answer the question as you say it's wrong; so if you think the question is wrong, then please at least answer the "correct" question.
Jan
7
comment Stored Procedures a bad practice at one of worlds largest IT software consulting firms?
2) on unit testing stored procs. idk about other unit test frameworks but at least with MS Test (VisualStudio.TestTools.UnitTesting), running any of the Assert methods on the stored proc at least requires a Db connection, which by definition makes it more of an integration test than a unit test. And a stored proc may reference state about the database at a global, database level. These may not be fake-able or have interfaces.
Jan
7
comment T-SQL stored procs orders of magnitude faster than LINQ
"runtime performance is irrelevant"? but tell that to the users or developers who spend their time on performance-tuning. Judging by the extended comments yet no answer to the actual question, it seems that either the answer is none or that you don't know?