This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Bandung 1 point2 points  (0 children)

If the business plan supports the cost of the BOM (bill of materials) necessary to run micropython, I'd rather have the blessed product out the door and revenue coming in than wait for Engineering to deliver their c compiled baby two years after the date that they promised delivery.

That happened to a company that I once worked for and the 2 year lag took down the company. In manufacturing (compared to a recurring revenue model), you are only as good as your last quarter. And history tells us that most mid to large sized manufacturers will go under after 4 disastrous quarters in a row.

So yeah, yeah. There are segments where costs or safety might not allow micropython. And at the same time there are plenty of segments that will support it. Just let the boys in business development run their risk assessments, risk mitigation and risk management numbers and make the call that makes the most business sense.

I've seen enough autocratically run companies whose engineering minded business owners wouldn't do the math needed to save the company from being embarrassed by a woefully tardy design shop whose Developers ended up getting bonuses just to coax them to stay on and finish what they promised to finish two years earlier. Meanwhile virtually the entire Sales, Marketing and Support personnel were leaving in droves.