digdeeproots

Subscribe:

[digdeeproots @digdeeproots]

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

[Samuel Motal @SamuelMotal]

👨‍💻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 @digdeeproots]

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.

[digdeeproots @digdeeproots]

@jitterted Apologies, we have been knee deep in deliveries and live site issues, as you can see! We are moving off the platform and onto our own site. We are gratified that you enjoy the content and appreciate your patience!

[digdeeproots @digdeeproots]

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!

[digdeeproots @digdeeproots]

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

[digdeeproots @digdeeproots]

Arlo | Refactoring with Depth -- Culture and Code: Continuous Improvement that Sticks https://t.co/NfVdQ8jdVs

[digdeeproots @digdeeproots]

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

[Wisen Tanasa @ceilfors]

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 @digdeeproots]

@jasoncwarner The only place for microservices is with 5k engineers working on one product. Alignment is too expensive at scale, so you need independence. And you have the staff to handle the overhead that entails - including 1k people working on infra and automation.

[digdeeproots @digdeeproots]

@jasoncwarner Incremental architecture explained brilliantly. Also great context acknowledgement. When you have 30 ppl, keep the # of shippable units small. When you 7k, it gets large. In my exp, it's best to have each 8-11 ppl team own 1-3 shippable items.

[digdeeproots @digdeeproots]

@jasoncwarner Thus as he says: if you are a 5-50 person startup looking for product/market fit, then you have 1-2 teams, and should be either a monolith or a set of apps - depending on your current degree of discovery vs elaboration. This keeps pivots fast because deploy is easy.

[digdeeproots @digdeeproots]

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

[digdeeproots @digdeeproots]

What blended mode is to @arlobelshee in Continuous Automation.

https://t.co/uqmOOYByHJ

[digdeeproots @digdeeproots]

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

[Alexander Bird @[email protected] @alexander_bird]

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.

[digdeeproots @digdeeproots]

.@ArloBelshee's refactoring philosophies shared on the Deep Roots' LinkedIn page a couple times a week. Follow and engage!

https://t.co/9in4FRqdud

[digdeeproots @digdeeproots]

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

[digdeeproots @digdeeproots]

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

[Tom Henricksen @TomHenricksen]

When Should I Automate? by @digdeeproots https://t.co/FLlUiyblfU

[Tom Henricksen @TomHenricksen]

When Should I Automate? by @digdeeproots https://t.co/FLlUiyblfU

[neé Jay Bazuzi @jaybazuzi]

@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.