3 ms·

Really? I graduated this year from a state school with a degree in CS and we covered a lot of this stuff. Software Engineering was a required junior/senior leve

Really? I graduated this year from a state school with a degree in CS and we covered a lot of this stuff. Software Engineering was a required junior/senior level course where we had a semester-long group project where we had to self-organize using Agile methods, and we were grade on our user stories and . I took a senior-level elective course on product management, and we covered cloud and warehouse computing in computer architecture class. We also started using git in our very first programming course, where we had to turn in our code using a central repository. What year did you graduate, out of curiosity?

panopticon 9y ago
Not OP, but I graduated from a state university with a degree in CS just over 6 years ago, and we didn't get much in the way of process education. Couple of slides on development processes in a sophomore class and certainly no source control usage for class work (most instructors accepted assignments as zip archives). In the group project classes I took, the instructors were only concerned with the final results. The process, tools, etc were left to the individual groups to decide.
daotoad 9y ago
I graduated in 1996, we didn't do any of the work related stuff. We learned algorithms, datastructures, programming in imperative, OO, functional and declarative mode, numerical methods, discrete maths, operating systems, computability theory, and all the CS stuff. SDLC is one of those things that every company seems to do a bit differently. Even if you are the GOD of SCRUM THEORY AND PRACTICE, most likely you'll wind up on a team that is kinda vaguely following scrum. Or more likely they've got a fish-ladder process with lots of little waterfalls that they call agile. Good luck effecting change, especially if you're straight outa school. At best Agile methods provide an epistemology for project planning and estimation. At worst, it's a bunch of behaviors to mimic and terms to incant to justify bad or lacking processes.
aecorredor 9y ago
I graduated this year, Summer 2017. For example, my curriculum also required Software Engineering I, which was comprised of a full semester group project. The problem was that it was all waterfall, we spent the whole semester talking about the theory behind waterfall and how to do UML, and talking about architectures that were pretty outdated (we didn't even get to talk about MVC in detail, and don't even think about microservices). We had to do a bunch of documentation with UML about our classes, etc, which all seemed very abstract and like a time waste when comparing it to the actual rails app we had to code. We ended up coding the web app in 4 days with ruby and rails, and didn't even need all the docs to get that MVP. There was a cloud computing elective course which I planned on taking, but it was never offered in any of the semesters that I could have taken it (basically my last year). Wireframing was not even close to being covered in any course. Git I had to learn completely by myself, which isn't a major problem since it's not that bad tbh. Product management, again, not even close to being covered. And, agile, we did cover it in the senior project course, but in reality it was a very vague scrum process, where I'm 100% sure most of the students didn't get the whole purpose of it. Luckily for me I had done an internship in a pretty enterprisy and big company which already had a pretty mature scrum process set up, so I got to learn the benefits from them. I guess what I'm saying is, I feel like most of the stuff I know today about computer science/programming I learned on my own, and not because of my CS degree. I guess that going for a CS degree just helped me in the sense that it actually made me say "hey, this is gonna be you're career, so you better get serious and get into it", which in turn made me start learning a whole lot of more on my own. So, in a sense, I feel that a coding bootcamp can do the same, for a whole lot less money, and in a whole lot less time.

panopticon 9y ago

Not OP, but I graduated from a state university with a degree in CS just over 6 years ago, and we didn't get much in the way of process education. Couple of slides on development processes in a sophomore class and certainly no source control usage for class work (most instructors accepted assignments as zip archives). In the group project classes I took, the instructors were only concerned with the final results. The process, tools, etc were left to the individual groups to decide.

daotoad 9y ago

I graduated in 1996, we didn't do any of the work related stuff. We learned algorithms, datastructures, programming in imperative, OO, functional and declarative mode, numerical methods, discrete maths, operating systems, computability theory, and all the CS stuff. SDLC is one of those things that every company seems to do a bit differently. Even if you are the GOD of SCRUM THEORY AND PRACTICE, most likely you'll wind up on a team that is kinda vaguely following scrum. Or more likely they've got a fish-ladder process with lots of little waterfalls that they call agile. Good luck effecting change, especially if you're straight outa school. At best Agile methods provide an epistemology for project planning and estimation. At worst, it's a bunch of behaviors to mimic and terms to incant to justify bad or lacking processes.

aecorredor 9y ago

I graduated this year, Summer 2017. For example, my curriculum also required Software Engineering I, which was comprised of a full semester group project. The problem was that it was all waterfall, we spent the whole semester talking about the theory behind waterfall and how to do UML, and talking about architectures that were pretty outdated (we didn't even get to talk about MVC in detail, and don't even think about microservices). We had to do a bunch of documentation with UML about our classes, etc, which all seemed very abstract and like a time waste when comparing it to the actual rails app we had to code. We ended up coding the web app in 4 days with ruby and rails, and didn't even need all the docs to get that MVP. There was a cloud computing elective course which I planned on taking, but it was never offered in any of the semesters that I could have taken it (basically my last year). Wireframing was not even close to being covered in any course. Git I had to learn completely by myself, which isn't a major problem since it's not that bad tbh. Product management, again, not even close to being covered. And, agile, we did cover it in the senior project course, but in reality it was a very vague scrum process, where I'm 100% sure most of the students didn't get the whole purpose of it. Luckily for me I had done an internship in a pretty enterprisy and big company which already had a pretty mature scrum process set up, so I got to learn the benefits from them. I guess what I'm saying is, I feel like most of the stuff I know today about computer science/programming I learned on my own, and not because of my CS degree. I guess that going for a CS degree just helped me in the sense that it actually made me say "hey, this is gonna be you're career, so you better get serious and get into it", which in turn made me start learning a whole lot of more on my own. So, in a sense, I feel that a coding bootcamp can do the same, for a whole lot less money, and in a whole lot less time.