Refactoring

1. Analyze codebase using
   Ranked Recursive Summarization

2. Identify weak points and group related code segments (
   High Cohesion)

3. Distribute refactoring tasks among team members with clear interface (
   Low Coupling)

4. Begin by addressing dependencies, data models, and configuration

5. Implement code generation to meet regulatory requirements

• Expose problems explicitly

• Don't negate the previous system

• Ask for opinions and thoughts

Rewrite total things are dangerous

You can't stop the business, or why rewrites fail | Swizec Teller

Rewriting code isn't a magic fix-all. Consider the opportunity cost, complexity of the old system, and estimation challenges. Instead of stopping all to rewrite or building new while maintaining the old, try incremental improvements and new code adoption.

https://swizec.com/blog/you-can-t-stop-the-business-or-why-rewrites-fail/

[2020-11-11] 5년차 개발자

나에게 5년차라는 개발 연차는 조금 특별하다. 첫 회사에서 내가 속한 조직에는 시니어 개발자가 없었다. 내가 입사했을 때 1년 정도 차이가 나는 선배개발자가 한분 있었고, 입사한 후 6개월 텀으로 1~2명 정도의 신입 개발자들만 채워졌다. 당시에 동료들과 나는 5년차 개발자에 관해 이야기를 많이 했다. 회사에 5년차 정도의 개발자 한분만 오셨으면 좋겠다고 매일 이야기했다.

https://blog.kingbbode.com/51

The Alternative Implementation Problem

In this post, I want to talk about a dynamic that I’ve seen play itself over and over again in the software world. In fact, I would venture a guess that this kind of situation probably happen…

https://pointersgonewild.com/2024/04/20/the-alternative-implementation-problem/