@JustkickinitG
I work in a codebase with 3 million lines of spaghetti code. Any consistent architecture or design patterns would have been better than what we.
@piyushagarwal7628
I 100% agree on it. Sometime too much functions and abstraction make things impossible to understand .
@javiere.gonzalez1021
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.
@arielapp9469
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.
@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 💪
@9rrr7
lol, I have worked in Google, Amazon and VMware, if you think it is how enterprise code looks like then you will get a heart attack the first time you see an actual enterprise code😂
@yuripiano5179
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
@centauri07
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.
@SiamakAshrafi
Use Android Modern Android Development (MAD) Arch because all the tools build on it ...
@manuelsalas6190
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
@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.
@martinseal1987
Great take 👏👏👏
@karolkulbaka8577
DRY KISS!!
@youNeverThoughtAboutIt
promote Kiss, make the world a better place
@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
@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
@electrobunnyful
Thankyou!
@melon5544
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 ;)
@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.
@imb-alan-ced