4 ms·
I'm in robotics and I agree with this. ME people are 100 times more thorough in checking things are done correctly than EE or SWE. Its very hard to make changes
by accurrent 6y ago
I'm in robotics and I agree with this. ME people are 100 times more thorough in checking things are done correctly than EE or SWE. Its very hard to make changes in ME. Also people heavily underappreciated the difficulty of the field.
From a SWE perspective, Robotics Engineers need to know physics and math than the average SWE learns.
Interestingly almost all the successful robot projects I've worked on seem to follow a waterfall process. You keep working on it till it works. After its ready don;t change anything.
- ptx 6y ago> waterfall process ... keep working on it till it works I thought waterfall was to plan it out in detail, then do all the work according to the plan despite realizing that the plan is wrong, then finally, after disbanding the development team, test it to see if it works? That's obviously a caricature, but if you have the feedback loop to see if it works while you're working on it, you might also call it agile.
- jki275 6y agoYou’ve described waterfall accurately, but waterfall is kind of an anti-pattern. Nobody actually uses it.
- lmilcin 6y agoYou mean there are no places where managers tell their teams the scope and deadlines and then tell the team to go play "agile"?
- jki275 6y agoThat's not waterfall.
- lmilcin 6y agoFrom that point of view I would say no project is waterfall. In any sufficiently complicated project requirements MUST change over development if only for the fact it is not feasible to specify absolutely everything absolutely precisely before development starts.
- jki275 6y agoI agree. Waterfall is primarily a discussion point on why Agile is the way to go -- hence an anti pattern. Nobody actually does waterfall.