Jason Gorman’s Post

I'm not in the business of selling code craft (believe it or not). I prefer to focus on helping those who're already sold on it make these technical practices work for them. But if you *want* to sell TDD, refactoring, CI, separation of concerns, CD etc, here's my tip: What appeals to business stakeholders is getting their hands on working software *sooner*. Sooner's a big deal. Not bugs. Not maintainability. Not "professionalism". How soon can we give them that change they asked for? All the roads of code craft lead to "shippable at any time"

Refactoring is a crucial step in maintaining code quality, improving performance, and ensuring scalability. 1. Identify the Problem Areas: Start by pinpointing inefficient, duplicated, or complex code segments.  2. Set Clear Goals: Define what you want to achieve with the refactor. 3.Start with Small Changes: Begin by refactoring small sections at a time, such as renaming variables, breaking down large functions... 4.Maintain Code Readability Prioritize code readability. should make the code easier to understand. 5. Optimize Performance: Look for opportunities to optimize performance. 6.Test Continuously: Continuously run and test each change to ensure that everything works. 7.Document Changes: Make sure to document significant changes.

𝐈𝐧 𝐲𝐨𝐮𝐫 𝐂𝐨𝐝𝐞 , 𝐰𝐡𝐚𝐭 𝐢𝐬 𝐚 "𝐂𝐨𝐠𝐧𝐢𝐭𝐢𝐯𝐞 𝐂𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐲" ✔ it is a measure of how difficult a unit of code is to intuitively understand. ✔it tells you how difficult your code will be to read and understand. before you deploy your code , make sure to take care of this. Your code should be easy to read and understand and eventually would be easy to change. I take care of this - break your long function to small understandable, reusable & meaningful functions. Do you?

Is no-code enough for your business? Discover why leading industries still rely on custom code development for complex projects. Learn more about the limitations of no-code and why custom coding often provides the flexibility and scalability needed for success. https://ow.ly/yayn50TwQEs #nocode #customcode #customdevelopment

"Refactor half of the codebase in one go." is awful approach. That's how you: - Do a bunch of changes all over the code - Introduce new bugs in the process - Get discouraged - Feel anxious - Never refactor again Instead, make a plan: 1. Take the next task you'll work on. 2. See if there are tests covering the code. 3. If not, write the tests. 4. Improve the code as you make changes. 5. Write the tests for the new code. Refactoring should take 5 minutes. Not 5 months.

[𝗖𝗹𝗲𝗮𝗻 𝗖𝗼𝗱𝗲] 𝗘𝗺𝗲𝗿𝗴𝗲𝗻𝗰𝗲 Rules for writing clean code are simple, and there are just a few of them. However, simple doesn't mean easy. What is difficult is repeatedly doing simple things, writing tests, and refactoring. Actually, you have to take time for this and deeply recognize that doing this kind of work doesn't mean stagnating but preparing for advancing better and faster. 𝗧𝗼𝗱𝗮𝘆'𝘀 𝗳𝗼𝗰𝘂𝘀: 𝗘𝗺𝗲𝗿𝗴𝗲𝗻𝗰𝗲. ----- You are not ready for deployment if your code is not clean. Clean code means maintainable. Maintainable means survival and growth. 

What matters: 1. Business Value. 2. Throughput. 3. Code Quality. In that order. Quality is 3rd only because it matters only if it’s missing. High quality code with no business value is pointless. High throughput with no business value is pointless. How many of you have seen an org focus on Throughput, while the product side and development side of the organization barely talk to each other?

#software #refactor #technique #code 💡 What is Refactoring? 💡 When Should you Refactor? Refactoring is not : ⛔ Rewrite some classes or components that change the external behaviors. Refactoring is : ✅ a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. When : ✅ Duplication ✅ Nonorthogonal design ✅ Outdated knowledge ✅ Performance ✅ The tests pass 💡Before begin refactoring make sure you have solid and enough tests about business and what do you want in result. 💡After each small refactoring run tests as often as possible.

Refactoring is not something you can do at any time, any scale! Most people look at the “Refactoring” as a magic button. It is as easy as pushing it, any time he wants. Miss the point that refactoring needs planning from the start, when you decide to add technical debt for any reason. Planning for refactoring means getting prepared to change software at a minimum cost. The essential point, in my opinion, is making room for it by making boundaries and abstractions. so it is possible to change the codebase without the avalanche effect, which you force to refactor a large part of the codebase because of dependencies between them. Otherwise, although you call it a “Refactor”, it will cost as much as rewriting the code, maybe even more! #softwaredesign

Can be refactored != Should be refactored I should have added a disclaimer that some may get heated that not all code should be refactored. Let's chat about what might motivate us to refactor code: - Difficult to understand - Hard to make changes in - Very brittle when we do make changes - Little to no test coverage, and difficulty adding any - Cannot extend the code to perform any other functionality If code could benefit from refactoring, why might you opt to leave it as is? 👇Check out the comments for the link to the article!👇 ---- 📨 Sign up for my email newsletter! 🗣️ Share with your network! #refactoring