Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
use case driven Profile picture
@tpierrain
May 26, 2023 • 7 tweets • 7 min read • Read on X
Scrolly
Refactoring Blockers

- Lack of patience
- Seeking perfection (can be demotivating)
- Guilt-shame-despair
- I don’t know (we don’t trust our own ability-opinion
- No spears, no spikes
- No compassion

@ClareSudbery #newcrafts Image
How to facilitate refactoring using compassion to…
@ClareSudbery #newcrafts ImageImage
« Thinking takes time. » @ClareSudbery at #newcrafts

Couldn’t agree more. Reason why I always refer to the « sustainable pace » of eXtreme Programming with my colleagues and also ask them:

Can't you find your best ideas like me by walking or taking a shower? 😄 Image
Many more much smaller steps.

@GeePawHill quoted here by @ClareSudbery at #newcrafts Image
The wheel of confusion. Everyone has blind spots or favorite topics. Let’s share this all together in order to get more confident in our refactoring. ImageImageImageImage
“Seeking joy” while refactoring by @ClareSudbery

A really important topic for me too. 😍

I use to challenge myself & colleagues with: let’s try to make every work day worth living by achieving baby steps, improving things, learning stuffs and seeking joy.

#newcrafts ImageImageImage
To conclude @ClareSudbery at #newcrafts ImageImage

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with use case driven

use case driven Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @tpierrain

use case driven Profile picture
May 26, 2023
Look who’s here! #newcrafts Image
Coupling and cohesion for the first time were defined in this book. #newcrafts ImageImage
“Software design is an exercice of human relationship” was written
Read 15 tweets
use case driven Profile picture
May 26, 2023
Nick Tune now on stage #newcrafts Image
@TeamTopologies was filling some dots im 2019. #newcrafts ImageImage
Multiple heuristics to identify the subdomains. #newcrafts #DDDesign ImageImage
Read 15 tweets
use case driven Profile picture
May 25, 2023
The maintenance mode problem. @SteveSmith_Tech #newcrafts ImageImageImage
Solution #1 the delivery teams #newcrafts

“If you name your app with greek gods, beattles, or…. You and I won’t be friends” 😄 ImageImage
In a nutshell, delivery teams solution. #newcrafts ImageImage
Read 9 tweets
use case driven Profile picture
May 25, 2023
“Finding efficient solutions to practical problems” @davefarley77 at #newcrafts ImageImageImage
Optimize for learning #newcrafts ImageImageImage
Managing complexity @davefarley77 at #newcrafts ImageImage
Read 7 tweets
use case driven Profile picture
Jul 10, 2022
#CQRS is not a general purpose style of architecture.

A thread ⬇️
The first time I built a CQRS system… it was in 2006. The term hadn’t be coined yet by Greg (that happened in 2010), but the practice was ubiquitous in finance with tons of high throughput platforms to build or to maintain.
Actually, the first time I’ve used this architecture style was not due to my young skills of tech architect, but rather on a technical constraint.
Read 32 tweets
use case driven Profile picture
Apr 30, 2022
Him: last time you were saying that you wanted us to avoid using feature branches. Why? 🔽

Me: I was saying that if you want to move toward Continuous Delivery on that specific software, you’d better aim trunk based development.
H: ok but what you don’t like with branches?

M: Despite what people here are saying, they are very often long-lived. They last more than a day, more than a couple of days. Sometimes a week… When no merge conflict is detected at the end it’s ok.
Bad things happen when there is a merge conflict at the end of the day.

H: Yes, but is it that much painful? Aren’t branches our bread n butter?
Read 33 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

Send Email!

:(