5,358 reputation
11330
bio website stroiman.com/software
location Gladsaxe, Denmark
age 39
visits member for 3 years, 9 months
seen 1 min ago

I have worked professionally with software development since 1997. Since year 2000 I have worked as an independent contractor, helping various business in developing their internal and external IT systems. Since 2002 I have worked almost exclusively with the .NET framework.

Of notable work can be mentioned IT-Jobbank, Denmark's largest online job board for IT professionals, where I was the lead developer and architect.


Jan
28
revised How do we make unit tests run fast?
added 123 characters in body
Jan
27
answered How do we make unit tests run fast?
Jan
25
comment agile / scrum and functional specs
And I'm not hung up on dogma. If the individual team finds that it makes more sense to update the specs every 3 or 4 sprints, by all means do so. Scrum is not set in stone. Adapt it to your own needs. I'm just pointing out that if you want to deliver a potential shippable, it might be problematic to have updating the specs in a separate story.
Jan
25
comment agile / scrum and functional specs
"... @Pete expressed concern that if the spec were a story, how can the product be "potentially shippable" if all that is delivered after an iteration is a spec?" I have a feeling you have misunderstood my comment. What I am trying to say is, can you say that you are delivering a potential shippable after each sprint, if updating the functional specs is placed in a separate story scheduled to be implemented in a later sprint?
Jan
24
comment agile / scrum and functional specs
Very good idea to have updated ISO specifications to be part of the done criteria for a story. To place it in a separate story however, I have difficulty seeing how you can deliver a "potential shippable" product after each sprint.
Jan
21
awarded  Mortarboard
Jan
16
awarded  Necromancer
Jan
16
comment IOC and stateless services. Short-lived or single-instance?
No. What I am trying to say is that it may be difficult to predict how your code base will be modified over time. But the question is extremely general, so I'm giving an extremely general answer ;)
Jan
15
answered IOC and stateless services. Short-lived or single-instance?
Jan
11
awarded  Yearling
Jan
2
answered Use Queue<T> or stick to native f# lists
Nov
1
awarded  Nice Answer
Sep
11
comment Declaring interface in the same file as the base class, is it a good practice?
It is in fact a quite normal pattern to have one interface for one class in .NET, as it allows unit tests to substitute dependencies with mocks, stubs, spys, or other test doubles.
Sep
11
comment Declaring interface in the same file as the base class, is it a good practice?
Like it or not, using an 'I' in front of an interface name is a de-facto standard in .NET. Not following the standard in a .NET project would in my point of view be a violation of the 'principle of least astonishment'.
Sep
11
answered Declaring interface in the same file as the base class, is it a good practice?
Sep
8
awarded  Guru
Jun
11
comment Is it common for a programmer not to know the difference between C and C++?
Generally, the "young" programmers I have met have had a degree in engineering. Come to think of it, almost all the programmers I work with have a degree in engineering, including myself.
Jun
11
revised Is it common for a programmer not to know the difference between C and C++?
added 1 characters in body
Jun
11
comment Is OOP becoming easier or harder?
@gbjbaanb - We already have great tools for system-wide/acceptance testing, e.g. Cucumber on the Rails platform. But the teams that are really good and writes very few bugs, but also delivers fast, they write a lot of unit tests, and just a few system-wide tests. See about the "Testing triangle", e.g. here jonkruger.com/blog/2010/02/08/the-automated-testing-triangle
Jun
11
answered Is it common for a programmer not to know the difference between C and C++?