digdeeproots
@digdeeproots
Followers
174
Following
72
Media
16
Statuses
369
Subscribe: https://t.co/KxuLCXGgvG Chat: https://t.co/6AoCcHWNjr . Register: https://t.co/5XXxK2CaHg . .
Asheville NC
Joined April 2019
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. https://t.co/66PjDy1zXQ
0
0
1
👨💻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.
4
24
106
Yay! We have re-deployed https://t.co/ZIVfeCjAmg. 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.
0
0
2
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!
0
0
1
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! https://t.co/mVNZO0bP2K
22uts435088.typeform.com
Turn data collection into an experience with Typeform. Create beautiful online forms, surveys, quizzes, and so much more. Try it for FREE.
0
1
1
Arlo | Refactoring with Depth -- Culture and Code: Continuous Improvement that Sticks
0
0
1
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! https://t.co/LDpI34uLk2
eventbrite.com
Welcome to our virtual water cooler! Or in the classic Arlo method: whiskey hour.
0
4
3
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
19
33
155
Note the this account is not verified. Now you know it's credible. 😆
0
0
2
What blended mode is to @arlobelshee in Continuous Automation. https://t.co/uqmOOYByHJ
linkedin.com
You want to do automation, but you’re trapped in doing it in big batches. In order to make automation continuous, we have to change our goal definition. Traditionally, we think of the goal for...
0
1
1
Yaaas! Our brains are meant to work together and learn in small bits. #Mobbing for the win!
Solo coding: I get stuck, I do a few minutes of web searching until I learn just enough about the thing I'm stuck on to keep working Mobbing: we get stuck, someone in the group who did deep research on the topic spends a few minutes educating everyone, then we keep working.
0
0
3
.@ArloBelshee's refactoring philosophies shared on the Deep Roots' LinkedIn page a couple times a week. Follow and engage! https://t.co/9in4FRqdud
linkedin.com
Why does Deep Roots do and teach everything " ... as a Process"? Because it is a mechanism for turning any batch mode activity into a continuous activity. For example, another name for “Naming as a...
0
0
0
Our legacy project from 2 years has gained a lot of new features, including Continuous Candy Collection🎃🤣
0
0
4
Check out our blogpost by @arlobelshee on ways to automation /without/ uncertain return, impracticality, and high expense!
When Should I Automate? by @digdeeproots
0
2
1
@digdeeproots @Johnicholas @alexander_bird @m4gw4s @afilina @arlobelshee @LlewellynFalco 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.
0
1
3
@m4gw4s @afilina 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 https://t.co/nmUKfpKcMX is really helpful.
0
3
8
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
15
75
436
Great strategy for teasing apart business logic and an annoying dependency. Always enjoy Nicolas' blogs and tweets about refactoring!
0
0
1