“𝗝𝘂𝘀𝘁 𝗸𝗲𝗲𝗽 𝗰𝗼𝗱𝗶𝗻𝗴… 𝘄𝗲 𝗰𝗮𝗻 𝗳𝗶𝘅 𝗶𝘁 𝗹𝗮𝘁𝗲𝗿.” Every developer has said this at least once. 😅 At the beginning, it feels productive: Ship fast. Move forward. Don’t overthink. But later comes… the refactoring. the bugs. the “what was I even doing here?” moments. Because code is like this wall: If the foundation is messy, fixing it later becomes… painful. Move fast, yes. But don’t forget to build clean. Because “later” always comes. 👀 #Programming #CleanCode #DeveloperLife #TechDebt #SoftwareEngineering
Moving fast, quick proto and fixing later are not words you will ever hear from Senior devs. This particular slang usually comes with a studio culture commanded by producers, executives and alike supporting it, later that same people rushing to it, will recoil to the most vulnerable and restart another cycle firing people. In theory executives and CEO shouldn't have those problems anymore with the AI slop
Or keep coding, We can layoff you later and give him the ownership of the chaos you left :), The CEO will not notice
does it work? yes. is that visible after plastering? no. So everything is ok.
That is why learning system design is important
I read that in construction the higgledy piggledy mess above is less prone to cracking apparently
It's a perfect fit for small projects
Got new motivation for coding
Later may not come today it may not come tomorrow but it will come eventually listen to this message and don't let your code become a wall take your time write it right and remember the tortoise didn't win the race by just rushing he took his time like all dev's should now that isn't to say you should go as slow as you can but don't speed to fast the more problems your code could cause tomorrow means the more time you need in the future instead find the right steady pace. slow and steady may win the race but steady is the right pace