Yes, I strongly prefer waterfall. Back in the good old days we had a biz. quarter to deliver a set of features. This allowed time for a spec., thinking about how it would all work, doing a design doc, working with QA on how they'd effectively test the features etc. Weekly status updates were adequate and an appropriate "polling frequency".
All of that is now thrown out the window in the mad hacking frenzy to make progress on the stupid "points" and try and show progress at the dreaded daily standup meeting (even though it's not supposed to be a progress meeting).
Then to make it worse, various team's progress are compared by looking at "points completed" without any kind of normalization of difficulty or risk for the different teams.
Then the final insult is the whole debacle is deemed a "success" because we've "switched to Agile", thereby checking off a box that some CTO with too much time on his hands read about in some MIT technology review.
I would actively refuse any job offering "Agile development" unless they had a very practical & pragmatic way of implementing it. The only one getting any benefits from this crap are the Agile consultants and the PMs.
100% this. I also find it extremely annoying to have to give daily status updates on highly complex, time consuming problem. It shows a complete lack of understanding of the work being done.
The sooner we move om from this Agile garbage the better.
Do you have any more details on the re-programming that would be occurring on non SLC flash cells, even if mounted in read only mode? This is something I was always concerned about too.
Thanks for the response. Do you have any recommendations for tax software, or do you have your accountant handle tax payments? I'm a sole proprietor now but am going to upgrade to an LLC soon.
Thanks @vibrolax, that does look ideal. I was going to muck around and design the circuit myself (hopefully based off a solid reference design), but the COTS setup you listed above looks just like what I need, so I think I'll go ahead and get it once funds allow :) Thanks again for the tip.
Does anyone know what kind of circuit would be able to convert 12VDC (e.g. from a small lead acid gel. cell battery) to 20VDC (which my Lenovo E470's DC charging voltage)? The E470 is my work computer and does not have an easily swappable battery, so I wanted to experiment with some kind of external charging system I can use when working remote at sites without accessible outlets.
I used one of their Cortex M3 parts on a project a while ago that needed a large number of SPI ports to drive strings of LEDs. Was very easy to get the initial POC working, and their IDE software worked surprisingly well.
What a cool and useful sounding project! Does LORA handle any of the meshing aspect, or do you have to manage that at the application level? Also what kind of node to node range are you getting from the radios, and when the users install them, how do they know they'll be within range of the next node?
Musk has painted himself into a corner. He is probably aware that skipping the hard tool test phase was a bad idea, but had no choice, they would've run out of money adding another 6-12 months to the model 3 timeline.
What they're probably seeing now is lots of model 3s coming off the production line with non trivial faults (as to be expected), and stock-piling those because they can't afford to stop the line and fix root causes. Fixing all those stockpiled 3s will take a hell of a lot of time and $$$.
Fair chance Tesla will go into BK in the next 12 months or so if you ask me..
I agree with this comment. OTOH it's very hard to have and enforce discipline in commercial SW development in the US anyway. Managers just want solutions hacked out as quick as possible, so no real time for properly crafting solutions in most cases. Scrum etc. also drives this type of mindset.
All of that is now thrown out the window in the mad hacking frenzy to make progress on the stupid "points" and try and show progress at the dreaded daily standup meeting (even though it's not supposed to be a progress meeting).
Then to make it worse, various team's progress are compared by looking at "points completed" without any kind of normalization of difficulty or risk for the different teams.
Then the final insult is the whole debacle is deemed a "success" because we've "switched to Agile", thereby checking off a box that some CTO with too much time on his hands read about in some MIT technology review.
I would actively refuse any job offering "Agile development" unless they had a very practical & pragmatic way of implementing it. The only one getting any benefits from this crap are the Agile consultants and the PMs.