![]() | This is the
talk page of a
redirect that targets the page: • Software development Because this page is not frequently watched, present and future discussions, edit requests and requested moves should take place at: • Talk:Software development |
![]() | This redirect does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() | The contents of the Software developer page were merged into Programmer on 12 May 2019. For the contribution history and old versions of the merged article please see its history. |
What is that? Google seems to know a lot about it, but wiki doesn't [1]. I'm a developer myself and have never heard about it. -- Michael Janich ( talk) 14:28, 3 March 2009 (UTC)
÷==Software development too easy==
I moved this from the main article, where Jesse60905 had left it:
Since when is software development easy? Some is, to be sure, but not all. Ever try to write an RTS with no noticeable latency, despite the fact that all the AIs are running pathfinding algorithms in a continuosly changing topology? — Frecklefoot | Talk 21:14, 22 May 2006 (UTC)
Jesse60905 again. Lost my pass and cba to retrieve it.We also eat alot of apples. Do you? Don't talk about things you don't know anything about. Sadly you are not aware of the fact I have taught myself quite a bit about programming on my own and sadly I stick to my original comment. Programming is quite easy considering the lack of any actual labor. 66.65.221.52 ( talk) 20:56, 13 March 2008 (UTC)
This page may need to be merged with programmer. Joncnunn 20:08, 11 April 2006 (UTC)
The single reference here is not sufficient to denote a clear difference between programmers and software developers. In many companies, the terms are synonymous, and the broader scope work is assigned to "programmer analysts" or "engineers". -- 207.154.89.62 ( talk) 23:01, 17 January 2008 (UTC) Furthermore, there are also people in some "programmer" positions that do much of the work that is applied to software engineers. And thus, I don't feel this specific term carries higher importance than programmer on the level that it requires a separate article. -- 207.154.89.62 ( talk) 23:05, 17 January 2008 (UTC)
has the software developer all the quality like software tester ,designer ,analyser , —Preceding unsigned comment added by 122.163.223.123 ( talk) 06:30, 24 February 2008 (UTC)
I cannot see how a single man's essay is being used as a definition for for differentiating "developers" and "programmers". Is the difference between programmers and developers Wikiality or is it reality? Park3r ( talk) 07:54, 4 March 2011 (UTC)
Sorry, but am highly amused to see classic wordsmithing games still current here.
Some of us know what we do, the rest of you have difficulties with the concepts. May be trying to glorify selves, or methods, or schools, not sure.
Leave the article alone. Let it stay.
Programming since 80, C since 84.
Stop walking on eggshells. Some are just coders, some are Architects like John Galt. Get over it. Individual variation drives evolution, baby.
From a scholarly perspective, merely preserving the cultural differences in the definitions of terms is more valuable than your eventual boring (and likely biassed) concensus.
But, have a nice day. — Preceding unsigned comment added by MajorVariola ( talk • contribs) 19:57, 8 April 2011 (UTC)
I'm very new here so take this for what it's worth...
I know it would make a big article, but would it be most useful to the reader to combine the best parts from all of these into a single article and redirect all of the current ones to it?
As has been stated, there is no widely accepted delineation between programmer, developer, analyst or software engineer. In any given organization, there's a hierarchy in roughly this order but the titles are more of a way of forcing a rigid structure on something that is really rather fluid. That characteristic is important.
Someone looking for career options or a non-IT manager deciding what title to hang on a new IT position they're creating should understand that, at least at this stage of maturity in the industry, responsibilities tend to follow the work flow and individual skills far more than duty assignments. Programmers develop products, analysts engineer complex systems and all of them write programs.
Hope this contributes something useful to the discussion. — Preceding unsigned comment added by Robertcwatson ( talk • contribs) 08:48, 24 October 2011 (UTC)
"In software engineering, it is more common to have the architecture, design, implementation, and test functions performed by a single individual."
Actually, the current status is that few companies hire persons for only "programming", "design" and test separately. You have the title "Software Developer" and do the design (with UML), "programming" based on your own design and run some tests for the use case to cover most of your code and functionality (module testing and coverity). It is rare for an individual software developer to "architect" something. Architecting is for the architects and architects don't have time to execute the individual cluster development (or even design) in any larger company.
The "Software Engineer" is just a buzzword to the HR and a legal term (military, health care). Do not mix it up with medical sciences. Medical sciences are much more structured and much more defined. Medicine is based to the study of the human body, which doesn't change much. On the other hand, software development is based on creativity, tools and processess. I.e. the software developer is creating these "bodies" for others to study so it is not that easy comparison. — Preceding unsigned comment added by 88.114.90.60 ( talk) 10:33, 4 December 2011 (UTC)
"This resembles the early phases of industrialization in which individuals would both design and build things."
Actually in practice the total separation of design and development in software R&D is harder than it seems. When you design a bridge, the process is clear. However, when you design a software subsystem, a highly skilled "programmer" might start to see errors in the design in the very early phases.
If we think about Agile development process coupled with strong separation of roles, it might correct some problems in the stiff structure of design and development. However, if we follow the waterfall development process, the "programmers" will happily execute the possibly flawed sketches.
Also in practice you need sketches to model what to be implemented (to save time and effort in the design phase). If you need sketches you also need highly skilled "programmers" how are capable of deep abstract thinking (if you want them to correct the flaws). If you document in too structured way (the waterfall, i.e. bridge designer), you might as well not document it as the code with good comments will be better than the hundreds of pages of code in pictures. — Preceding unsigned comment added by 88.114.90.60 ( talk) 11:42, 4 December 2011 (UTC)
Has anyone considered adding discussion of the lack of unity within the development community? There are growing numbers of local organizations to try and unite developers, but very few on the national level... I find it worth a conversation with all of the privacy conversation right now surrounding apps and no unifying voice to represent them. Wikime720 ( talk) 19:17, 10 May 2012 (UTC)
Hi,
I find about this article that the introduction is too long. I can't change it because my level of English is pretty poor.
Cordially, 82.224.165.208 ( talk) 15:17, 10 December 2012 (UTC).
I think the article since there is no disambiguation page, should indicate when the term Software Developer change from one who develops software to a Programmer. One who develops software can be a company such as Nintendo or an Individual like David Braben who creates software (the entire solution)... where as a programmer typically is an individual (which might be an employee).
Job ZhuLien ( talk) 13:17, 20 April 2018 (UTC) — Preceding unsigned comment added by 118.127.112.218 ( talk)
![]() | This is the
talk page of a
redirect that targets the page: • Software development Because this page is not frequently watched, present and future discussions, edit requests and requested moves should take place at: • Talk:Software development |
![]() | This redirect does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() | The contents of the Software developer page were merged into Programmer on 12 May 2019. For the contribution history and old versions of the merged article please see its history. |
What is that? Google seems to know a lot about it, but wiki doesn't [1]. I'm a developer myself and have never heard about it. -- Michael Janich ( talk) 14:28, 3 March 2009 (UTC)
÷==Software development too easy==
I moved this from the main article, where Jesse60905 had left it:
Since when is software development easy? Some is, to be sure, but not all. Ever try to write an RTS with no noticeable latency, despite the fact that all the AIs are running pathfinding algorithms in a continuosly changing topology? — Frecklefoot | Talk 21:14, 22 May 2006 (UTC)
Jesse60905 again. Lost my pass and cba to retrieve it.We also eat alot of apples. Do you? Don't talk about things you don't know anything about. Sadly you are not aware of the fact I have taught myself quite a bit about programming on my own and sadly I stick to my original comment. Programming is quite easy considering the lack of any actual labor. 66.65.221.52 ( talk) 20:56, 13 March 2008 (UTC)
This page may need to be merged with programmer. Joncnunn 20:08, 11 April 2006 (UTC)
The single reference here is not sufficient to denote a clear difference between programmers and software developers. In many companies, the terms are synonymous, and the broader scope work is assigned to "programmer analysts" or "engineers". -- 207.154.89.62 ( talk) 23:01, 17 January 2008 (UTC) Furthermore, there are also people in some "programmer" positions that do much of the work that is applied to software engineers. And thus, I don't feel this specific term carries higher importance than programmer on the level that it requires a separate article. -- 207.154.89.62 ( talk) 23:05, 17 January 2008 (UTC)
has the software developer all the quality like software tester ,designer ,analyser , —Preceding unsigned comment added by 122.163.223.123 ( talk) 06:30, 24 February 2008 (UTC)
I cannot see how a single man's essay is being used as a definition for for differentiating "developers" and "programmers". Is the difference between programmers and developers Wikiality or is it reality? Park3r ( talk) 07:54, 4 March 2011 (UTC)
Sorry, but am highly amused to see classic wordsmithing games still current here.
Some of us know what we do, the rest of you have difficulties with the concepts. May be trying to glorify selves, or methods, or schools, not sure.
Leave the article alone. Let it stay.
Programming since 80, C since 84.
Stop walking on eggshells. Some are just coders, some are Architects like John Galt. Get over it. Individual variation drives evolution, baby.
From a scholarly perspective, merely preserving the cultural differences in the definitions of terms is more valuable than your eventual boring (and likely biassed) concensus.
But, have a nice day. — Preceding unsigned comment added by MajorVariola ( talk • contribs) 19:57, 8 April 2011 (UTC)
I'm very new here so take this for what it's worth...
I know it would make a big article, but would it be most useful to the reader to combine the best parts from all of these into a single article and redirect all of the current ones to it?
As has been stated, there is no widely accepted delineation between programmer, developer, analyst or software engineer. In any given organization, there's a hierarchy in roughly this order but the titles are more of a way of forcing a rigid structure on something that is really rather fluid. That characteristic is important.
Someone looking for career options or a non-IT manager deciding what title to hang on a new IT position they're creating should understand that, at least at this stage of maturity in the industry, responsibilities tend to follow the work flow and individual skills far more than duty assignments. Programmers develop products, analysts engineer complex systems and all of them write programs.
Hope this contributes something useful to the discussion. — Preceding unsigned comment added by Robertcwatson ( talk • contribs) 08:48, 24 October 2011 (UTC)
"In software engineering, it is more common to have the architecture, design, implementation, and test functions performed by a single individual."
Actually, the current status is that few companies hire persons for only "programming", "design" and test separately. You have the title "Software Developer" and do the design (with UML), "programming" based on your own design and run some tests for the use case to cover most of your code and functionality (module testing and coverity). It is rare for an individual software developer to "architect" something. Architecting is for the architects and architects don't have time to execute the individual cluster development (or even design) in any larger company.
The "Software Engineer" is just a buzzword to the HR and a legal term (military, health care). Do not mix it up with medical sciences. Medical sciences are much more structured and much more defined. Medicine is based to the study of the human body, which doesn't change much. On the other hand, software development is based on creativity, tools and processess. I.e. the software developer is creating these "bodies" for others to study so it is not that easy comparison. — Preceding unsigned comment added by 88.114.90.60 ( talk) 10:33, 4 December 2011 (UTC)
"This resembles the early phases of industrialization in which individuals would both design and build things."
Actually in practice the total separation of design and development in software R&D is harder than it seems. When you design a bridge, the process is clear. However, when you design a software subsystem, a highly skilled "programmer" might start to see errors in the design in the very early phases.
If we think about Agile development process coupled with strong separation of roles, it might correct some problems in the stiff structure of design and development. However, if we follow the waterfall development process, the "programmers" will happily execute the possibly flawed sketches.
Also in practice you need sketches to model what to be implemented (to save time and effort in the design phase). If you need sketches you also need highly skilled "programmers" how are capable of deep abstract thinking (if you want them to correct the flaws). If you document in too structured way (the waterfall, i.e. bridge designer), you might as well not document it as the code with good comments will be better than the hundreds of pages of code in pictures. — Preceding unsigned comment added by 88.114.90.60 ( talk) 11:42, 4 December 2011 (UTC)
Has anyone considered adding discussion of the lack of unity within the development community? There are growing numbers of local organizations to try and unite developers, but very few on the national level... I find it worth a conversation with all of the privacy conversation right now surrounding apps and no unifying voice to represent them. Wikime720 ( talk) 19:17, 10 May 2012 (UTC)
Hi,
I find about this article that the introduction is too long. I can't change it because my level of English is pretty poor.
Cordially, 82.224.165.208 ( talk) 15:17, 10 December 2012 (UTC).
I think the article since there is no disambiguation page, should indicate when the term Software Developer change from one who develops software to a Programmer. One who develops software can be a company such as Nintendo or an Individual like David Braben who creates software (the entire solution)... where as a programmer typically is an individual (which might be an employee).
Job ZhuLien ( talk) 13:17, 20 April 2018 (UTC) — Preceding unsigned comment added by 118.127.112.218 ( talk)