Is Clean Code Important for My Go Project? | The Imperfect Project 1/3
The ability to write good code is crucial for any programmer. However, this idea often overlooks a crucial question: does the project really need it right now?
It turns out that's not always the case, and sometimes it can even get in the way: when you're trying to create an MVP, test a new library, or simply need to get results quickly. But it's not as bad as it seems.
Code is a tool that solves a problem. And I understand that the concept of "dirty code" can be overlooked by the client for a long time, and it can snowball. It happens. And that's why you're in this story—a professional who will analyze the task and understand the goal.
So, in my story, I'm the client and my Imperfect Project. My goal is to finish it as quickly as possible and show you my compromises. But most importantly, if you're watching this video, it means the project is finished, and you'll see the rest.
In this video, I'll talk about the project's concept, show what's already there, and write a plan for the next video, which will be released tomorrow!
The GitHub link will appear in the third video.
🔹 VyacheArt on Telegram https://t.me/VyacheArt
🔸 Support on Boosty https://boosty.to/vyacheart
#ityoutubersru #ityoutubers
00:00 Introduction
01:01 Concept
01:56 What's already there?
03:17 Plan for the next video