Comments on: Why does software development take so long?

By: Matt

Matt — Sat, 12 Feb 2011 23:51:26 +0000

It always takes so long because with each decent sized project the technologies have moved on and you have to learn how to take advantage of the new ways - if you try to apply your tried and true method of a year ago, you often end up digging yourself into a hole. Perhaps just as importantly, each new technology has it’s own suite of nuances that you need to learn to work with and pitfalls that you need to learn how to work around.

By: Encino

Encino — Thu, 25 Jun 2009 04:23:07 +0000

Look at some of the things you listed, some of it just came out months ago! Every time we code something it is like re-inventing the wheel that is why it takes so long.

By: Jon Kruger

Jon Kruger — Tue, 31 Mar 2009 00:45:58 +0000

@joe,

I think of the membership Users table as separate from my Users table. For one, I don’t like to use Guids as my primary keys because I think it’s a pain.

The ASP.NET Users table ONLY deals with login related stuff. So I’ll have a separate Users table that looks like this:

create table Users
(
UserId int not null primary key identity(1,1),
MembershipUserId uniqueidentifier,
FirstName varchar(30),
LastName varchar(30)
)

The ASP.NET membership database comes with stored procedures for doing everything, so I should be able to just use those stored procs for all access of the membership tables. If I absolutely had to, I can map the membership tables to entity objects pretty easily with NHibernate.

My separate Users table will get loaded with NHibernate and is my real domain object.

This may not seem like it’s as “clean” of a solution as if you wrote it all from the ground up. But this way you don’t have to spend the couple of weeks writing all of this stuff yourself. If you have a valid reason for writing it all yourself, by all means go for it. I’m just trying to find a way to get things done faster, and using ASP.NET membership doesn’t muddle things up so much (IMO) that it’s not worth using.

By: joe

joe — Mon, 30 Mar 2009 23:03:39 +0000

How well would the asp.net membership integrate NHibernate. Thats my main problem with using that one particular piece. User interface elements and toolkits are interchangeable, but Users are domain level items i’d like a bit more control over.

By: DotNetShoutout

DotNetShoutout — Mon, 30 Mar 2009 20:53:26 +0000

Jon Kruger’s Blog » Blog Archive » Why does software development take so long?…

Thank you for submitting this cool story - Trackback from DotNetShoutout…

By: DotNetKicks.com

DotNetKicks.com — Mon, 30 Mar 2009 14:54:38 +0000

Why does software development take so long?…

You’ve been kicked (a good thing) - Trackback from DotNetKicks.com…

By: ASP.NET MVC Archived Blog Posts, Page 1

ASP.NET MVC Archived Blog Posts, Page 1 — Mon, 30 Mar 2009 02:37:57 +0000

[...] to VoteWhy does software development take so long? (3/28/2009)Saturday, March 28, 2009 from Jon KrugerEvery year, thousands of software development projects are [...]

By: Tim

Tim — Sun, 29 Mar 2009 16:26:47 +0000

Jon,

Great points all the way through.

My “however” though, is that bullet point 1, the ASP.Net Membership stuff…we had a recent project where we wanted to use that, but a client decision kept us from it. Integrating another membership app just wouldn’t work. Granted that’s just one case, and one I wish we didn’t have to deal with.

Also, the tons of brownfield projects we seem to inherit, a lot of these decisions have been made, and we get to deal with the consequences. It seems our biggest hurdle is still “just get it done,” rather than getting it done right.