Great strategy for teasing apart business logic and an annoying dependency. Always enjoy Nicolas' blogs and tweets about refactoring!

I tried skipping TDD this week. It went faster But then I worried my stuff didn't work, so I wrote some unit tests. I found & fixed several silly bugs Then I needed to change stuff, but the classes were big & tangled. So I refactored I'm almost finished fixing my "faster" work

Magosányi Árpád 🇺🇦 Anna Filina There are some great resources on incremental improvements to legacy systems. Are you familiar with the work of Arlo Belshee and his project digdeeproots? Also Llewellyn Falco does live coding of legacy coding refactoring on twitch. The legacycode.rocks is really helpful.

digdeeproots @Johnicholas Alexander Bird @[email protected] Magosányi Árpád 🇺🇦 Anna Filina Arlo Belshee Llewellyn Falco I'm afraid there is no article (I should write one), just this picture. Also: - start from a fresh pull of main - make branch - commit, commit, commit - git merge --no-ff Go fast + stay green the whole time. Avoid merge conflicts by checking in first.

When Should I Automate? by digdeeproots open.substack.com/pub/digdeeproo…

Check out our blogpost by Arlo Belshee on ways to automation /without/ uncertain return, impracticality, and high expense!

Our legacy project from 2 years has gained a lot of new features, including Continuous Candy Collection🎃🤣

.@ArloBelshee's refactoring philosophies shared on the Deep Roots' LinkedIn page a couple times a week. Follow and engage! linkedin.com/posts/dig-deep…

Yaaas! Our brains are meant to work together and learn in small bits. #Mobbing for the win!

What blended mode is to Arlo Belshee in Continuous Automation. linkedin.com/feed/update/ur…

Note the this account is not verified. Now you know it's credible. 😆

Test-after: 1. Write code 2. Write tests (green) 3. Change tests to make them red 4. Change tests back to green 5. Change the code to make tests red 6. Change the code back to green 7. Refactor Test-first/TDD: 1. Write tests (red) 2. Write code (green) 3. Refactor

Our quarterly Ask Me Anything with Arlo Belshee is in just two days! Sign up for your "seat at the bar" to chat about automation, anything as a process, and other legacy related topics you bring! eventbrite.com/e/408763551787

Arlo | Refactoring with Depth -- Culture and Code: Continuous Improvement that Sticks digdeeproots.substack.com/p/culture-and-…

Are you interested in a 2-hour low cost workshop for Arlo Belshee applying continuous improvement that sticks for you or your team? Let us know! 22uts435088.typeform.com/to/c9bhflXm

Our website has been the victim of WordPress updates not playing nice with our customizations. We are now moving it to a static site under our control. Content and URL access will be back as soon as Arlo Belshee can find the remaining hours to finish it!

👨‍💻Unexperienced developer: I need advice from the seniors. 👨‍💻👨‍💻Experienced developer: I don't need advice. 👨‍💻👨‍💻👨‍💻Really experienced: Let's see what the new guy in the team thinks about that topic. Maybe it can shift my perspective. Maybe we both can learn.

Yay! We have re-deployed digdeeproots.com. It is now 100% under our power, so live site issues are now 100% our fault 😅 Optimisations still to come, but content is back! Disclaimer: cookbook coming soon - still working to get from original admin.

This article represents the backbone of what Arlo Belshee does with coaching through Deep Roots. We help teams work in tiny steps even in the ugliest code. codeiseasy.substack.com/p/coding-with-…