Why 'Clean Code' Likely Makes Your Code Worse

#programming #coding #mobiledevelopment #androiddevelopment #android #kotlin #androidstudio

[imb-alan-ced]

Glad you added the caveat of working on enterprise software. The problem is, most large enterprise software has legacy architecture that could use a "cleaner" architecture to make scaling easier. Simple is good for smaller personal apps, but once it starts to get into a larger codebase maintained by multiple devs, ANY standardization of architecture is better than none.

[yuripiano]

Problem is that many "senior" developers have no idea of what clean architecture is, and many companies are dealing with incredibly messy code. So yes, keep it simple if coding is a hobby, study software architecture if you want to be a real programmer

[VlastimirRadojevic]

As an iOS tech lead, I try to explain to my coworkers that Clean Code is not a dogma that needs to be applied with the same examples that some people propagate. Being as simple as possible (KISS) is good for every developer who joins an existing project because it will take them less time to jump in, not break something easily, and start contributing to the project.

Really simple, thanks Philipp 💪

[javiere.gonzalez]

Let's not jump on the "clean code is bad" bandwagon. Bad engineers writing bad code is bad. Implementing architecture correctly requires experience and understanding what not to use. KISS is hardly useful by itself. Everyone has their own idea of simple.

[arielapp]

even in an Enterprise app we don't always strictly adhere to clean architecture, sometimes the requirements leads us to other paths, but the base is the same.

[SiamakAshrafi]

Use Android Modern Android Development (MAD) Arch because all the tools build on it ...

[centauri]

Keep It Simple, Stupid principle alone is quite vague. SOLID principle might’ve made more sense or the concept of coupling and cohesion, wherein all major principles revolve around.

[manuelsalas]

Please give some KISS examples! I always create my projects with data, domain and presentation layers (CLEAN) lot of abstractions and to make a single screen with an API request I have to create lots of files and mappers

[melon]

Yes, for personal projects this may apply, but if You work with at least few devs then everyone will have it own 'simple stupid' perception what when mixed in longer term may just end up with 'stupid' - that is hard to maintain and devlope codebase. Some rules, maybe not full blown clean code + solid + X patters, but some of them, helps to maintain project in 'tidy shape' for a longer time. Imo everything boils down to amount - every cure in large enough amount becomes toxic. but it does not mean that You should not take medicines at all ;)

[OGdoCavaco]

Absolute programming. My company enterprise software uses all this mess, and the final code is harder to follow than the Linux source code! And my company are two apps with some user dialogs. I think enterprise software are in its lowest quality in decades

[PaulMichaelReilly]

Terrible take! All apps start out small. No app worth it's salt stays small. So start clean and keep it clean. Small methods, small files, simple design, solid principles, *DD are just a few of the aspects of clean code that apply to apps with one module to apps with thousands of modules.

[AimanYosofi]

Most people forgot about the simple and start writeing stupid code
So I think clean code put a standards for just know how stupid your code is

[hoeric]

Then which architecture is better then clean architecture? MVVM ??

[alexkhutornyi]

Love dev bloggers with 10 YOE criticizing someone with 50 YOE, who is world wide recognized and proved it through successful giant projects

[nicoloagnoletti]

Is it possible to consider clean architecture what is actually is for once and stop thinking that it is only what you've seen in the biggest app project you've worked on?
Clean architecture works on both small and big projects, it can be done minimizing abstraction, and it keeps everything simple and isolated for the ones afraid of it.
If you think it's cumbersome and clunky, either you don't understand what architecture is about or you're to lazy to get into good software practices

[vukkumsp]

Start with a simple monolithic working code and based on requirements upgrade it with time. A consistent improvement does better job than a single one time complicated work.

[CatzHoek]

Start he video with the premise "Here's why clean code will likely make your code worse:" and never actually adressing it, leaving people to read between the lines. Sry, typical mornic baity short form content.

[pradam]

and then the project changes over time and then youre fucked with whta you started with lols

[youNeverThoughtAboutIt]

promote Kiss, make the world a better place