11 ms·
The challenges of teaching software engineering
- coldcode 7y agoWhat is software engineering anyway? I've heard this term for almost 40 years, and still wonder what it really means since everyone has a different idea.
- wjmao88 7y agoIts called software engineering when it needs to operate under a set of requirements and conditions in scale and complexity comparable to other engineering projects. Everyone has a different idea because everyone has different ideas about what other engineering is about too. Its just that governments/guilds usually publish specific descriptions of what it is and as outsiders we take that as the truth.
- seanmcdirmid 7y agoSoftware engineering a practical art related to the large scale production of software (vs programming as a smaller scale production of programs). Given its practical nature and young age, it isn’t surprising that we don’t really know what it is yet (like how carpentry was practiced a few thousand years ago).
- hashberry 7y agoYou're not alone. Wikipedia has an interesting "Controversy" section about software engineering[0], with a quote from Edsger Dijkstra: ... software engineering should be known as "The Doomed Discipline", doomed because it cannot even approach its goal since its goal is self-contradictory. Software engineering, of course, presents itself as another worthy cause, but that is eyewash: if you carefully read its literature and analyse what its devotees actually do, you will discover that software engineering has accepted as its charter "How to program if you cannot." [0] https://en.wikipedia.org/wiki/Software_engineering#Controversy https://en.wikipedia.org/wiki/Software_engineering#Controver...
- ScottBurson 7y agoAh yes, I love this line: "How to program if you cannot." The fact is, nobody can program, not when programming means building complex systems (pretty much anything bigger than 30kLoC) absolutely correctly. Not I, not you, not the late Prof. Dr. Dijkstra — nobody. We can't. But we need to build these systems nonetheless. So, "how to program if you cannot" becomes an essential area of study.
- skybrian 7y agoDijkstra is a good source of controversial quotes, but they tend to be hyperbolic and I wouldn't take them as the last word on anything.
- hermitdev 7y agoMy favorite is "goto Considered Harmful". Yes, it can be abused, but can so nearly every other programming construct. There are places where goto makes sense, such as error handling or breaking out of nested loops. I hate seeing a Boolean flag(s) being tracked for whether or not break out of nested loops. It's more typing and confuses the intent. Just goto the label following the nested loop. Also, nearly any looping construct can be implented using a conditional goto, and if you go down to assembly, they almost universally are. Jumps are goto's by another name. I've seen exceptions used for control flow. Awful. It's about knowing the appropriate construct for the problem at hand. I've seen do{...}while(false) used with conditional breaks to avoid use of goto in error handling and it's confusing as you're reading through an unfamiliar codebase to see abuse like that. As I'm reading through the code, I see the 'do' and I expect the code to loop, only to continue reading and find out it doesn't loop. Frustrating.
- goto11 7y agoDijkstra was arguing in favor of structured programming languages powerful enough that you didn't need GOTO. For example you mostly see GOTO for error handling in C, because C lacks a structured way for resource cleanup. Dijkstra certainly wasn't arguing you should use trick like do{...}while(false) to avoid using the GOTO keyword.
- carapace 7y agoDr. Margaret Hamilton coined the term while developing the software for Apollo 11. She went on to design a system that permitted bug-free software development ("Higher Order Software" or HOS) and attempted to market it. It was panned by e.g. the Navy and Dijkstra, and languishes in obscurity to this day. The basic details of the system are described in a book called "System design from provably correct constructs: the beginnings of true software engineering" by James Martin (he mentions Hamilton in the references.) In modern terms you work directly with an AST and the UI only permits modifications by operations that preserve the correctness of the AST. It eliminates all sources of bugs, and it was simple enough to teach normal people to use it with just some coaching. Anyhow, that's "software engineering". The rest of us are just pushing text around in buffers and hoping it isn't broken. There are a few people using math to make software, and it works out really well (E.g. https://www.categoricaldata.net/ https://www.categoricaldata.net/), but mostly "software engineering" as it is usually used is an oxymoron.
- skybrian 7y agoThe claim that a "correct AST" would eliminate all sources of bugs is unreasonably bold, and I wonder if they really made that claim, or you misunderstood something? That just means the code compiles. Some languages are stricter than others, but none claim to eliminate all bugs. Static analysis and safe refactoring tools are great, but they are certainly not going to protect you from implementing the wrong thing because you misunderstood the requirements or the environment; that's not possible even in principle. At best you can check for consistency (for example, consistency between a specification and its implementation).
- Jwarder 7y ago> you work directly with an AST and the UI only permits modifications by operations that preserve the correctness of the AST. It eliminates all sources of bugs With the caveat up front that I know nothing about this beyond what you have written: wouldn't this just catch compilation bugs? The compiler tells me if the blob of text I gave it is incorrect in terms of any syntax errors. Business logic bugs and accounting for bogus data seem more important to me.
- ScottBurson 7y agoMy definition is that software engineering is about the management of complexity. Complexity in software proliferates faster than in any other discipline precisely because it is so easy to create and change. The difficulty is not in writing or editing a line of code, but in understanding how that line of code interacts with all the other code in the program. The essence of software engineering is building large systems in such a way that they are as easy to understand as possible.
- paulddraper 7y agoIt's the software equivalent to electrical engineering, civil engineering, etc. Designing/creating software.
- bigger_cheese 7y agoWhen I was studying engineering in the early 2000's my degree was structured such that in the first year all the engineering students (regardless of whether they intended on majoring in Chemical, Civil, Mechanical, Electrical etc) all took a common set of courses. This included classes such as: Calculus, Linear Algebra, Physics, Chemistry etc. There were two required CS courses (one in the first semester of first year and one in the second) The first semester course was "Intro to programming and algorithms" which began by assuming no one had any prior programming experience and started with the very basics "This is a variable", "This is a function" "This is a conditional statement", "This is a loop" that sort of thing. Eventually it covered algorithms like quicksort, bubblesort etc and really helped get you into the mindset of "This is how you use programming to solve a problem" For example I remember writing code to solve simultaneous equations (i.e Linear Programming), finding line of best fit through a series of discrete points things like that. In the second semester the required class was "Intro to software engineering" I remember the course covering things like Object oriented programming - classes/inheritance public/private members and all that stuff, this was a component on unit testing. There was also an essay component to the course I can remember having to write an essay about the Ariane 5 explosion. I really didn't enjoy this course and the impression I got was not a lot of my friends did either. I can understand the intent of making us sit through the course but in some ways I think it did more harm then good pretty much everyone came out of that class at the end loathing "object oriented" programming. At the time it was kind of a struggle to see the relevance behind the topics covered and even now with 15 years of engineering experience working in manufacturing what we learnt in that classroom is very divorced from what goes on in the real world. When I write code I am, typically speaking, not writing complex software that has multiple reusable components that talk to each other most of the code I write is trying to solve some type of problem. When I write code I'm usually thinking in terms of mathematics and problem solving rather than classes + objects and unit tests, my code tends to be a lot more in the style that was taught in the algorithms course rather than in the software engineering course I suspect quite a lot of "research code" would be similar.
- agumonkey 7y agoI learned what an engineer was when dabbling in electromechanics. I think after the 80s, engineering lost its meaning in computers because people could abstract the machine away and hodge-podge a lot of systems. No need to carefully encode data, precompile addresses, state etc which would be similar to the dimensioning computations in physical systems. ps: to extend the story, most engineered things have very carefully defined dimensions and limits which drives most things in the design. Max Wattage in your PSU will reflect in the gauge of wires, size of capacitors etc. A bit like choosing an arch when compiling. I remember some threads in 2000s boards where some guys did talk about jobs like these in computing. They had said space and said cycles to work with, with that they could see what algorithm could compute the needs back against the limits. I found it especially interesting brain wise because you could "think" in hard figures, instead of glueing things without any idea what was really going on.
- skybrian 7y agoThis went out the window in favor of portable software, multitasking, and reusable components. As soon as you have software that can run on a variety of machines (including new hardware that hasn't been invented yet), there is no way to give a performance guarantee. (An exception might be something like a game console where hardware is fixed.) Even if hardware is fixed, if you don't control the other programs running on the machine, you don't know how many cycles you'll get. And whenever you allow a newer, "compatible" version of a library or OS component to be swapped in, all bets are off. No mainstream languages take performance into account when deciding whether a newer version of a library is "compatible". So, any security update could invalidate your measurements. (And in a way, the same is true of hardware since you don't control the environment it runs in or what might be plugged into it.) We can ignore all this stuff and it mostly works. We wouldn't have an Internet without it. (Imagine if web browsers had to give performance guarantees.) Instead we'd have some kind of fixed-hardware monoculture.
- madhadron 7y agoMy definition is a bit different from what I generally hear, and is based on discussions with my father, who is a structural engineer. Engineering is about making a process legally defensible. A structural engineer can stand up in court and say, "As designed, this should have stood up to all expected loads in this location," and have it be taken as expert opinion. In the US, where engineer isn't as controlled a term as elsewhere, we use the term engineer for all kinds of roles. In, say, Canada, engineer means a professional engineer in one of the legally protected categories. You can't use engineer as a job title outside of those. So if you're trying to talk about software engineering, imagine something horrible has happened with a system you were involved in designing (say, Therac-25). What what you need to know and do to be able to say that this failure should legally qualify as an "act of god"?
- keithnz 7y agoIt gets used broadly for any kind of software creation, but I think of it as software that is created in an engineering context ( like software for machines ) where you apply engineering concepts via software. So software engineers would be able to, in software, apply principles of things like control theory to a problem.
- ilaksh 7y agoSoftware engineering is what programmers do. The idea that programming is a different or less-skilled occupation is false. The engineering part is any skill and knowledge you use that goes beyond the basic language syntax. Things that everyone who programs for a living has to have, such as the ability to determine requirements and organize code in a maintainable way. The controversy is due to human biases and stupidities.
- theshrike79 7y agoSoftware engineering is what happens to programming when you add time and other programmers. –Russ Cox, GopherCon Singapore 2018
- DarkContinent 7y agoI'm sort of curious how one could "learn" software engineering in a week. Judging from the article, it seems the course assumed very little prior knowledge about SWE (teaching OOP at the beginning). Wouldn't it make more sense to teach a course assuming some basic background knowledge (like OOP and command line utilities) and use the teaching time to discuss architectural patterns, testing practices, etc?
- asauce 7y agoThis is exactly what I was thinking. Software Engineering is a lot more than just writing code, however this blog post makes me think that he is teaching Software Engineering to a completely new audience. It is very easy to overwhelm software students when trying to teach a broad array of topics (especially in a week!). He mentioned that his students ran into challenges such as not understanding the difference between 'python foo.py' and 'python3 foo.py'. How can you expect these students to overcome these beginner challenges and then still learn topics such as git, CI, machine learning (!!), functional programming, concurrency, processes, etc! These topics can take years to learn properly, and require a good foundation. Maybe I didn't understand the purpose of this course, but it seems pretty insane
- ticmasta 7y agoIt's a smell that a course that dedicates an hour to object-oriented programming even mentions UML. Wouldn't your audience be far better served if you offered dozens of focused sprint classes (1 topic; 1 hour) rather than some sort of eclectic marathon?
- kemiller2002 7y agoI agree. It's a nice attempt, but I don't see how this is practical. It falls into the same trap people looking in from outside the software development have been falling into for years. They assume that it's easy because they can do an excel macro and such. Software development is actually really hard. Complex systems are hard. A parallel to this would be something like, "You built a bird house out of wood. We'll teach you how to build a skyscraper in a week." It's just not possible.
- fogetti 7y agoIf it's an introduction to software engineering then I think leaving out software craftsmanship or functional programming, etc is not necessarily a sin. And git (the cli not the versioning approach per se) never made sense to begin with. It is extremely user hostile. So no surprises there.
- spraak 7y agoI have heard often people's view that git is not user friendly, but it's always confused me because that hasn't been my experience compared to any other tool I need to learn. Can anyone explain more this view? Perhaps I'm too accepting and forgiving.
- duxup 7y agoAs someone who feels they understand git enough to use it... I think it is unfriendly. The terminology is just a beast. I feel like every term / command is a bit of a hieroglyph that means nothing on the surface and then I have to associate with some other thing (possibly more hieroglyphs) and memorize. Few git... isms really tell me / give me a clue what it does. It feels like programming in a foreign language (god bless you folks who do that!) where I just don't have anything to hang on to, just memorize it all.
- Stratoscope 7y agoTry SmartGit. It gives you all the power of the command line and then some. A lot of the 5-10 line git recipes you see online are just a single operation in SmartGit. The reflog is one example. Instead of copying and pasting hashes and checking out each one to see if it had the changes you want, just click the Recyclable Commits box and every commit from the reflog shows up in the normal commit and branch display. Just click one to see its changes, or click two commits to see what is different between them.
- keithnz 7y agoSmartGit is great. It makes Git completely usable to a novice and still useful to powerusers, it also makes it very easy to visualize the state of your repositories. For the most it hides things like staging, however you still need to understand the git "mental model". I think the biggest problem for people new to git is that it solves problems they don't really have yet. They are solo on their own repo.... they don't see the point of branches, they only really ever need to stage/commit/push all their changes to a remote. So they learn the magic command line incantations until the day it goes wrong somehow, or they need to roll back, or need to start collaborating and they have to dig a bit deeper
- dzink 7y agoYou seem to be starting too abstract. Analogs help and so does starting from a point where the students can experiment and get feedback on their mistakes from their own code, not from abstract concepts. These are lessons I learned when we designed and taught a 8 week coding course for Graduate students who had never touched code before. Feedback for us as teachers was instant. (Analogs. Analogs. Analogs.) Imagine learning about structural engineering - would you rather start by prototyping bridges with different materials and seeing how different structural designs hold up better, or would you prefer to be lectured about conflicting philosophies on proper road arrangement, materials and tensile strength first. Analog example I used (explain like they're five): Front end, backend, middleware, databases are like a Macy's animated window display. HTML is choice and order of the mannequins in the window. CSS are the colors and positioning. Javascript is the string that makes visible characters move. Middleware (Python, Go, Java) are the sales clerks grabbing goods from the warehouse (database), serving customers, and updating the window panes. The course did a lecture on HTML/CSS first day, Javascript second, dug in deeper by debugging a snakes game in JS, Git on day 3 (failed for same reasons you mentioned), Ruby on Rails (immediate productivity was key), Wordpress installation, then PHP deeper dive, etc. One student said "I can't believe I paid someone $20k to build me a Wordpress site that I can now set up and customize myself after a few days." Always start with immediate productivity for non CS students - let them sink teeth into the ideal outcome, then modify that ideal, then learn how to break and fix it, then dig deeper into why and how things work before going to best practices. If they don't know why something broke, they can always go back to figure out how it should work first.
- dzink 7y agoIf I was to do it again, I would teach Git with paper - have the class augment a paper tree with paper nodes or something else tangible. You can even have them write a collective story instead of code. The more abstract the topic, the simpler the analogs to get the largest subset of users to grasp it.
- haggy 7y agoI have to strongly disagree with this approach to teaching git. I've been in software engineering for a decade now and have taught many entry level and experienced devs about git. If you start out with trees and other git internal concepts you're just going to lose them. Have them create a directory, put some files in it, `git init`, add all their files and commit. Have them make some changes, add and commit again. Then ask them how their fellow devs would see their changes. This leads into the distributed nature of git and pushing to remote repos. Continue from there with more practical work and repeat. I've seen it take devs months of working with git daily to start to understand some of the more advanced concepts so it needs to be practical up front.
- codingslave 7y agoThe secret of programming, and it's greatest challenge, is that the ability to get "good" at it is largely innate. Just like you can't teach people to prove math theorems (the ones that one encounters in an elementary college proof class), you can't teach great software engineering. Near anyone can learn to build a javascript app, beyond that, to higher levels of abstraction and complexity, things become murky. It's why large tech companies ignore past experience, it proves nothing. They need to see you use abstractions from memory on the spot to ensure you have the capability. It's not perfect, but nothing is.
- deleted 7y ago[deleted]
- jedberg 7y ago> git, in particular, is decidedly unfriendly. What I want to do is commit my changes. What I have to do is stage my changes, then commit my staged changes. As a result, teaching git use takes a significant chunk of the available time, and still leaves confusion. In college, the way my professors got around this and other things like it was by creating an alias file and scaffolding code. We would get a project that was 1/2 done with all they annoying crap, and then only have to implement the algorithms. Then we would save our work with a single simple command with no options, that was just a shell script for all the source control steps (rcs at the time, but the idea is the same). They never actually taught us about source control. We just learned it on our own when we stopped having access to their aliases. But at that point we had enough knowledge that we could figure out it (or we were in our first job and the senior devs taught it to us).
- invalidOrTaken 7y agoI don't know exactly what the goal of the course is, or where he's teaching, but... it seems like a really hard problem. Making working computer systems---like a drawing program, or an Amazon deploy---can be really hard, or really simple. You can teach someone enough Python for fizzbuzz in twenty minutes. Teaching them enough...everything...to get a web version of fizzbuzz, that checks a database for the words (it might be "nargle" and "gargle" by user preference, after all), with a Python install that they manage, a postgres install that they manage, that they don't feel at a complete loss about if something goes wrong, and to collaborate with others on this...is another matter entirely. I'm not one of those who believes programming ability is innate, but there are absolutely compounding effects that can certainly have basically the same effect. In retrospect, I thank my lucky stars for my 6th-grade computers class using HyperCard.
- gambler 7y agoSounds more like "the challenge of using a mish-mash of non-integrated tools with no interface". Developers could definitively solve this by moving away from 70+ year old abstractions (files, terminal) towards things more in line with Smalltalk ideas. But I guess it's better to make thousands of beginners suffer each year, instead of admitting that the current way of doing things is conceptually flawed and outdated. https://www.youtube.com/watch?v=I9LZ6TnSP40 https://www.youtube.com/watch?v=I9LZ6TnSP40 https://alumni.media.mit.edu/~mt/thesis/mt-thesis-Contents.html https://alumni.media.mit.edu/~mt/thesis/mt-thesis-Contents.h... https://www.youtube.com/watch?v=QTJRwKOFddc https://www.youtube.com/watch?v=QTJRwKOFddc https://github.com/pharo-open-documentation/awesome-pharo-ml https://github.com/pharo-open-documentation/awesome-pharo-ml (And no, there is nothing special about copy-pasting commands and Unix pipelines that cannot be easily recreated in UI if the UI is designed to be programmable. )
- hyperpallium 7y agoIt's very difficult to teach software engineering because you need a big project to create and/or modify. Another reason it's difficult to teach is because of a complete lack of a legitimate discipline to teach.
- BeetleB 7y agoMost of the problems he is having seem orthogonal to software engineering, which he is trying to teach. It's clear he's teaching it as an intro course. In my opinion, SW engineering absolutely should be taught as a later course - after the student has had quite a bit of exposure to programming. I wouldn't expect a SW engineering course to require teaching much command line usage. That's a thing for lower level courses. Same with editors. Don't use git if it is confusing to students. Mercurial is as good and much friendlier. The potential benefits to git are fairly advanced and will not have any impact at an introductory level. Your goal is to teach the concept of revision control, not the internals of git (which every git advocate says one should know if one wants to use git well - just search any HN thread that comes up about git). As for Python vs Python3: Again, I would not expect a SW engineering course to teach any language. The course should let the student pick a language of his/her choice.
- colemorrison 7y agoHaving taught software, devops, and the like for years at this point, while this article touches on some difficult parts of teaching, they're all just side effects of bigger difficulties of teaching software. a) Everything is the "tip of the iceberg" - which makes teaching what you actually want to teach tricky. Which is why so many resources do the whole "we won't go into it, because this is a large topic." For example, Linux. Most projects and resources require this, but barely any actually go in-depth. b) Everything is always changing - and so you have to either support your students in the face of these changes or constantly keep the materials up-to-date. This is one of the largest challenges, if not the largest challenge. c) Everything has to be engaging - it's not enough to know what you're talking about. You have to know how to talk about it in a way that creates engagement and thus learning. This isn't something you learn how to do when slinging code left and right. d) Everything needs to be TAUGHT, not said - the ability to teach is often an after thought for folks looking to educate. If you want to really help your students, you have to learn how to teach so that they can think independently. Not rely on cheatsheets, prep tests, and step-by-steps. e) Every student needs the motivation to learn - usually instructors' will stop at spitting out their knowledge. The best instructors help their students push through their barriers, whether personal or professional, and get the learning done. It's easy to learn in a structured school system. It's hard to learn when you have multiple kids, a full time job, and all the emotional baggage of being an adult. Now, to be clear, I'm talking about teaching modern, practical implementations of software...not CS theory or other things that are far more evergreen and less technical.
- dijit 7y agoSoftware engineering at least has a fundamental underlying educational system supporting it (comp sci, EE). I think the harder thing is training sysadmins, there’s no real formal education. I know we’re downplaying a lot of the traditional sysadmin roles and pushing for more development in sysadmin but the sysadmin approach is still required, and the only thing that keeps it going is the corpus of industry knowledge, a myriad of vocational or vendor based certs and a willingness to teach. Or am I wrong?
- dnprock 7y agoI think there's a hype in quickly training software engineers. This article is an example. We poke around with tools to find quick and easy ways to create software. Tools have been improving quickly but creating software remains challenging. The tool race is influenced by market more than software engineering. The discipline of software engineering has not changed much for decades. To teach effective software engineering, we need to start with the principles. Some fundamental questions: - How do we create functional and scalable software? - Given an existing (complex) software system, how do we maintain and incrementally improve? One important principle I learned outside of school and training: software is never just code, we always need to think about the user ecosystem around the software. Failure to understand this principle leads to wasteful effort. For example, attempt to rewrite of the code. These principles are very abstract. We cannot teach them easily. People use tools and new technology to cover up their lack of understanding.
- bsder 7y ago> git, in particular, is decidedly unfriendly. Why do people persist in pushing one of the most user unfriendly tools to ever exist?
- jkingsbery 7y agoI taught a 2-hour session to a group of middle schoolers and high schoolers back in December - obviously, not as big a deal as the author, but still something I'm proud of - and ran in to the same issues. These were all students who either had done some programming or were interested in it. I started with "ok, so, first, go to your command line..." and it went sideways from there. One thing that the students taught me that helps overcome some of these things is a site called https://repl.it/ https://repl.it/ . I stopped my plan, started using it, and taught the rest of the class using repl instead in order to focus on the concept I was trying to teach. Obviously, as a professional software engineer you need to know about git, command line, etc., but those aren't what software engineering is. They rarely excite new comers to the field. Using repl.it helped to get to the core ideas faster for people who don't really know as much.
- rpeden 7y agoIf you enjoy repl.it, you might enjoy StackBlitz as well. I've had fun using StackBlitz to put together some prototypes of React apps. I love repl.it too, of course! It's nice to have several great tools to choose from.
- jkingsbery 7y agoInteresting, thanks for the reference!
- flukus 7y agoI think there's a half way between both because the command line is a REPL, even the awful windows one. I think that's a better starting point than a web based IDE (I don't think repl.it is actual a REPL) because you can naturally expand to more tools, have access to your own files, etc. If you start out that way then setting things like core.editor become natural extensions of what they've already learned and not some magic incantation to get started.
- jkingsbery 7y agoYeah... I tried that. It was confusing because different people had different operating systems (and therefore different command lines), and since they weren't familiar with the command line at all I would have spent the time talking about something completely unrelated to the thing I wanted to teach about. I see where you're coming from with your suggestion, but I think in practice it contributes to information overload and intimidation to a large part of the population.
- ilaksh 7y agoThis is the course he is talking about: https://github.com/OxfordRSE/rsd-engineeringcourse https://github.com/OxfordRSE/rsd-engineeringcourse So to become a "real software engineer" and not "just a programmer" one needs to know how to create requirements, use source control, do modular, and/or object-oriented and/or functional design, deploy your software, and take advantage of open source? Those are things that all programmers need to know (assuming "programmer" means someone whose primary job is programming). Which is why the distinction between "programmer" or "developer" and "software engineer" is bogus. Its usually just an attempt to justify higher or lower compensation.
- steven2012 7y agoNo offense to the OP but the syllabus is ludicrous. This isn't teaching anything. It's so packed with random software technologies, they will leave the course with nothing. Cut down on the syllabus and focus on a few topics. Make it project based so that you're building on the same project over the 4 days and learning more about programming. Split the other stuff like git, databases, OOP, functional programming, machine learning my God, for another course. There is no way anyone taking this course will get anything from this, it will just be a confusing mess of information that is quickly forgotten.
- alexgmcm 7y agoI read it assuming it was a semester long. Then I saw it was four days.
- cryptonector 7y ago> - you need to either tell people how to set their core.editor, or how to quit vim. You'll pry vim from my cold dead fingers.
- jpnelson 7y agoI'd love it if there was some sort of "helper terminal" that could teach people things like git, and basic command line stuff as they went. It could catch common errors and provide useful explanations. It could possibly even go as far as attempting to understand plain text commands, eg "delete the file file.txt" and suggest commands to do that.
- eitland 7y agoClippy, as orginally designed before they gimped it? ;-) Or just contextual help as it existed in many Windows applications (and certain current iOS apps).
- kouzant 7y agoI hope they don't add Jupyter notebooks to the syllabus. One day we'll wonder what went bad and whole programs are written in a single module/file :) Jokes aside, Jupyter and relevant projects are great tools but they drive programmers towards wrong paths.
- angarg12 7y agoI was a teaching assistant for the Introduction to Programming course on the first year of a CS degree. At the very least I can say it was a humbling experience. One thing I learned while teaching complete novices is that it is really hard for experienced engineers to get into the mindset of students. You need to forget everything you know and start more basic that you think it's necessary. You will need to teach people what are variables, list, functions, and so on. As an example an student got confused when we wrote something like the following: let X = 1; let X = X + 1; How could X be X + 1 at the same time? Maths don't work that way!. It might seem absurd to a programmer, but if you are in the mindset of someone who is only familiar with maths equations, it makes sense. So yeah, I would forget git, command line, tangents and whatnot, and focus on very basic concepts instead.
- jillesvangurp 7y agoWhen I was doing my Ph. D., I also ended up teaching some software engineering related courses. One thing that struck me and that I've since fixed by becoming a software engineer was the notion that here I was teaching Software Engineering without any experience whatsoever actually engineering any software professionally. This is the big problem in academic education on this topic: the teachers typically have little or no relevant experience actually engineering software because they have been in university all their life and as such lack experience working for extended periods of time with an actual team on some actual non trivial software. Lets just say that I learned a lot about this stuff after I left the academic world. A good practical introduction to software engineering should cover a lot of ground and most of it is going to be non technical. Learning how to program is mostly out of scope for a software engineering introduction. Assume the students have already learned some programming language and have some experience building small programs and maybe have already had some algorithm courses, etc. It doesn't really matter what language or tools they use. For the purpose of an introduction, pick something simple where the focus is mostly not going to be fighting with the tools. The key thing to learn as a software engineer is working with multiple people and the project dynamics that are associated with that. So: - project management and different roles in software projects, different ways of structuring teams, etc. - overview of different process methodologies common in the industry and where they came from: scrum, kanban, watefall (don't do this), etc. - different types of testing and their importance for continuous integration and deployment - different strategies for estimating cost, complexity, duration, etc. and their flaws and pitfalls.