Subscribe: https://xitter.cf/t.co/KxuLCXGgvG Chat: https://xitter.cf/t.co/6AoCcHWNjr . Register: https://xitter.cf/t.co/5XXxK2CaHg . .
Asheville NC
Joined April 2019
- Tweets369
- Following91
- Followers172
- Likes72
This article represents the backbone of what @arlobelshee does with coaching through Deep Roots. We help teams work in tiny steps even in the ugliest code.
codeiseasy.substack.com/p/co…
digdeeproots retweeted
👨💻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.
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 @arlobelshee can find the remaining hours to finish it!
Are you interested in a 2-hour low cost workshop for @arlobelshee applying continuous improvement that sticks for you or your team? Let us know!
22uts435088.typeform.com/to/…
Arlo | Refactoring with Depth -- Culture and Code: Continuous Improvement that Sticks digdeeproots.substack.com/p/…
Our quarterly Ask Me Anything with @arlobelshee 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/40876355178…
digdeeproots retweeted
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
What blended mode is to @arlobelshee in Continuous Automation.
linkedin.com/feed/update/urn…
Yaaas! Our brains are meant to work together and learn in small bits. #Mobbing for the win!
.@ArloBelshee's refactoring philosophies shared on the Deep Roots' LinkedIn page a couple times a week. Follow and engage!
linkedin.com/posts/dig-deep-…
Our legacy project from 2 years has gained a lot of new features, including Continuous Candy Collection🎃🤣
Check out our blogpost by @arlobelshee on ways to automation /without/ uncertain return, impracticality, and high expense!
digdeeproots retweeted
When Should I Automate? by @digdeeproots open.substack.com/pub/digdee…
digdeeproots retweeted
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.
ALT A series of git commits, in quick succession. 7 refractorings, 1 behavior change, and a single-sided merge to master.
digdeeproots retweeted
There are some great resources on incremental improvements to legacy systems. Are you familiar with the work of @arlobelshee and his project @digdeeproots? Also @LlewellynFalco does live coding of legacy coding refactoring on twitch. The legacycode.rocks is really helpful.
digdeeproots retweeted
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