this post was submitted on 04 Mar 2024
5 points (100.0% liked)
Talks
79 readers
2 users here now
A community to share and discuss good (conference) talks in/about software industry.
Please try to listen to a significant chunk of the talks before engaging in discussion and try to avoid responding just to the title of the talk.
Rules
- Follow programming.dev rules
- Be excellent to each other, no hostility towards other users for any reason
- No spam of tools/companies/advertisements.
Credits
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
founded 9 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Good talk. Watching refactoring is fun.
I feel like most of what he talks about is common knowledge now. But then again, I stumble upon code written by experienced developers that is just like the one he started with: unclear responsibilities, poor encapsulation, etc. What is even worse is: I sometimes catch myself writing code like that :)
What we do requires continuous attention to detail. We sometimes get tired or lose focus. And that may result in poor quality code. However, that’s only one reason to end up with such code. I think the other (and more common) reason is accumulating functionality. Einar Høst’s talk about technical debt touches upon that aspect. You start with a beautiful model. But then
ifstatements start raining on it. If we are not diligent, we end up with a mess.