Відео

"You'll never be able to fill 45 minutes by saying the same thing over and over again" "Like what?" "Like, say, you need to write software so you can rewrite it from scratch in one week" "No problem, hold my beer.."

AoC 2024 hype!

This is a total bullshit when it comes to software development in real world. If you write software to measure a temperature in your own house, maybe you can use this methods 🤣

I should WATCH and not only listen... I realized it at 22:40 when Mark is saying "I like meth"... yea

It would be nice to see this from the angle of entering an enterprise that already is overly-coupled and guiding improvements one small, deletable addittion / strangulation / wrapper / adapter at a time.

I can't count the times I've worked on systems where loose coupling, and no proper data definitions and typing in event buses led to spaghetti that goto spaghetti soup could only hope to emulate. These kinds of systems often rely on anecdotal hearsay and lived memory as documentation systems, and debugging prod logs lead to a bunch of "oh yeah, I remember now!" Sure, it's easy to rewrite little modules/actors/microservices in schemaless, loosely coupled software - but with each rewrite, something of the original intent and lived knowledge will be lost. This is more akin to credit card debt, or high-interest rate variable mortgage.

The problem I see is that the tech debt often lives in the in-betweens, in the contracts between services, in the models being passed around. I would like to see a more concrete discussion of what it looks like to reorganize a 17,000 line monolith into deletable, one week chunks.

nice bullsjit. We all know know we should drink more water, but all give a shit!

that's why goos, it takes this idea messages passing and showcases it. always thankful to these authors...

it's like my ideas put forward in better way... same thing i realized, 12:37 thanks...

Unix philosophy 30 years ago? More like 50 years ago

Thank you very much. That was very useful.

Much truth in there. However, not all debt is contained within one one-week bit. Then fixing that is not just a week. And when the behavior of the system emerges from the connection of small bits of behavior that's also nothing to rewire within one week.

Hey Tretton, I’m Nik and I’m researching consultants’ problems on UA-cam (I’m not selling anything). What are your biggest problems with UA-cam? (Don't have enough time, aren't getting enough leads through it,...) Your response would mean so much to me, so thanks

I don't buy this. The idea that you write a ton of small programs such that they aren't interdependent upon each other is not practical for most applications. Any sufficiently complex program will have dependencies such that when X changes, you also have to change Y. In the worst case, this cascades and now you have to change A, B, and C.

As Greg suggests, small programs have more advantages than disadvantages, but things are not that much simple always and also things are not viewed technically always.. Programs size and in other words programs boundaries are political aspects in many companies… To be happy with it or not, it happens that around programs some form of ownership is created.. Finally, programs size are in most cases further than just a technical issue

Writing small programs inside a a big program is ok and not a new idea. But, overhead of managing and understanding too many small connected programs is still complex.

I prefer Native Android

Geat talk!! Greg again confirmed that in IT there is too much teenager-like attitude 'won't learn from elders - my world is very different. Let's invent!'

Note this video was taken in 2016! But as always excellent stuff from Jon Skeet! Thanks for posting.

Jon Skeet can solve NP-complete problems in constant time. He has the answers to every one on the back of his hand

That was great. The state monad was a twist for me because of the "life force" analogy. I always thought that it would be something for a logger at the end. This was a very good presentation

In an event sourced system, does anyone know how to delete the code and still enable replayability of events? Keeping around old models for replayability doesn't seem like a great idea, but how do you do it otherwise?

Thank you for your impressive #IWD2024 #InspireInclusion activity 💜 for #InternationalWomensDay

Fantastic talk! This solved the mystery of options and async in multiple programming languages for me at once. I wish I could like it more than once. Great job!

Lol us Eve players are a rare breed indeed.

Wow! This is the talk I need to give my team!!!

"Your tools affect your code". Exemplified by 'The medium is the message'. Mcluhan was right.

This is such a great talk. Thanks to Greg and the organizers of this talk.

I'd make this talk mandatory to watch for every software developer.

I think I've seen this before. When was the original?

Haha! Cecilia! hej hej :) /Diego

It's unfortunate we can't see the code slides 😒

Puzzles are crap... i prefer myst type of puzzles to solve in cli fashion....

Yay! Greg lives!

Loved. This one. I went home and ordered three books, migrated my notes and got a new reader app!

one bad thing about adventure of code is that it does not encourage you to solve the problem. I quit after like 5 days last year, and this year I quit after first one lol. I thought it was supposed to be for people who wants to learn to code, and for them who can code to help a bit. I hope someone does a Adventure of code for those who dont code that much but wants to learn.

❤ Great legacy = transmitting micro debts ! The whole talk is great, pure wisdom. Thanks for sharing

Loved it! 🙌

cool

'Promo SM'

Version 4? This looks extremely old video

thank you, this will be a great video to fall asleep too <3 <3 <3

2:04 I'll be there next year! Just send me the location :)

Where's the money

Liar

Where's the funds

Where's my funds

his tone makes me hang myself

Thank you <3