|
Marc Clifton wrote: the poor kid hasn't had any school exposure to languages like C#, and no exposure to modern tools (IDE's, debuggers, etc), again, anything he's learned he has learned on his own.
Honestly I think it's a plus. Learning how to think, how to write algorithms and the hard science is more important than leanring the usage of tools. A properly trained mind can master any tool in a reasonable amount of time, even after paradigm shifts ot big technological changes. An ignorant mind who's been trained only in the use of some tools won't be able to adapt as easily. Of course every person is a world in itself so it's a GENERAL consideration.
It's not the Education System that has to teach jobs for the companies, that is responsibility of the companies themselves. The Education System must create people, with the skills and mindset to approach their trade and life itself.
In Italy we have Professional Schools, they are high schools that teach 5 years straight a trade, and we have Technical Schools, which are basically light engineering (up to 30 years ago the graduated students from those high schools were officially named Junior Engineers, with legal value). At the Technical University I (coming from a Technical high school) had the chance to confront with students coming from Professional Schools: they looked like monsters. They knew all the current tools and were able to quickly put up some sort of working... things. But they weren't able to design a simple algorithm or to learn plain C, because they were only trained to use a couple of languanges... of which they botched the exams. And they were anything but stupid, mind you.
It's also the biggest chasm between Computer Science and Computer Engineering, at least in my city. CS students exit with many, many more "current" skills than us in CE. And quickly lose value and adaptability over the next 5-10 years. Our Technological University clearly stated that their most radicated goal is to make us as much tool-independent as possible.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
OriginalGriff wrote: except the in depth stuff has vanished in favour of "how to use FarceBook in VB"
You've got that damned right.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm sure the spirit of the article won't be as of this discussion[^] 
Quote: did college teach you engineering skills
Yes but that would be basic. But most knowledge comes from applying on a real work environment and building your experience from project to project.
Wonde Tadesse
|
|
|
|
|
I keep seeing these posts here about software engineering is dead, developers don't exist anymore, yadda yadda.
I have absolutely no idea what the blazes you guys are talking about. I've been a software engineer for 33 years and we are more busy now than ever before. It's insane we are so busy. Yes, developing systems in C# and SQL, and 100 other technologies linked together. We have to force ourselves to stop for most of today in order to interview 3 new candidates to join the team.
The entire world is now software. Even my car runs on software. Software engineers are gods.
As for your other question, I studied electrical engineering. Every single thing about systems and application design I taught myself, or from mentors. I have never stopped learning new things and exploring new technologies. When I get home, I switch to my home projects, mostly involving security, home automation, video streaming, communications, avionics... I try to sleep once in a while.
|
|
|
|
|
I get the feeling that Marc's post has less to do with software engineering being dead and more to do with the cult of the script kiddies who seem to want to jump onto the latest shiny, rather than applying rigour and discipline to build and maintain systems. Marc has just been through a particularly bruising application of this where a well engineered system has been cast aside to allow the children to write a new Python based one, from scratch, simply because they have the CTO's ear.
This space for rent
|
|
|
|
|
Got it. I see that too. You have swarms of high-schoolers who are only interested in writing games for iOS. But we've had that kind of people in our midst since the beginning. Important systems running on big hardware still run the world. I laugh at people who say the iPhone is replacing the desktop. If anything, I want my desktop system to be even more powerful. My friend just added a 43 inch monitor to his development workstation. I don't see myself sitting in a corner building systems on a 4.5 inch phone. Can you imagine doing AutoCAD drawings of a space station on an iPhone? I can't.
Don't get me wrong, those toys are really cool, and I use one myself. But that doesn't take away from the real data processing needs of the world. And the infrastructure that runs those millions of iPhones are not running on little iPhones. They are running on real hardware. Built by real engineers.
|
|
|
|
|
If you send me a picture of yourself I'll start building your statue right away.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Pete O'Hanlon wrote: Marc's post has less to do with software engineering being dead and more to do with the cult of the script kiddies who seem to want to jump onto the latest shiny, rather than applying rigour and discipline to build and maintain systems.
Two sides of the same coin.
Pete O'Hanlon wrote: to allow the children to write a new Python based one, from scratch, simply because they have the CTO's ear.
The irony here is that because of hardware and browser hosting issues, Python got thrown out (I think) and it's being rewritten in F#.
More irony. Particularly since the only junior guy, while he has FP experience, has never used F# and I had to tell him "if you use the debugger, you'll see that your property assignment isn't working because you need to use the <- operator to make an assignment to a mutable structure, not the = operator.
Marc
|
|
|
|
|
You can't blame the "children" for that, they didn't make that decision. The CTO did. And calling them "children" is probably a little patronising, we were all young once.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Basildane wrote: I've been a software engineer for 33 years and we are more busy now than ever before. It's insane we are so busy.
But that's point -- you're an engineer because you have 33 years of experience. But it seems that very few people, particularly (as Pete pointed out the motivation for my post) young script kiddies and CTO's that think they're programmers because they coerce a few open source projects to work together to build a website.
Colleges/universities don't seem to teach engineering skills, managers freak out when you write code that uses a publisher/subscriber pattern, and Agile (in the ways I've seen it implemented) doesn't give a sh*t about up front design.
Marc
|
|
|
|
|
Yeah.
Irony: My son is now at the script kiddie age (14). So, his mom and I set him up with a VMWare platform with hosts running Linux. No GUI's are allowed. He builds and hosts servers from command line only. One year on, he's kicking ass and has paying customers.
|
|
|
|
|
Basildane wrote: He builds and hosts servers from command line only. One year on, he's kicking ass and has paying customers.
That is awesome!
Marc
|
|
|
|
|
The techniques used to build a treehouse* don't work when building a cathedral nor vice versa. The same is true of IT - you need to know what type of a thing you are building before deciding what techniques to use.
Sadly in my experience in a very significant percentage of cases that first step is not taken. We decide the techniques to use based on factors external to what we are going to do with them - including external influencers (Gartner &c.) and existing experience.
I learnt database design (Codd's laws) and object oriented programming at college. This was a long time ago but I imagine things like MVVM would be in whatever has replaced my course.
Sadly I was also taught monolithic system design and it has taken me 2 decades to undo that.
* This is not meant to be pejorative - I'm just illustrating the point. Personally I prefer treehouses to cathedrals 
|
|
|
|
|
Duncan Edwards Jones wrote: Sadly in my experience in a very significant percentage of cases that first step is not taken.
Indeed, it's what I'm seeing happen -- throw some code together, plug in some open source solutions, assume they work correctly, etc.
It's all driven by the "we need to get product out the door now."
Marc
|
|
|
|
|
The cult of "minimum viable product" strikes again.
I usually fall back on the argument - "If this were a medicine would you feel confident in taking it yourself? If this were an airline would you fly with it?"
(Again - if this is a treehouse type of project then the medicine is a placebo and the airline is a lego toy)
|
|
|
|
|
Engineering looks like a pile of sheets with a lot of poorly drawn correct diagrams, awesomely drawn wrong diagrams, scraped lines, hastily written and more hastily forgotten "illuminations". Followed by smaller and smaller piles of similar sheets of improved quality.
It's the most abstract and time consuming part, requiring focused meetings (not scrum, not at all) with the minimum necessary number of people and open minds - which means that after an hour everyone goes back to solo thinking and meet the next day.
The only engineering skill that I learnt in college is to be as rigorous and factual as possible. Record all the results of the experiments, all the intermediate results and the procedures used to obtain those intermediate results and the indexes used for the decisions. Everything else is experience and personal initiative - the first requires time ("it takes a year to make a year of experience"), the latter is a tract, you have it or you don't have it.
College also taught me methods to be factual and rigorous, in the form of Mathematical Analysis, Logic, Statistics and courses of Engineering - they are useful in that they make you design standard cases with the tools used to solve them the first time and then explaining how they were solved in the first place. Basically they are history classes on engineering matters.
As for design patterns I have some trouble with the term because I have a colleague (self-taught) who misuses them on regular basis because deep down he does not understande them and makes things harder for everyone else. Then reasoning on the real meaning of the term I recognize that I use them as well, because THEY WORK, even if usaully in my team we prefer reinventing the wheel. We do embedded highly customized systems so it's usually the saner thing to do - standard components or pre-cooked desgin patterns never worked for us in the past 25 years.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Marc Clifton wrote: how do you practice it in, well, practical terms?
Someone assigns tasks during a sprint.
Marc Clifton wrote: for those with some level of college degree, did college teach you engineering skills
Schools are there to make sure you become obedient, not to convey knowledge.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Quote: Schools are there to make sure you become obedient, not to convey knowledge.
Exactly. That's why we home-school.
|
|
|
|
|
I would contend that colleges are designed to teach problem solving, in general. They are a way of transitioning from the "rigid tell me what to do" of public high schools to the "you're on your own" mentality of modern business. Some are able to put those pieces together themselves without college. Some will never understand where to start solving a problem no matter how long they might be in school. For most, however, college guides the graduates to become self-motivating and, more importantly, self-sufficient.
I would agree, and argue that it is a positive thing, that colleges do not teach what businesses want. Such information is transitory while the skills that college teaches are permanent.
|
|
|
|
|
As a member of the BCS over here in the UK I remember attending a seminar from a software engineer from the Ministry of Defence who was involved in the development of avionics and navigation software for their jets. And it was eye opening exercise. I had no idea development teams actually used things like Z (the formal programming language) in practice. The level of discipline was far beyond anything I had encountered in real life. Their procedures were extremely disciplined.
The key point is that engineering is a set of rigorous disciplines used to build applications. The level to which we employ these disciplines depends on the goals, costs and risks. It takes time, effort, cost and skill to build these sorts of systems. You therefore need to weigh these against the goals. Obviously in avionics, a software bug can lead to a fatality so higher levels of engineering discipline are required than for say a web site.
I graduated with a degree in Computer Studies nearly two decades ago where I was taught software design, Z, formal methods, computational mathematics, data structures etc. All of these can be thought of as engineering disciplines.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Great response. Thank you!
Marc
|
|
|
|
|
Dominic Burford wrote: I had no idea development teams actually used things like Z
God!
You've just brought back such horrible memories!
Working for the MoD, that was great -- we had access to any mess we wanted, for our meals (the chiefs and POs' ended up as the favourite, except on Fridays, which was officers' mess all the way).
But Z!
Logic, my @rse! It has to be the stupidest and most unintuitive way in the world to organise data structures, et al.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: It has to be the stupidest and most unintuitive way in the world to organise data structures, et al.
But.......it is mathematically provable, and that's the point. I must admit I found Z to be intuitive as it aligns with mathematics.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Hey, I don't need mathematical proof that a light switch works to enable me to switch on the light.
If you want people to find creative solutions to problems, it's better to abstract them well away from the world of Z -- but that's probably why the military likes it; "creative" is a bad word, in the military (with good reason, though. Following "The Book" is much less likely to get you and your mates killed).
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Also, I would add that a lot of what is portrayed as "software engineering" practice is, in fact, project management. Agile v Waterfall v whatever is all about how you get teams to work together on software and nothing about how you get software to work.
Many of our industry failings are human failings - but sadly we persist in trying to find technological solutions for them.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
