refactorkit
@RefactorKit
Make better refactoring decisions. A workflow engine for #software teams to make consistent, predictable & successful code health decisions. By @sovilon_studios
You might like
Human language is tech for learning and understanding. Metaphors are language tech. “Tech debt” is just a metaphor that describe a state of code idealism. It’s used for learning and understanding.
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…
There are just so many metaphorical bridges between tech debt, code health and pandemics. “There is no glory in prevention.” Let’s change that.
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.
IMO the worst code review is to explicitly say "shouldn't do X" or "must be Y". Unless it's something obvious, we need to be conscious that human on the other side is not a moron. Even you might be right, the point is to convince an alternative solution, not prove your genius
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.
2 vote · Final results
My articulation of this is that enterprise software is process manifest as product.
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.
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 = 🔑
In addition to assisting remote workers, a commitment to a written culture helps quickly moving organizations by making sure that people execute on decisions made even if they were not yet hired when the decision was made.
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.
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.
for halloween, I'm coming as the technical debt ticket you've shoved in the backlog for the past 6 months
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…
United States Trends
- 1. #WWERaw 75.8K posts
- 2. Packers 50.7K posts
- 3. Packers 50.7K posts
- 4. Jordan Love 6,994 posts
- 5. John Cena 72.6K posts
- 6. Jalen 16.9K posts
- 7. #GoPackGo 5,343 posts
- 8. #RawOnNetflix 1,901 posts
- 9. Kevin Patullo N/A
- 10. Grand Slam Champion 22.1K posts
- 11. Desmond Bane 1,315 posts
- 12. Lane Johnson 1,144 posts
- 13. Matt LaFleur 1,395 posts
- 14. #MondayNightFootball 1,122 posts
- 15. Green Bay 12.1K posts
- 16. Cam Whitmore 1,411 posts
- 17. Jenkins 2,596 posts
- 18. Nikki Bella 1,285 posts
- 19. Jaelan Phillips 1,411 posts
- 20. #PHIvsGB 1,342 posts
Something went wrong.
Something went wrong.