4 Copy-editing
source | link

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, iI would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/ewhatever to be successful in aan entry level-level position. A willingness to learn, some enthusiasm, and a good team fit are (atleastat least in my experience) huge factors in being successful in an entry level-level role.

However, to better answer the question from an educatorseducator's perspective.: I think dealing with mess is under emphasized. A lot, and iI mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an internsintern's face when iI told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. (Bonus cool-guy points if you added a feature you needed to a tool you found lacking).) I think it would be great to see this (dealing with huge messy projects) added to more csCS degrees. There is an art to it.

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, i would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/e to be successful in a entry level position. A willingness to learn, some enthusiasm, and a good team fit are (atleast in my experience) huge factors in being successful in an entry level role.

However, to better answer the question from an educators perspective. I think dealing with mess is under emphasized. A lot, and i mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an interns face when i told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. (Bonus cool-guy points if you added a feature you needed to a tool you found lacking). I think it would be great to see this (dealing with huge messy projects) added to more cs degrees. There is an art to it.

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, I would say nothing. I don't necessarily think you need to be the best at TDD or GIT or whatever to be successful in an entry-level position. A willingness to learn, some enthusiasm, and a good team fit are (at least in my experience) huge factors in being successful in an entry-level role.

However, to better answer the question from an educator's perspective: I think dealing with mess is under emphasized. A lot, and I mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an intern's face when I told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. (Bonus cool-guy points if you added a feature you needed to a tool you found lacking.) I think it would be great to see this (dealing with huge messy projects) added to more CS degrees. There is an art to it.

3 added 645 characters in body
source | link

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, i would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/e to be successful in a entry level position. A willingness to learn, some enthusiasm, and a good team fit are (atleast in my experience) huge factors in being successful in an entry level role.

However, to better answer the question from an educators perspective. I think dealing with mess is under emphasized. A lot, and i mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an interns face when i told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. Bonus(Bonus cool-guy points if you added a feature you needed to a tool you found lacking). I think it would be great to see this (dealing with huge messy projects) added to more cs degrees. There is an art to it.

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, i would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/e to be successful in a entry level position. A willingness to learn, some enthusiasm, and a good team fit are (atleast in my experience) huge factors in being successful in an entry level role.

However, to better answer the question. I think dealing with mess is under emphasized. A lot, and i mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an interns face when i told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. Bonus cool-guy points if you added a feature you needed to a tool you found lacking.

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, i would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/e to be successful in a entry level position. A willingness to learn, some enthusiasm, and a good team fit are (atleast in my experience) huge factors in being successful in an entry level role.

However, to better answer the question from an educators perspective. I think dealing with mess is under emphasized. A lot, and i mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an interns face when i told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. (Bonus cool-guy points if you added a feature you needed to a tool you found lacking). I think it would be great to see this (dealing with huge messy projects) added to more cs degrees. There is an art to it.

    Post Undeleted by Scheme
2 added 645 characters in body
source | link

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

InTo answer your question literally, i would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/e to be successful in a entry level position. A willingness to learn, some enthusiasm, and a good team fit are (atleast in my own experience when hiring) huge factors in being successful in an entry level developersrole.

However, I try to better answer three questionsthe question. I think dealing with mess is under emphasized. A lot, and i mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an interns face when i told him there are about them60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. Bonus cool-guy points if you added a feature you needed to a tool you found lacking.

  • Would they be a good fit?
  • Can they understand basic programming concepts?

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

In my own experience when hiring entry level developers, I try to answer three questions about them.

  • Would they be a good fit?
  • Can they understand basic programming concepts?

What is missing from a typical undergraduate program, or not sufficiently emphasized, that a person needs to know for successful employment in a software development position?

To answer your question literally, i would say nothing. I don't necessarily think you need to be the best at TDD or GIT or w/e to be successful in a entry level position. A willingness to learn, some enthusiasm, and a good team fit are (atleast in my experience) huge factors in being successful in an entry level role.

However, to better answer the question. I think dealing with mess is under emphasized. A lot, and i mean a lot of software development is horrendously messy. Seriously. I remember with vivid clarity the look of disgust on an interns face when i told him there are about 60,000 files in the solution he would be working on (so sorry John). To me a good way to get that experience is as others have said: open source. Bonus cool-guy points if you added a feature you needed to a tool you found lacking.

    Post Deleted by Scheme
1
source | link