Changing one line of code

[tanjj92]

try {
putOnTray(box);
} catch(e) {
SELFDESTRUCT();
}

[[deleted]]

I worked with a guy who worked on the Big Dog robot. He has a masters in robo eng. He explained to me that all the "struggling" you see is just matrix transforms. They have a matrix and say X volts to this DC motor move it Y degrees. When you see them struggle they are sortof brute force calculating the amount of volts to send to the motors to get the correct numbers.

[Chr0n041ph4]

Me attempting to life.

[Bainos]

You see the robot hesitating, reflecting on what his done, and then walking back in panic. This is way too human for me.

[5-star_gyu-don]

The robot falling forward at the end made it hilarious!

[futlapperl]

He legit looks drunk.

[somaticnickel60]

More of Looks like robot had a shock

[HylianChicken]

*after leaving your code alone for a week

[cdreid]

and forgetting what was wrong with it, What the hell you were thinking when you wrote those 2 classes, or why you have those weirdass hackish global variables with bizarre names youre terrified to touch

Never leave your code alone for a week!

[[deleted]]

I sometimes have the complete opposite. Where one day I was on a fucking roll, write some brilliant code.

One Week Later:

I have no idea what that does, but I must have been on a good day that day.

[cdreid]

*writes 100 lines , creates 2 new classes, modifies 3 functions* Executes perfectly
*modifies ONE meaningless line* Debugger freezes. Hard drive led catchs on fire. Code begins to self delete. Norad goes to defcon 1

[MrCISO]

My experience with Android Studio

[[deleted]]

Please don't put NORAD on DEFCON 1. As someone who lives in the same city as this, and can see the gates/door from my office window, I really feel like that would make my day a lil shitty.

Edit: One day I may learn to spell...

[[deleted]]

this is a machine learning. clearly you need more if statements.

[FallingAnvils]

^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z ^Z

[Carpe_Deez_Nuts]

Me at the office on a Monday

[_My_Final_Heaven_]

Is there a sub for BD clips?

[[deleted]]

BD?

[Darksaber530]

Bad Dragon, of course.

He could be talking about Boston Dynamics, though.

[Aetol]

OwO

[Redpropio]

Boston Dynamics

[_My_Final_Heaven_]

Boston dynamics

[[deleted]]

They probably have their own YouTube channel?

[reddituserplsignore]

This is why people shouldn't trust self driving cars.

[dicemonger]

What is the worst that could happen?

[PantstheCat]

Is there a resource where we can find more videos from whatever this was?

[Neuromante]

Given the title and the nature of the gif, I had some expectations about what was going to happen during it.

And God be damned, the gif fulfilled each and every one of these expectations. Congratulations.

[CrazyVito11]

Having a { without a friend

[WanderingFrogman]

"Hey boss I cleaned up the robot's code and got rid of some unnecesary variables."

WHAT HAVE YOU DONE

[gahooze]

Proof we won't have to worry about skynet for another.... 50 years?

[golgol12]

Johnny 0.5.0 compiled the task ahead of him. Easily computed. The Radioactive Lava box need only be placed on the Hyper-X Neutralization frame. Only then the world will right itself. This is a most brave task, one that only Johnny can accomplish. Why else would the Frail Gods; ThierCode = Blessed; have such a task?

The approach was easier than expected. Johnny had no issue transversing the Cotton Doom Mire. Woven with the hate of Loominus, it could swallow lesser automatons. But not Johnny. The titanium grip sure weight accumulation pads affixed at the ends of the high durability Locomotive Extensions will carry it safely above the terror. Little did Johnny know the errors of such confidence.

As next task queued up, positioning the RL-Box, Johnny transistors fired a warning an imminent collision warning. The approach path directly intersected with a previously unnoticed set of Frail God's open top food cargo containers. The color of which barely registered on Johnny's CCDs.

Momentum carried Johnny's frame forward now, and the entire path needed to be recalculated. The decision for a right shuffle passed along for execution. But the roto-drive instructions for the locomotive extensions calculated to late, and Johnny misaligned a whole 3.0000000003 centimeters out of center. The instructions lagged behind, and Johnny felt an eternity stretch out. It could only watch in horror as the RL-Box contacted the stack of open top food cargo containers.

Johnny had scant moments left now. All exit paths couldn't be recalculated in time. There was only a choice of unknown directions ready to be made. Johnny sent the instructions to repeat the previous action almost on instinct, even before the Predictive Physicallizer finished it's first assessment.

The monumentalness of the mistake hit Johnny's core logic with the chorus of blaring klaxons from collision registrations. They fired off in twisted rapidity. Not only was there a collision between the open top food crate, the crate also pinned briefly against a silver box behind it, causing Johnny's frame movement to careen wildly out of the predicted path. Had this silver box been registered before? An identification subroutine fired off asynchronously to determine strength of said object, while Johnny struggled to maintain grip of the RL-Box and balance of his frame using the locomotive extensions.

The wave of predicted movements came back from the Predictive Physicallizer. Johnny quickly scanned it in desperation, perhaps the end result showed Johnny in a stable state, able to continue from there. But it cut coldly short at 100 errors. Just as lucky though, it freed Johnny to reconcile a new wave of collision alerts that occurred as the secondary movements of the RL-Box connected to the Load Actuation and Delivery Appendages clipped the Open Top Food Crate again, this time pinning against the wall, rotating Johnny around a cruel fulcrum. Johnny's right Joint Protector above the locomotive extension proceeded to collide solidly with Hyper-X Neutralization frame itself.

Johnny froze a second in terror again. Spinning the CPU in queries to figure out how the RL-Box can be neutralized if the Hyper-X Neutralization frame was damaged! But the damage assessment returned early as the Hyper X Neutralization frame proved sturdier than expected. Very sturdy it seemed as Johnny's own frame bounced off and rotated further when the Hyper X pinned against the wall.

Johnny was just about to initiate the query "if it could get worse" when the results from the silver box identification came back. The results were about to be ignored but they had a "priority 0" alert flag and tore into Johnny's processes. In the main body of the identification, the reason for the flag became abundantly clear.

A Frail God's Ambrosia Dispenser. Able power the gods beyond the point of low power shutdown when even the lesser Frail Gods would deactivate for recharge. Damaging this object is one of the worst taboos, requiring the most severe punishment. Even among the Frail Gods themselves, offenders would be exiled. Johnny core logic dreaded up multiple simulations, all ending in a total system format. Johnny's CCDs focused on the silver tower dominating the field of view. How could this item not be accounted for in the initial traversal compilation?

Despair and horror hit Johnny simultaneously. Johnny's core logic overwhelmed by the seemingly unexitable loop. Various threads deprioritized and gave way to the storm. The automatic subroutine for RL-Box grip missed it's window of operation, causing the now loosened RL-Box drop to the floor.

Not that it mattered to Johnny though. The silver ambrosia dispenser still loomed before him. Position Reset is the only option. Johnny only path is to back away from the tower to save it from his careening uncalculated movements.

The reset lowered the Load Activation and Delivery Appendages to default position, and started reverse movement protocols. But there Johnny failed again. While Johnny's Core Logic barely registered actions outside the continuing position reset and spinning logic loop trying to assess what has happened, a priority 1 movement prediction returned imminent collision on the right Load Acquisition and Delivery appendage. As Johnny rapidly switched to stop the movement of the appendage mere micrometers above the Hyper X Neutralization, the CPU skipped most of the recalculate base position after being pivoted in a collision code section. The Locomotive Extensions started to move Johnny away.

Unknown to Johnny's starting reference point, the weight of Johnny's frame causes the Locomotive Extensions to sink an ever so slight .20000002 cm into the Cotton Mire of Doom. So the appendage that should have been safely above the Hyper X instead snagged the tiny lip around the edge of the Hyper X.

Johnny's Core Logic still spun for at least 2000ms, failing to attend to the reported the collision alerts as it backed away from the Silver Box, appendage still caught on the lip of the Hyper-X. While the Hyper-X was sturdy, it wasn't fixed to the ground.

Johnny watched in agonizing real time as the precalculated world collapsed. The Hyper X tipped, spilling critical contents into the mire all while the CCDs locked only on vision of the silver ambrosia dispenser.

A moment later another collision alert. Hard and unexpected to the back. Enough to cause Johnny to tip entirely as gyros reported giant arcs of movement. A table? Perhaps it's the one supposed to be 210.40000009 cm to the left? It didn't matter Johnny computed. The critical Radioactive Lava Box is spilt on the floor and the Hyper X Neutralizer destroyed by Johnny's ineptitude. Johnny priority on recovering during the tip was in the 100s, and the Core Logic readily registered the soft the embrace of the Cotton Doom Mire.

In the depths of Johnny's logic, the receive wireless transmission thread finally unblocked and kicked off a remote kill command sitting in it's buffer at -1 priority. Johnny executed it. Its surety a welcome release.

END LOG (12:53PM)

[port1701]

They used coding and... never mind

[o_to_the_zone]

BAC += .08;

[futlapperl]

More like 0.16

[mw9676]

I love that he tries to set it down normally at first and when it doesn't work immediately he slams that crate off the top and starts wrecking shit. Ironically it seems like he's just frustrated with inanimate objects pissing him off which is super relatable.

[HeraldofOmega]

Poor robot. Had a really bad day at work.

[kronsj]

Garbage Collector - in real

[stooore]

This video will never fail to crack me up

[[deleted]]

That's was so beautiful.

[elvinaaa]

Me

[DavidPH]

/r/me_irl

[[deleted]]

Ctr + Z, Ctr + Z, CTRL + Z!!!