The hardest part of software development has nothing to do with code

30Jun/1012

The hardest part of software development has nothing to do with code

People who complain about how much “more” code they have to write in an MVC project versus a Webforms project, or really any project, prove to me that they have absolutely no idea where the REAL work is in ANY development project.

The main work in any software development project is FIGURING OUT WHAT TO BUILD. How you build it is trivial compared to the amount of time and effort you SHOULD put into discovering the users needs and working with them to solve their problems and make their life better.

Remember, that’s the number one purpose for any piece of computer hardware or software. This cannot be stressed and repeated enough.

COMPUTERS SHOULD MAKE OUR LIVES BETTER!

How do we write programs that make lives better? By writing programs that fulfill their needs and ease the pain of their work. We still aren’t at a point where we have a common, easy to understand vocabulary when it comes to build software. We often get it wrong the first, second, and third times. That’s where the discipline and engineering comes into play.

Filed under: Agile, General, MVC, Tutorials Leave a comment

CAPS!

What is it with THE FREAKIN’ CAPS?!
Pingback: Tweets that mention The hardest part of software development has nothing to do with code | Lazycoder -- Topsy.com
Matt Long

To assert that by favoring one framework or tool over another means that one has “absolutely no idea where the REAL work is in ANY development project” is quite ridiculous.

Having a preference to a tool or “complaining” about another has nothing to do with anything you’ve addressed here.

While I agree that working with users to discover their needs etc is paramount, how you go about building a solution is hardly “trivial”.
http://bentleydavis.com Bentley Davis

Wouldn’t writing less code in general allow you to prototype faster allowing you to work through the design options with your customer more efficiently with quicker and presumable more iterations getting to your customers needs better?

Help me understand how more code to accomplish the same thing does not slow down that process and reduce impact.

Although, I didn’t think MVC really had significantly more code.
http://www.lazycoder.com Scott

Bently and Matt,

Yes the choice of framework can affect how much code you have to write and affects how long it takes you to write the application. But if you write the wrong application or get the functionality wrong, you end up having to write twice as much code no matter what language or framework you choose because you have to write the code twice.

The Agile Manefesto and agile practices help to address figuring out WHAT to build more than HOW to build it.

Caps: WHAT DO YOU MEAN?!?!
http://blog.failbettergames.com Alexis Kennedy

+1 for Scott!

@Bentley “Although, I didn’t think MVC really had significantly more code.”

For a number of years Microsoft bigged up the declarative stuff in .aspx files, not to mention all those wizards and right-click property setters on the visual designer. You just can’t do that stuff with MVC (natively or obviously) – you have to write procedural code. When you’re coming from WebForms, it’s natural to feel that you’re having to hand-write the stuff that the tools took care of for you. I imagine this is the response Scott means.
John

Yup, it’s all about the business rules. The code really is the trivial part.
http://bobcravens.com Bob Cravens

I suspect that most developers have a requirements team that “figures out what to build”. The requirements elicitation process may not be congruent with the skill set / desires that most devs have. Devs need to be plugged into the process of translating the customer requirements into code. In a small shop, maybe the devs have to gather requirements. but in general this may not be the best use of their time.

It could be that we hear more discussions about coding / platforms / etc because we (I am a dev) hang around other devs, read dev blogs, subscribe to devs on twitter…etc. I think if we were requirements engineers (or interacted with more of them), the discussion would be different.
http://www.jouercasino.eu/ casino en ligne

Greetings! We are conducting a casino online. To all interested in online games. Visit our site for more information.. Play now and enjoy our site! Happy gaming!
Pingback: | Lazycoder
http://www.guide-des-meilleurs-casinos.com casino en ligne

Computers should make ours life better ? I don’t think so …
but if you want to play with les
meilleurs casinos en ligne u can
http://www.gagner-euro.com/betclic.php Betclic

thanks for sharing
Anywho

Ha ha ha! This post only shows that the author is the one who has “absolutely no idea where the REAL work is in ANY development project”. I bet you are either a PM or a requirements “engineer”. Why don’t you try to switch with a real developer for a week or so and then talk.
fake rolex watches

As the business grows, rolex replicas has also jumped into an international brand. It is worth mentioning that,replica rolex watches is the ancestor of today’s brand-oriented, in order to protect the quality and brand name will be printed on their products, the history of fashion in the world, is the first one first.rolex replica watches, fake rolex, fake rolex watches .fake omega watches
replica omega watches
tag heuer replica watches
tag heuer watches.http://www.erowatch.com

Herding Code 87: Jeff Atwood on Area 51 and Stack Overflow » « Herding Code 86: Saqib Shaikh on Accessibility and Developing with Limited Sight

Subscribe to Blog via Email

.NET HTTP Abstractions group

Subscribe to .NET HTTP Abstractions

Email:

Visit this group

Lazycoder