Gettin' the Ball Rollin: Difference between revisions
No edit summary |
No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 18: | Line 18: | ||
I told Mike this already, but running personality update test suites on our assembly drones is not only pointless, but dangerous.<br> | I told Mike this already, but running personality update test suites on our assembly drones is not only pointless, but dangerous.<br> | ||
One badly configured integration test and we could shut down | One badly configured integration test and we could shut down '''at least''' one of the lines.<br> | ||
Repair and reset could take days, and the total loss one of our lines being down will frankly | Repair and reset could take days, and the total loss one of our lines being down will frankly '''dwarf''' anything that might come from underutilized compute. | ||
Also, reiterating the contents of my last email on assembly drone hardware: <br> | Also, reiterating the contents of my last email on assembly drone hardware: <br> | ||
| Line 25: | Line 25: | ||
We can't guarantee they'll even be able to run any of our latest updates.<br> | We can't guarantee they'll even be able to run any of our latest updates.<br> | ||
My official recommendation is an emphatic no. | My official recommendation is an emphatic '''no'''. | ||
</div> | </div> | ||
| Line 62: | Line 62: | ||
It sounds like upper leadership on this project needs to be informed of the limitations involved. | It sounds like upper leadership on this project needs to be informed of the limitations involved. | ||
</div> | </div> | ||
<div style="font-family: Times New Roman; font-size: 110%; background: #190b33; border: 1px solid #434145; padding: 1ex 1em;"> | <div style="font-family: Times New Roman; font-size: 110%; background: #190b33; border: 1px solid #434145; padding: 1ex 1em;"> | ||
| Line 73: | Line 75: | ||
Dan here. Leadership has made the decision to move forward with the initiative. <br> | Dan here. Leadership has made the decision to move forward with the initiative. <br> | ||
Additionally, in order to maximize Mike's support on making sure we ship this into production ASAP, <br> | Additionally, in order to maximize Mike's support on making sure we ship this into production ASAP, <br> | ||
we'll be assigning Emil as Technical Project Manager. He'll be working with you to manage the day to day | we'll be assigning Emil as Technical Project Manager. He'll be working with you to manage the day to day. | ||
Upper leadership is looking forward to a working proof of concept by the end of the quarter. <br> | Upper leadership is looking forward to a working proof of concept by the end of the quarter. <br> | ||
| Line 99: | Line 101: | ||
SUBJECT: RE:RE: QA Initiative Kickoff<br> | SUBJECT: RE:RE: QA Initiative Kickoff<br> | ||
FROM: dan.gorman09@charmtech.com<br> | FROM: dan.gorman09@charmtech.com<br> | ||
I'll get you three. | I'll get you three. | ||
</div> | </div> | ||
Latest revision as of 19:03, 10 October 2024
SUBJECT: On Prem Cloud QA Initiative
FROM: meghan.teller04@charmtech.com
TO: lauren.amira@charmtech.com
CC: mike.roberts02@charmtech.com
Hey Lauren,
I know you're busy, but I asked Mike and he said you've been DND on Slack for a few days now.
Could we connect regarding the latest QA initiative? Just wanted to get any thoughts you might have.
Please get back to me by EOD?
SUBJECT: RE: On Prem Cloud QA Initiative
FROM: lauren.amira@charmtech.com
I told Mike this already, but running personality update test suites on our assembly drones is not only pointless, but dangerous.
One badly configured integration test and we could shut down at least one of the lines.
Repair and reset could take days, and the total loss one of our lines being down will frankly dwarf anything that might come from underutilized compute.
Also, reiterating the contents of my last email on assembly drone hardware:
they are all decommissioned not-for-sale product IDs that we've taken off the market.
We can't guarantee they'll even be able to run any of our latest updates.
My official recommendation is an emphatic no.
SUBJECT: RE:RE: On Prem Cloud QA Initiative
FROM: mike.roberts02@charmtech.com
Hi Lauren,
Our CEO and CTO agree that we are massively underutilizing compute resources.
Especially given our cloud costs. Just to remind you,
our efficiency initiative has identified that if we can offload our compute onto our existing units we might be able to save upwards of $85,000/day.
We basically have an army of small computers building even more computers. Why can't we get this done this quarter, let alone this year?
SUBJECT: RE:RE:RE: On Prem Cloud QA Initiative
FROM: lauren.amira@charmtech.com
Once again,
The implicit assembly line requirements are exacting. In some places we have a total per unit clearance of maybe half a centimeter in some axes.
That's before we consider how tight our time requirements might be. Any assembly line is fundamentally a series of dominoes falling in sequence.
You're basically asking one of those dominoes to step out of line and do something else before stepping back into line just in time.
We can't do this. There's just no viable way to ensure hardware safety.
SUBJECT: RE:RE:RE:RE: On Prem Cloud QA Initiative
FROM: mike.roberts02@charmtech.com
Gotcha. I'll escalate the discussion further up the chain.
It sounds like upper leadership on this project needs to be informed of the limitations involved.
SUBJECT: QA Initiative Kickoff
FROM: dan.gorman09@charmtech.com
TO: lauren.amira@charmtech.com
CC: meghan.teller04@charmtech.com, mike.roberts02@charmtech.com, emil.bonchance@charmtech.com
Hi Lauren,
Dan here. Leadership has made the decision to move forward with the initiative.
Additionally, in order to maximize Mike's support on making sure we ship this into production ASAP,
we'll be assigning Emil as Technical Project Manager. He'll be working with you to manage the day to day.
Upper leadership is looking forward to a working proof of concept by the end of the quarter.
Investors are already very interested in our success here, and we have a unique opportunity to really make a splash in the market with regards to cost savings.
You'll be helping revolutionize our company's relationship with cloud computing resources.
Let's all do our best!
SUBJECT: RE: QA Initiative Kickoff
FROM: lauren.amira@charmtech.com
Hi Dan,
Just wanted to set expectations.
First and foremost, we will be unable to do allow any form of physical movement as part of any of our test suites.
Second, we'll need to work on a whole new job parallelization and queueing system in order to interweave both steps from the tests and the assembly jobs.
This is a distinctly non-trivial ask, and we'll probably need additional software engineering resources in order to ensure we meet our goals.
Third, we will need at least one established test line in order to limit possible issues; it is unsafe to test any of these in production.
The more test lines we can have, the more thoroughly we can test.
SUBJECT: RE:RE: QA Initiative Kickoff
FROM: dan.gorman09@charmtech.com
I'll get you three.