What you need to know before you jump into refactoring code...
Read more here:
https://www.devleader.ca/2023/11/28/what-does-refactoring-code-mean-what-new-developers-need-to-know/
What you need to know before you jump into refactoring code...
Read more here:
https://www.devleader.ca/2023/11/28/what-does-refactoring-code-mean-what-new-developers-need-to-know/
Why should we even bother with refactoring?
Read more here:
https://www.devleader.ca/2023/11/21/what-is-refactoring-and-understanding-why-you-need-it/
Here's a list of 10 different refactoring techniques for you to leverage!
Read more here:
https://www.devleader.ca/2023/11/14/top-10-refactoring-techniques-you-need-to-transform-your-codebase/
Sockpuppet: Blog: elasticStage update https://sockpuppet.band/blog/1085-elasticStage-update #Distribution #Transitions #Refactor #Vinyl #Blog
protip never let anything distract you for 2 weeks in the middle of a precarious #refactor
Refactoring can work wonders for simplifying code
Read more here:
https://www.devleader.ca/2023/12/04/how-to-simplify-your-code-with-effective-code-refactoring/
There comes a time in every developer's life where we're faced with this...
Read more here:
https://www.devleader.ca/2023/11/27/refactoring-legacy-code-what-you-need-to-be-effective/
Why bother with the Sisyphean task of migrating from Prettier and ESLint to #BiomeJS when you can just use a 🪓 to #refactor your entire codebase? It's like trading your bicycle for a tricycle and expecting to win the Tour de France. 🚴♂️💨
https://blog.appsignal.com/2025/05/07/migrating-a-javascript-project-from-prettier-and-eslint-to-biomejs.html #SisypheanTask #Codebase #DeveloperHumor #CodingChallenges #HackerNews #ngated
How do you know when to rewrite it all instead of refactor?
Read more here:
https://www.devleader.ca/2023/11/26/rewriting-vs-refactoring-code-how-to-navigate-the-two/
When should we refactor code?
Read more here:
https://www.devleader.ca/2023/11/24/when-to-refactor-code-how-to-maximize-efficiency-and-minimizing-tech-debt/
Ah, yes, the riveting tale of how a "noop" refactor—a coder's favorite oxymoron—somehow tanked #performance by 30% ⏬. But fear not, brave souls; our hero embarks on a treacherous journey into the mystical land of #Golang #memory allocations 🧙♂️, determined to unfurl the secrets of the heap while we all pretend to care. 🤷♂️
https://www.dolthub.com/blog/2025-04-18-optimizing-heap-allocations/ #noop #refactor #allocation #coding #humor #HackerNews #ngated
Level up your refactoring with these 9 articles!
Refactoring is a critical skill in software engineering. Here are some articles to help you level up:
https://www.devleader.ca/category/software-engineering/refactoring/
Refactoring Techniques:
https://www.devleader.ca/2023/11/14/top-10-refactoring-techniques-you-need-to-transform-your-codebase/
Remove Control Flags:
https://www.devleader.ca/2023/11/19/remove-control-flag-refactoring-how-to-simplify-logic/
What & Why For Refactoring:
https://www.devleader.ca/2023/11/21/what-is-refactoring-and-understanding-why-you-need-it/
When to Refactor:
https://www.devleader.ca/2023/11/24/when-to-refactor-code-how-to-maximize-efficiency-and-minimizing-tech-debt/
https://www.devleader.ca/2023/12/27/when-should-code-be-refactored-what-you-need-to-know/
Rewrite vs Refactor:
https://www.devleader.ca/2023/11/26/rewriting-vs-refactoring-code-how-to-navigate-the-two/
Legacy Code:
https://www.devleader.ca/2023/11/27/refactoring-legacy-code-what-you-need-to-be-effective/
What is Refactoring:
https://www.devleader.ca/2023/11/28/what-does-refactoring-code-mean-what-new-developers-need-to-know/
Simplified Refactoring:
https://www.devleader.ca/2023/12/04/how-to-simplify-your-code-with-effective-code-refactoring/
Testing With Legacy Code:
https://www.devleader.ca/2023/12/20/dealing-with-legacy-code-how-to-make-anything-more-testable/
I'm also happy to announce that I have an awesome course on all things refactoring, which you can check out here:
https://dometrain.com/course/from-zero-to-hero-refactoring-for-csharp-developers/
You'll learn a host of refactoring techniques with real code examples to walk through. Understand how to approach refactoring and when you may want to consider a rewrite!
----
📨 Sign up for my email newsletter!
🗣️ Share with your network!
I refactored the [[Bookcase]] in my wiki … it might be a good topic for a video tutorial someday.
Instead of loading in different stored lists as a way of filtering the content, I now have one list that is filtered dynamically that both list (text) views and cover (image) views adhere to, making for neat on-the-fly re-arranging of the same list, and much more optimized.
#tiddlywiki #wiki #personalwiki #books #reading #code #lists #archivist #refactor
Sockpuppet: Blog: Vinyl releases https://sockpuppet.band/blog/1031-Vinyl-releases #Distribution #Transitions #Refactor #Vinyl #Blog
I compiled useful refactoring techniques into this 5 hour course to help you improve your ability to refactor.
Check it out:
https://dometrain.com/course/from-zero-to-hero-refactoring-for-csharp-developers?affcode=1115529_nl-teyzg
I compiled useful refactoring techniques into a course that guides you through different ways to refactor with code examples.
Check it out:
https://dometrain.com/course/from-zero-to-hero-refactoring-for-csharp-developers?affcode=1115529_nl-teyzg
more ughhhh. been trying to #refactor the code which renders all this stuff for *ages*
i want it as free-standing single-purpose functions, so i can test each one of them more easily
however, i keep running into my reluctance to write code of the sort:
```
fn foo <'a, A, B, C, D> (a: A, b: B, c: C, d: D) -> impl Content + use<'a, A, B, C, D> where A: impl Content, B: impl (Fn()->A) + Send + Sync, C: impl Content, D: impl (Fn()->C)+Send+Sync { ...```
This might be the most obvious of #linktuesday links in ages, but really, I've recently been helped a lot by #rector. So yes, I'm sharing Rector today: https://getrector.com
If you have not worked with it before, it may seem intimidating, but take some time to get used to it, because it can really make your life a lot easier, especially when working with #legacy code
Because I am
- #agile -y only writing #code that I need immediately
- writing research #software where I don't really know what I want until I see it running
- dumb
I often find I get 90% of the way to somewhere useful and realize I need to #refactor large swaths to get the last 10%.
I missed an abstraction layer. Or rather, I deliberately omitted it because I was "more like DISTRACTION LAYER" at the time. But now I need that layer.
It seems overwhelming, but I have a major #engineer #mentalhealth tool: #git
If it turns into a tar pit, I can just revert.
I compiled useful refactoring techniques into this 5 hour course to help you improve your ability to refactor.
Check it out:
https://dometrain.com/course/from-zero-to-hero-refactoring-for-csharp-developers?affcode=1115529_nl-teyzg