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
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.
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
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
digdeeproots retweeted
I think the biggest risk with refactoring is how many devs misunderstood the term and know almost nothing about the actual practice. Our industry is full of people using names without understanding what those names implied. We are still looking for the silver bullet.
digdeeproots retweeted
The recording of the “No Bugs” session of the Art of Agile Development #bookclub is up! It featured @arlobelshee and @LlewellynFalco discussing legacy code, long methods vs. short methods, understanding user needs, and more. jamesshore.com/v2/books/aoad… #agile #aoad2 @OReillyMedia
digdeeproots retweeted
I've turned down Agile-adoption jobs where they want a roadmap with benchmarks and metrics and estimates and a finish date. It just doesn't work that way. Sorry. You cannot become agile using a rigid plan. You have to approach the problem in an agile way. 1/3
digdeeproots retweeted
What a fantastic visualization.
What happens with communications on teams and why do we keep them small?
digdeeproots retweeted
Every so often there will be a burst of Twitter conversations on the “Reverse Conway Manoeuver” and related topics.
I find this encouraging, but not for a reason you might suspect.
Hear me out; this is important.
1/28
digdeeproots retweeted
Ready for refactoring processes that make your code testable without risking bugs? #MenderCon sponsor Deep Roots is here to help your team get real results! Check out their website to subscribe, chat, and find out about their processes. buff.ly/395MZCR
digdeeproots retweeted
I'm looking forward to a great conversation on new ways to think about dev and test
digdeeproots retweeted
Reflecting on the difference between conventional commit notations conventionalcommits.org/en/v… and @arlobelshee commit notations github.com/RefactoringCombos…
digdeeproots retweeted
Made a getting started with #ApprovalTests.python [video]
youtube.com/watch?v=2PbA273J…
digdeeproots retweeted
Special thanks guests we have had on the show (Part 6 of 6): @nagworld @kawaguti @kohzas @martin_lover_se @JoshuaKerievsky @modernagile @Aaron_Griffith @arlobelshee @digdeeproots @mhwilleke and Willem Larson
digdeeproots retweeted
"Gnarly legacy codebases are like tangled balls of yarn, full of knots. There are two kinds of knots:
- Dangerous-to-change
- Difficult-to-isolate-to-test"
Wisdom from @arlobelshee
digdeeproots retweeted
I think about this too. The idea of "fundamentals" comes to mind, including selecting *which* fundamentals. I am always in awe of how my friends @digdeeproots are able to break things down into small habits without losing sight of impacthttps://insightloop.digdeeproots.com/