Software developer

Microsoft is one of the world's most famous software development companies.^[1]

A software developer is a company or person that creates software - either completely, or with other companies or people. The phrase 'software development' often means more than just designing or writing the software, it usually means someone who manages the project, or does only the main things. Most software developers are still led by a lead programmer (a software engineer that guides the project).

A programmer generally only writes code,^[2] but a software developer usually will:

Work out the requirements to use the software
Develop prototypes
Work on the budget and finances of the project
Perform testing, or get ideas from testers they select before the software is released
Work on demonstrations or samples
Release updates and patches for the software.

Software Developer Media

The TEAF Matrix of Views and Perspectives
Example of the interaction between business process and data models
Anjuta, a C and C++ IDE for the GNOME environment

References

↑ Tim Chen. "Introduction to Testing at Microsoft" (PDF). Retrieved 2008-11-29.
↑ Eric Sink. "Small ISVs: You need Developers, not Programmers". Retrieved 2008-11-29. A programmer is someone who does nothing but code new features and (if you're lucky) fix bugs. They don't write specs. They don't write automated test cases. They don't help keep the automated build system up to date. They don't help customers work out tough problems. They don't help write documentation. They don't help with testing. They don't even read code. All they do is write new code.

This short article about technology can be made longer. You can help Wikipedia by adding to it.

[Microsoft-1] Tim Chen. "Introduction to Testing at Microsoft" (PDF). Retrieved 2008-11-29.

[Sourcegear_2005-2] Eric Sink. "Small ISVs: You need Developers, not Programmers". Retrieved 2008-11-29. A programmer is someone who does nothing but code new features and (if you're lucky) fix bugs. They don't write specs. They don't write automated test cases. They don't help keep the automated build system up to date. They don't help customers work out tough problems. They don't help write documentation. They don't help with testing. They don't even read code. All they do is write new code.

[1]

[2]