Programming

17373 readers

201 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Tidy First? | Henrik Warne's blog (henrikwarne.com)

submitted 10 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

The book “Tidy First?” introduces the concept of "tidyings," which are small refactorings that don't change program behavior, but make it easier to implement behavioral changes. It’s important to structurally prepare code before implementing behavioral changes. A balance must be struck between the time value of money and optionality in software, highlighting the need to create a structure that supports quick changes.

I stole the summary from https://tldr.tech/webdev

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 6 points 10 months ago (1 children)

I have noticed that many developers are reluctant to introduce explaining variables/constants.

I do, and it's very helpful for me and my futur me and the other one.

[–] [email protected] 5 points 10 months ago

Yeah my own code is greek and latin to me if I come back a few months later. Excessing logger statements and descriptive variable/function names save my bacon more than I can admit.

[–] [email protected] 3 points 10 months ago

Neat post. I'm too lazy to read the book, so I appreciate the summary.

I like the taxonomy of refactorings. It's always helpful to have names for things.

[–] [email protected] 2 points 10 months ago

Sounds like the book would be a great resource.

I've hopped out of electronics and now make a living coding in an adjacent area, but find myself working with colleagues that are happy approaching all tasks like a script.

Code reviews, coupling etc arent part of their vocab so in lieu of peer role models im on the look out for good resources thst aren't just chasing the next buzzword.