refactorkit @RefactorKit

Make better refactoring decisions. A workflow engine for #software teams to make consistent, predictable & successful code health decisions. By @sovilon_studios refactorkit.com Toronto, Ontario Joined February 2019

Tweets

116
Followers

23
Following

58
Likes

78

Scott Wlaschin @ScottWlaschin

5 years ago

Excellent post by @einarwh. "Software development is largely a communication problem. Developers should provide expertise not just in programming but also in the externalization of mental models to facilitate communication and collaborative modelling" einarwh.wordpress.com/2020/05/19/int…

1 20 64 0 9

refactorkit @RefactorKit

6 years ago

There are just so many metaphorical bridges between tech debt, code health and pandemics. “There is no glory in prevention.” Let’s change that.

0 0 0 0 0

refactorkit @RefactorKit

6 years ago

How often do code reviews fail to persuade and educate? Code review is containment in a pandemic metaphor. It works well to prevent outbreaks of tech debt. Refactoring is mitigation. But to explain how this works needs simulation / modeling tools for code health.

osdnk @mosdnk

6 years ago

2 3 21 0 1

0 1 1 0 0

refactorkit @RefactorKit

6 years ago

This #coronavirus has me thinking about models. Models are key for making decisions. Does your software team use a model to measure code health? Reply with the model you use.

0 1 0 0 0

Peter Zakin @pzakin

6 years ago

My articulation of this is that enterprise software is process manifest as product.

Balaji @balajis

6 years ago

My articulation of this is that enterprise software is process manifest as product.

8 47 291 0 25

2 17 184 0 27

refactorkit @RefactorKit

6 years ago

Using our app means you’re installing an idea into your dev culture - the idea that code quality decisions should be consistent, predictable and non-contentious.

Balaji @balajis

6 years ago

Using our app means you’re installing an idea into your dev culture - the idea that code quality decisions should be consistent, predictable and non-contentious.

8 47 291 0 25

0 0 3 0 0

refactorkit @RefactorKit

6 years ago

When devs tell you “we need to rebuild from scratch” for “too much tech debt” You should point them to refactoring decision records that outline: - rationale - context - decision Written culture = 🔑

Patrick McKenzie @patio11

6 years ago

7 163 610 0 65

0 0 0 0 0

Robert Graham @ErrataRob

6 years ago

Infosec is full of bad analogies. The absolute worse is "technical debt". People think it's a good analogy for communicating with "business types", but it isn't, because techies don't understand "debt". Techies think debt is bad, business types think debt is good.

35 169 534 0 33

myconull @myconull

6 years ago

@kentcdodds @rajington @codescene I’ve been studying technical debt for my side project @RefactorKit and @codescene is one of the most impressive projects I’ve heard about. More developers should know about it.

0 3 3 0 1

I Am Devloper @iamdevloper

6 years ago

for halloween, I'm coming as the technical debt ticket you've shoved in the backlog for the past 6 months

42 962 4K 0 24

Alex Makhaev @mankms

6 years ago

Empathy is a Technical Skill, @andreagoulet Over the past decade, I’ve been amazed at how an empathy-focused approach to software development can help pay down technical debt and contribute to the overall health of a software system. infoq.com/articles/empat…