PokeVideoPlayer v23.9-app.js-020924_
0143ab93_videojs8_1563605 licensed under gpl3-or-later
ImmersiveAmbientModecolor: #bdaba3 (color 2)
Video Format : (720p) openh264 ( https://github.com/cisco/openh264) mp4a.40.2 | 44100Hz
Audio Format: 140 ( High )
PokeEncryptID: 54f460f82f5fa3d01bca8b11aa7e2029fc69b61624c8f431525188c1c8d7b3f0e4d12b57fc10081c3f9012c4bc6732fb
Proxy : cal1.iv.ggtyler.dev - refresh the page to change the proxy location
Date : 1732637018843 - unknown on Apple WebKit
Mystery text : ejBXX0VKNGFhTFkgaSAgbG92ICB1IGNhbDEuaXYuZ2d0eWxlci5kZXY=
143 : true
13,822 Views โข Oct 17, 2024 โข Click to toggle off description
Views : 13,822
Genre: Science & Technology
Uploaded At Oct 17, 2024 ^^
warning: returnyoutubedislikes may not be accurate, this is just an estiment ehe :3
Rating : 4.876 (21/658 LTDR)
96.91% of the users lieked the video!!
3.09% of the users dislieked the video!!
User score: 95.36- Overwhelmingly Positive
RYD date created : 2024-11-12T21:46:07.683461Z
See in json
40 Comments
Top Comments of this video!! :3
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.
14 |
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 ๐ช
6 |
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
2 |
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.
1 |
Use Android Modern Android Development (MAD) Arch because all the tools build on it ...
2 |
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.
2 |
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.
|
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
1 |
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 ;)
1 |
I think you forgot that you just dropped a course on clean architecture ๐
3 |
Great take ๐๐
|
Thank you good sir.
|
Then which architecture is better then clean architecture? MVVM ??
|
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
|
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
|
DRY KISS!!
|
Love dev bloggers with 10 YOE criticizing someone with 50 YOE, who is world wide recognized and proved it through successful giant projects
|
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.
|
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.
1 |
@imb-alan-ced
1 month ago
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.
15 |