Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta
16 posts

Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi

a piece of deep wisdom from @twominutepapers which can be abstracted to life in general. good things can take time and as long as you're trying & trending in the right direction you'll come out the other side ✌️users.cg.tuwien.ac.at/zsolnai/gfx/ph…

English
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi

@dmokafa Code without tests (A.K.A legacy code) is not designed to write tests after, so we must break its dependencies first. There are lots of strategies to do so with a minimal impact and risk
Michael Feathers refers to that as the "legacy code algorithm"
twitter.com/_rodrigomd/sta…
Rodrigo@_rodrigomd
The legacy code algorithm 🧩 1⃣ Identify change points 2⃣ Find test points 3⃣ Break dependencies 4⃣ Write tests 5⃣ Make changes and refactor - excerpt from "Working with legacy code, Michael C. Feathers" Use it whenever you need to make a change on a legacy code
English
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi
Kriztoper Urmeneta retweetledi

A more scientific way to read Twitter that shows only paper links posted or retweeted by people you follow: twitter.com/search?s=follo… (Modify as necessary if you care about different journals than I do.)
English












