Dylan Beattie - The Cost of Code

DevConf - The Software Craftsmen Festival for Sharing Knowledge and Inspiration (devconf.pl/)
Coders code. That’s what we do. We write functions and classes and modules and we conjure amazing systems out of thin air. Electrons dance at our command; with a few keystrokes we can solve the most complex calculations, find hidden patterns in the data of our everyday lives, and send information flying around the planet at the speed of light.
The world uses our code to book flights, pay taxes, talk to friends and family… and before too long, our code might be driving cars, diagnosing illnesses and convicting criminals. Code runs the world. And when our code goes wrong, the solution is almost always… more code. We ship millions of lines of code every day - and, in these days of smartphones and networks and IOT, a single line of code could be running on millions of devices within minutes of us deploying to production. But have you ever stopped to consider the real cost of those lines of code? Your code might end up running in production for years, maybe decades.
It’ll become one small part of a giant global codebase that’s using literally trillions of processor cycles and hundreds of billions of kilowatt-hours of electricity every year. A codebase that’s hiding countless vulnerabilities, flaws and dependencies. A codebase that's driving users to buy millions of new laptops and smartphones and tablets every year because the old ones are too slow, or won't run the latest apps. A codebase that is literally changing the world we live in - and not always for the better. Join Dylan Beattie at DevConf 2019 for a stark, sobering look at the real cost of the code we’re shipping every day. What’s the real cost of code - to our organisations, to our society, to our environment? How can we help our teams and users understand that cost? And what can we do to reduce it?

[@UliTroyo]

Each of Dylan’s talks is a voyage. I just wanted to be entertained during breakfast.

[@joshmarsten7294]

That would be better breakfast than coffee

[@ShinjiGetsGrounded]

I'm not even a programmer I just watch all this guys talks

[@Proppeti]

I don't even speak English!! Just kidding 😂😂

[@HeilTec]

Amazing perspective, great view, and
clearly presented in present tense
(counting the occurrence of the word "now" - ;)
in a riveting fashion.

[@peterwmdavis]

15:45 very relevant in 2024 with the xz backdoor

[@dgkimpton]

Somehow I suspect the response will be lots of head nodding, agreement, and then going back to doing exactly what was being done before :( These issues are so huge it doesn't seem like an individual can fix them... and yet if individuals don't act nothing will happen. I suppose talking about these issues is a good first step.

[@joshmarsten7294]

Interesting

[@cx123456]

This was probably the longest and most entertaining sales pitch I have ever seen.

[@frechjo]

Great talk.

[@edgeeffect]

Wow Dylan.... I mean, I usually "quite like" your talks..... but, 'kin'ell, that one was "a biggie"!
"Bardzo dziękuję" indeed!

[@michalmikulasi5193]

that was fking awesome. really awesome

[@BryonLape]

I've been using the same iPhone for years

[@antdx316]

great talk = true

[@edgeeffect]

Great talk === true. ;)

[@hardcodedsoftware4212]

@@edgeeffect error line 1: variable "talk" is not of type "boolean", talk is of type "great"

[@lliammcbean6819]

greatTalk(greatTalk());

[@kayakMike1000]

Um... Two different functions.

[@lliammcbean6819]

@@kayakMike1000 wot?

[@otesunki]

@@kayakMike1000 depends. it could be varargs or overloading
probably javascript, though

[@pianochess1882]

@@otesunkialso default argument

[@pianochess1882]

@@otesunkialso default argument

[@gwickenden9040]

It has a main-main-ten-ten-ance-ance cost ;)

[@peterwmdavis]

38:46 this is false. The plane flies just fine without MCAS. It’s just that it would have flown *differently*, which would have required a different type rating for pilots.
Great story, but I want to correct the misconception that the 737 MAX is fundamentally unstable.

[@diablominero]

All the radioactive stuff was in the ground before we dug it up, so what's the issue with putting it back when we're done taking the neodymium out of it?

[@janhofmann3499]

The ore was a solid block and over time released only few radioactive particles when exposed to water. Good storage. Now it’s radioactive sludge. This stuff MUST not get in contact with ground water.

[@diablominero]

@@janhofmann3499 fair enough, but that's pretty easy to solve. Just let the water evaporate and leave radioactive dust behind, mix the dust with clay, fire it, and bury the ceramic. And then we don't have to put up signs telling people not to dig, because there were no signs for us and we turned out fine.

[@hhhpestock951]

free weed is better then free beer

[@devcybiko]

Thank you, Captain Obvious. Never has there been a more meandering and pointless presentation. Lots of entertaining data points, but no real solutions nor best practices. As usual - enteraining as all get out. But just a nic 45-minute click-bait meme. No real estimate of "the cost of software."

[@sfdntk]

Why are you so upset?