if you're not using a methodology like Agile Scrum, or some such that can manage spec's and produce on going working prototypes that allows everyone to get a sense that something is taking shape, then you'll end up doing something like waterfall. And then that's the end of that.
Season programmers have been through all the scope creep scenarios w/o being able to get anything up to prototype state of execution.
At least things like Scrum allow you to have 10-20min standup where you get your status reports and developers don't have to remember to email them to you and the end of day/week.
Agile is actually rather good at getting individuals motivated and satisfied. Scrum is what is used here at where I'm working.
As a seasoned vet myself, all I want is to see code+unit_tests(passing)+releases that show me that we're being productive as a team.
My stats may be a bit rusty, but jesus! A sample size of 29 undergraduate students? Come on. And we draw conclusions from this?
A sample of size of 29K with 50K mens faces, then maybe I'd look twice.
Saw it at a media preview. I was disapointed, and at the end everyone just got up and left. No clapping, cheers, what-not. Just got up and left. Several times on the way out I heard the term "cheese" used.
Each scene looked great, but they didn't tie together as a story, no real character development. So, would make a great screen saver.
Also, I don't think Lucas achieved a good balance of humour and tension. Reminded me of the ROTJedi, where the ewoks kept making silly sounds. Distracted from the weight of what was going on. At least with the original ESBack, the absence of these childish sounds made the whole film build in tension. And, er, Lucas didn't direct it (thank god!).
Thing is, if you've chosen to study computer science to develop complex algorithm to solve a real-world problem, are you/have you also studied the art of developing software so that your implementation isn't hindered by common development faults.
This means that you'll gain (or have) a deep understanding of the software development lifecycle and all the possible failure points in that lifecycle. You've also developed a tight personal software development process the likes of which SEI has championed over the years via the CMM, or some other framework such as the Microsoft framework for development which the MS consultant division use (hold on, it's actually very good! Just wish Microsoft developers themselves would embrace it:-o ).
The average developer hasn't even considered the fact that developing (near) bug-free software on time,on schedule, and within budget is possible, so they either don't bother trying to find a better way to peel the potato or are in a corporate environment where deploying poor quality software and using the customer as a "free" QA dept. is the norm.
The ability to develop tight code is paramount these days. Locking down complex algorithms which your research has yielded will allow your future employer to realise that your education and academic research has huge real-world value.
An fully developed software engineer has a much better chance of securing employment in the current climate here and around the world.
Formulate a clear intent and then jump of the cliff.
Having worked at MS (in testing) and have friends that still do, I can assure you that at no time has testing been as precise as mortis.
Damn lucky if they even test their products competently. Several products are shipped w/o testing at all. I remember overhearing a tester say "well we shipped it last time w/o testing it!".
MS is an 80's relic, developing code like an 80's relic. They're only now learning that testing actually save's you money!
Slashdot Mirror
if you're not using a methodology like Agile Scrum, or some such that can manage spec's and produce on going working prototypes that allows everyone to get a sense that something is taking shape, then you'll end up doing something like waterfall. And then that's the end of that. Season programmers have been through all the scope creep scenarios w/o being able to get anything up to prototype state of execution. At least things like Scrum allow you to have 10-20min standup where you get your status reports and developers don't have to remember to email them to you and the end of day/week. Agile is actually rather good at getting individuals motivated and satisfied. Scrum is what is used here at where I'm working. As a seasoned vet myself, all I want is to see code+unit_tests(passing)+releases that show me that we're being productive as a team.
Two words Cowboy Coding (look it up) That's how they did it when I was there, from what I've heard ain't nuttin' changed baby!
Guitar Rig has a wah and it's usb too. Uhm, so yeah we have it already!
My stats may be a bit rusty, but jesus! A sample size of 29 undergraduate students? Come on. And we draw conclusions from this? A sample of size of 29K with 50K mens faces, then maybe I'd look twice.
Saw it at a media preview. I was disapointed, and at the end everyone just got up and left. No clapping, cheers, what-not. Just got up and left. Several times on the way out I heard the term "cheese" used.
Each scene looked great, but they didn't tie together as a story, no real character development. So, would make a great screen saver.
Also, I don't think Lucas achieved a good balance of humour and tension. Reminded me of the ROTJedi, where the ewoks kept making silly sounds. Distracted from the weight of what was going on. At least with the original ESBack, the absence of these childish sounds made the whole film build in tension. And, er, Lucas didn't direct it (thank god!).
my $0.02Thing is, if you've chosen to study computer science to develop complex algorithm to solve a real-world problem, are you/have you also studied the art of developing software so that your implementation isn't hindered by common development faults. This means that you'll gain (or have) a deep understanding of the software development lifecycle and all the possible failure points in that lifecycle. You've also developed a tight personal software development process the likes of which SEI has championed over the years via the CMM, or some other framework such as the Microsoft framework for development which the MS consultant division use (hold on, it's actually very good! Just wish Microsoft developers themselves would embrace it :-o ).
The average developer hasn't even considered the fact that developing (near) bug-free software on time,on schedule, and within budget is possible, so they either don't bother trying to find a better way to peel the potato or are in a corporate environment where deploying poor quality software and using the customer as a "free" QA dept. is the norm.
The ability to develop tight code is paramount these days. Locking down complex algorithms which your research has yielded will allow your future employer to realise that your education and academic research has huge real-world value.
An fully developed software engineer has a much better chance of securing employment in the current climate here and around the world.
Formulate a clear intent and then jump of the cliff.
Having worked at MS (in testing) and have friends that still do, I can assure you that at no time has testing been as precise as mortis. Damn lucky if they even test their products competently. Several products are shipped w/o testing at all. I remember overhearing a tester say "well we shipped it last time w/o testing it!". MS is an 80's relic, developing code like an 80's relic. They're only now learning that testing actually save's you money!