Search Results for "Creating Software"

“If debugging is the process of removing bugs, then programming must be the process of putting them in.”
-Edsger Dijkstra

Testing is arguably the most important step in any software project and also one of the most neglected steps. In most cases, testing is missed because clients don’t realize the importance of it and aren’t willing to pay for, or take the time to have the developers test properly.

In a perfect world, code would be thoroughly tested before it ever goes into the wild, but this just isn’t possible. Here are a few tips and tricks on testing so your product will never be released without even a little bit of testing.
Click for more →

To a developer, their desk is like athelete’s equipment; vital to occupation. If a hockey players stick breaks because it’s quality is sub-par they could lose a game. The same goes to a developers desk, if the desk isn’t stocked with the correct equipment it could impair the developer in their work.

Here are 10 things that every developer should have at their desk.
Click for more →

Software takes a long time to make. You first need to get the requirements from the client. Once you’ve gotten the requirements you then need to spend the time to properly design your product, drawing out paper prototypes, creating use case diagrams and other things like that.

Now that you’ve done all that, we’ll have a look at the third part of the Creating Software series: Starting to Code. Today we’ll look at different ways to code and the importance of testing as you code not afterwards.
Click for more →

Creating software is difficult. You need to first get the requirements from the client (or create them yourselves), then you’ll use the requirements and design a working system. Once you’ve designed the system, turn the design into code. Next you’ll test your code to make sure it works and finally deliver the completed project to the client.

Today I’m going to look at the second part of the Creating Software series: The Design phase. There are a number of aspects to designing software. You need to take the requirements you gathered previously and start to create your software. At this point, you’ll have very little code (and possibly none at all). Don’t let this fool you though, the design phase is extremely important, and many projects have failed because they either didn’t design, or improperly designed their software.

Here are three things you can do in the design phase to make your software project more likely to succeed.
Click for more →

This week has been a great week for us here at devjargon as well as around the blogosphere. We’ve had a number of great articles and comments here and have seen a number of great articles emerge around the web. Here’s an outline of some of our great stuff this week.

• 15 Reasons Why I Became a Developer
• Create Software: Getting the Requirements
• Love to Fail: 3 Tips to Help Learn From Failure

Click for more →

Most software projects follow a fairly similar path from creation to completion. They start with talking to the user, getting the requirements for the project. It moves to the next stage, taking the requirements and getting them on paper (designing your software). After that, you get into coding, testing, bug fixing and more testing, and finally, you show the finished project to the client.

Now I know that I’ve outlined a fairly crude time-line but thats the basics of it. Over the next few weeks I’m going to go over each of the parts of the software project time-line and outline a few of the things that I find difficult.

Today I’m going to start off with the first in the list and also the hardest in the time-line; talking to the client and getting the requirements.
Click for more →