Couldn't find any documentation on how to rebuild it when it's broken. I found some filled cans, was not sure where to put them. Also some clear schema with the don't matrix for the E and the F would be useful.
Are there some tests I can run to ensure its done correctly?
@sebastienros I thought you had already tested it, and it didn鈥檛 go well. Next time just some light smoke testing please :smile:
Any docs need to take optimal performance into consideration too #perfculture
Here are some suggestions on other patterns-based designs that could be used:
The original, ~6.5' (2 meters) Tower of Coke:
The revised, ~9' (2.7 meters) Tower of Coke:
Cherry Coke hasn't tasted the same since they changed from this epic can design...
@bricelam so true... so true...
!!!
@roji I believe I told you I'd try to find the pictures... those are the pictures 馃槃
And I thought we were doing so well...
@roji oh you were doing great, just with a different set of objectives 馃槃
Those are kind words @Eilon but I'm just gonna go be depressed in the corner now, thanks.
Blocked on lack of glue.
I found that regular super glue works, but is not very effective. It is too "thin," and doesn't adhere well to the shiny surface of the cans.
Some sort of thicker cement would be ideal. We'd need to run some structural tests on glued sections to figure out what works best.
Label area-tools? Definitely avoid up-for-grabs, or at least add a providers-beware in case any are standing around...
Before (only picture we have is after some damage):
Crash dump:
After re-build:
Initial observations from analysis of re-build:
The EF team definitely needs a tack welder in the office.
Tack welding aluminum is not trivial, apparently. But if we put our minds to it... we can definitely start a huge fire! 馃槃
You broke it and built it again from scratch? You guys need to add "core" to it then... Only a few more cans...!
A first attempt to add structural integrity (Scotch tape) resulted in disaster. We really need to hire a hardware engineer. Software engineers building real-world stuff isn't working too well...
Just today I thought "What are Microsoft doing that is so important that they ignore EF core Many2Many implementation for so long". Then I saw this.
That is EF Core Many 2 Many - Coke, Pepsi, Dr Pepper, Mountain Dew....
Current status: reconstructed, realigned, but still no glue:
I find it incredulous that no blame was laid for this destruction when, as ever, the fault lies with @davidfowl (Junior) who apparently, when I was away, removed the security from my desk, borrowed some toys and flung them with no apparent planning or threat model. He takes after his dad that one.
@blowdart Well...I heard that he was encouraged by a certain French gentleman. At least some of the blame must lie there. After all, if we're not responsible adults in our own workplace, then how can we expect the younger generation to learn appropriate behavior?
From a security POV I will point out that I firmly instructed the young man in the proper use of my pokeballs, which was to throw them at his daddy _ONLY_. Unapproved usage cannot be secured.
Has JB Weld been considered?
Also from a quick examination the initial vulnerability still exists and the current implementation remains insecure and unprotected.
It may be time for a comprehensive Sodacan Defense Lifecycle (SDL) review
@AndriySvyryd to post final picture.
Will there be Lego style instructions so we can build our own at home?
@pmiddleton You can see the source on some of the photos and there should be no licensing issues if you just copy that.
There was a hacker attack sometime between 2018.07.11-20:30 and 2018.07.12-09:00.
Sorry for the inconvinience. Services have been restored:
Let's not rule this out... http://mynorthwest.com/category/earthquake_tracker/
We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.
Most helpful comment
Just today I thought "What are Microsoft doing that is so important that they ignore EF core Many2Many implementation for so long". Then I saw this.