meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 8 months |
| seen | 2 hours ago | |
| stats | profile views | 68 |
|
Apr 12 |
awarded | Taxonomist |
|
Mar 21 |
comment |
Apply for a software job via WebService call Parse started doing exactly this about a year ago and got some press out of it. See parse.com/jobs#api. |
|
Sep 20 |
awarded | Yearling |
|
Aug 11 |
answered | TFS non-chronological deployment? |
|
Aug 8 |
comment |
Sell me on IoC containers, please Absolutely. I think maybe instead of saying "controlling lifetimes" I should have said "enable instance sharing" - my point was that a container could be used to enable pooling, singletons, etc. |
|
Aug 8 |
comment |
Sell me on IoC containers, please I don't know enough about native environments to comment on what you've written there, but "in garbage collected environments, you never have control over dependency lifetimes anyway" is only true if the dependent is constructing the dependency itself. If the dependency is passed in, the object that did the passing can optionally maintain a reference to it - this is what a container would do if you registered a type with a lifetime policy of something other than "create a new instance every time I need an instance." |
|
Aug 8 |
comment |
Sell me on IoC containers, please It's important to note that there are a couple of disadvantages to building your dependencies in the constructor of the object that uses them: 1) You have no direct control over the lifetime of the object, and 2) If the dependency is in another module (assembly, etc.), you end up with a module dependency. With a container, you can easily enforce/use concepts like lazy instantiation, pooling, and singleton, and all module dependencies are funneled through the container's module. |
|
Jun 6 |
awarded | Popular Question |
|
Mar 28 |
comment |
What is the preferred tool/approach to putting a SQL Server database under source control? +1 as far as I know, Database Projects are the "official" MS solution to this. Definitely give yourself some time to read about it and play around with it though, as not all of its features are obvious up front, and it has quite a bit of functionality. As you read about it and work with it, keep in mind that even though you're working in Solution Explorer, the model/strategy for working with database projects is a little different than for class libraries and the like. |
|
Mar 22 |
awarded | Nice Answer |
|
Mar 22 |
answered | Is dependency injection essential for unit testing? |
|
Mar 20 |
answered | Understanding Data Binding for Windows Phone 7 |
|
Mar 8 |
awarded | Nice Question |
|
Mar 7 |
comment |
Strategy for maintaining assembly references in TFS Don't look at solutions as units of developer work, look at them as units of build. If Project A in Solution A depends on project B, and project B is actively being worked on by anybody, make it a project reference. If the guy working on Proj. A doesn't need to work on Proj. B, then he doesn't need to touch it. |
|
Mar 7 |
comment |
Strategy for maintaining assembly references in TFS "This isn't always a good idea or feasible". Not saying that you're wrong, but what makes you say this? If you have code that's being actively worked on, it should be referenced as a project reference. |
|
Feb 24 |
awarded | Promoter |
|
Feb 22 |
asked | Is there an effective way to test XSL transforms/BizTalk maps? |
|
Feb 1 |
comment |
Dealing with management that does not see value in improvements that are not immediately visible to the user +1. The way you communicate this kind of stuff is through estimates. What you need to do is set the expectation that you will be providing estimates throughout the project (starting as early as possible) so that all involved can understand the return on investment. Make it clear that they are estimates (thus, they do not change without more information) and that you are communicating them so that the leadership can make better decisions. Then, you let the estimates start the conversation for you. "Why is this phase's estimate higher than the last one?" "Well..." |
|
Feb 1 |
comment |
Relationship between C#, .NET, ASP, ASP.NET etc +1, but one minor niggle on #2 - .NET is not a "library of code," it is a framework (which you correctly define as a "workflow" that defines how your programs are defined and run). The collection of standard libraries published by Microsoft that are available to the .NET languages is the .NET Base Class Library (BCL). |
|
Jan 12 |
answered | Rule of thumb for cost vs. savings for code re-use |
