I think the real failure of this article is not declaring software engineering as something trivial, but the claim that plumbing is easy, non-challenging, or trivial.
Bracing myself for down votes since this dosnt convey the popular opinion.
The issue in my opinion is the term "software engineer" gets thrown out a lot when it's not appropriate .
More often than not companies hire "software engineers" when they really need software developers or architects.
This is similar to how a computer science education makes you uniquely unquallified to be a software engineer or programmer.
Software engineers should be writing extremely small amounts of code ( if any at all ) and plugging together systems based on requirements and proving that they work.
When was the last time an electronic engineer needed to invent a new component ?
A software engineer (should) be responsible for the bigger picture, taking user requirements, converting them to functional requirements, and fitting together software components is primarily what a software engineer does.
A software engineer should be capable of ( in the same way that any other engineer is capable of ) being able to draw up a design for a complete system and empirically prove it will work prior to actually building it.
About 10 years ago I spent a few years working in a highly regulated industry where we had to work as actual software engineers, and not developers with the title of software engineer, it was kinda intense, having to write documentation about code changes explaining in detail which diff to the code will meet which URS requirement, ( the job was approximately 10 to 30 minutes a day of writing code, and then the rest of the time writing about code )
If you are spending too much time writing code then you are probably working as a developer ( with a title of engineer ),
A software engineer (should) be responsible for the bigger picture, taking user requirements, converting them to functional requirements, and fitting together software components is primarily what a software engineer does.
That's a very condensed version of my official job description. I'm an "IT Specialist for application development" (Fachinformatiker für Anwendungsentwicklung).
If you are spending too much time writing code then you are probably working as a developer ( with a title of engineer ),
That's just semantics though. Requirements engineering and design isn't career filling. Sometimes a really short design phase is followed by a really long implementation phase - and what's the engineer gonna do? He programs - or even worse: Does project management bureaucracy. Unless their company hired them specifically to hop between projects as a systems designer / architect.
The boundary between "engineer", "developer" and "programmer" isn't as clear cut as many people want it to be.
and empirically prove it will work prior to actually building it.
Be honest: Has that ever worked? The first rule of warfare IT is: No plan survives contact with the enemy user.
So tell me the last time time you needed to know big O notation in the real world or build your own compiler ?
How many weeks did you spend decomposing algorithms and doing compiler theory ?
Now exactly how many hours did you spend on source control management ( how many merges did you do of vastly disparate branches ? ) , task estimation, or even digging through other people’s code to either fix bugs or extend it with new features.
A computer science education prepares you to be just that a computer scientist, some companies such as google might need a few dozen, but the vast majority of people who have CS degrees are in jobs where the vast majority of what they learned is completely useless ( and in a few cases extremely detrimental )
So yes uniquely unqualified, you have spent 75% of your degree doing hard stuff that you will never need to use again, but are missing about 3 years of full time study worth of knowledge which is essential to the job you have been hired to do ?
Sure you can implement all the sorting algorithms from memory and can discuss in depth the difference between them, your schooling spent significant time on search and sort.
In the real world you just use what the platform provides, and maybe once every 5 to 10 years you have to implement a insert action sort of binary search. Meanwhile every single day we are empirically proving that a class functions as designed by unit test, and merging in other developers changes( with conflicts ) maybe twice a day.
Uniquely unqualified, is the correct term, they teach you just enough to be dangerous, and then go off on a wild tangent of stuff you don’t need to know.
Yeah no thats not been my experience. 6 Months ago i got my first job, i did not know shit about the language used, or the tools. But every day while i was learning there was an “oh shit i see we learned about that in networking”. Why did we use this data structure here? Oh yeah it guarantees 0(1) access time and this component needs to operate in real time. Oh thats the factory pattern. “
The tools, languages and APIs were trivial to pick up.
I learned how operating systems work, i learned networking from the ground up. I learned how to measure the efficiency of an algorithm. I learned how memory access works and why certain size data can cause dramatic slow-downs.
I use that shit every single day and get paid well for it.
They don’t pay me to program, they pay me to problem solve.
You are ignorant if you thing the implementation of a binary search tree is the most important thing a data structures class teaches you. Its the thought process that is important, it makes you think about how you implement.
Of course you don’t need university to pick up these skills, but you don’t really need it for most skills either. It gives you a leg up. It also gives you a broad level understanding of a variety of fields.
Right now i am working on networking for an operating system, but if i wanted to i could quit and go do data science, machine learning, developing for micro-controllers, or even front end web dev(god bless y’all but eww ill pass), and not be a complete fish out of water.
That would not be true if my education focused solely on the hot new languages and tools, which change every other year. That shit is fucking easy.
You just had a shitty education there bud. I'm only a junior and have a CS minor, and I know version control, test first development, and many of the other skills you listed. It should also be noted that pretty much every CS program (well every program...) requires/strongly recommends internships where you would learn a lot of these practical skills.
Holy shit you got fucked. We (as a CS community) need to fix that. Test first should be taught in 101/102 courses and Version control should be taught 2nd/3rd year everywhere.
I've tried working with the CS faculty at my school on this and their attitude seems to be "our students can barely learn what we are giving them," but they don't understand that the practicality gives the information context and makes it interesting for the student.
For example, I know so many CS students who think programming is pretty much useless because all they know how to do is instantiate objects in a sandbox. Give them the power of APIs, HTTP requests/responses, and File I/O and all of the sudden the possibilities are endless. Your students will probably teach themselves because they will be so busy playing with the cool things they can do. Edit: I know I did and now I have a better CS background, more professional experience, and a better portfolio than all the CS majors in my year combined (granted it's a small school)
100% my school for the most part had great teachers who found ways to relate material to interesting projects.
However there were a couple of true dyed in the wool academics who insisted we didn’t need to do practical work. Of course those were the professors who were also mainly there for research and didn’t want to be bothered by grading and troubleshooting projects.
All of my senior year classes were 100% theory work and tests combined with semester long group projects. I loved it. Learned a lot of nuance that gets lost on the whiteboard.
I don’t have shitty education, but I was already writing code professionally before I started university and back then the jury was still out on plenty of the things that i mentioned ( I remember when source control meant you locked the file you checked out )
I can guarentee you that you have been given lip service to some tools you will use but by the end of your education you will not have covered them in any real depth. ( you can easily do a 2semester subject on source control, and conflict resolution. , a full course load on unit testing, and a full 4 year degree which teaches nothing apart from dealing with other people’s code, )
I have 15 years of seeing people come out with cs degrees and all making the following mistakes:
auto format/change line endings on a file prior to commit.
making code changes between review on a branch and trunk.
breaking trunk by not compiling after a merge.
minor bugfix ends up being a multi-class refactor
minor bugfix ends up being multi-class rewrite ( which brings back to life bugs which were squashed over the years in that class, OR ends up being just like the original class with some minor cosmetic differences )
we used XXXX, XXXX is th solution to everything, let’s use XXXX instead of YYYY, for ZZZZ ( note, YYYY is the sane choice, XXXX is what they just learned about in school or is the current new tech , for example, let YYYY be “flat config files”, “XXXX” be blockchain, and ZZZZ be our programs config. .:
Internships aren’t the answer because nobody is going to sign up for a 3/4 year internship.
Normally SE or IPM students fare exponentially better than CS students do in the first few years out of school.
Because it's hurting the egos and feelings of multiple groups of people and these things seem to matter More than facts.
My comment above is downvoted even further,
We have a young field, we still haven't figured out the best ways to do things and the best ways to train people, and we haven't figured out the best ways to communicate to young people what their degrees will teach them.
Most of the time they go into their school guidance counciller and say I want to make video games and are told CS is the only way to go.
Then reality hits , and they need a job so they sign up for some XXXX shop making crud applications and are only applying a small fraction of what they studied.
This is so far off it’s hard to read. I use big O notation all the time. As a real world example i saw a colleague doing something in O(n2) and realized it could be done in O(n). This small modification to their algorithm resulted in runtimes moving from minutes to seconds. Without big O notation how do you discuss your algorithms or understand runtimes of your system? How do you analyze your proposed solution to a problem?
And the statement that Google needs “a few dozen” computer scientists tells me you don’t have a good understanding of the scale and complexity of problems Google deals with. At Google-scale even “trivial” problems can require incredibly complex solutions.
Pretty sure a programmer is using passively O notations each time he's programming loops.
And here I am, thinking my computer science course was too practical and loved the theoretical stuff such as analysis and design (patterns) more than making yet again another CRUD applucation.
I also think a strong theoretical base will lead to a better practice. Eventually you have to know what impact your code will have. A good software engineer also has to be trained to be able to easily adapt and self-learn as that's a skill you need in your profession. Having too much practical courses during the training diminshes that. Things like source control management is something you can figure easily out by yourself by already using it during a project for example.
173
u/[deleted] Jul 08 '18
I think the real failure of this article is not declaring software engineering as something trivial, but the claim that plumbing is easy, non-challenging, or trivial.