Here's WHY You Struggle With Software Architecture!
Вставка
- Опубліковано 31 тра 2024
- Software architecture seems to be a very complex topic. My mentoring and technical interviewing experiences showed me at least that software architecture is a topic a lot of people struggle with. In the end, software architecture is not simple, but it's also not rocket science. So, why do people struggle then? Well, in my opinion it's because the content we consume around this topic has at least 3 major defects. In this video I'll go through what I think that those problems are and also offer you solutions and actionable items that you can start doing now. I assure you, if you take them seriously, you will end you struggles with software architecture
#software #softwarearchitecture #softwaredeveloper #softwareengineer
Join this channel to get source code access and other perks:
/ @codewrinkles
Also follow me here:
✅Blog: codewrinkles.com/
✅Facebook: / danpatrascutech
✅Instagram: / danpatrascutech
✅TikTok: / danpatrascutech
✅Newsletter: codewrinkles.eo.page/newsletter
Content
1. Intro: 00:00
2. Why Is Software Architecture hard? 01:15
3. Spaghetti content: 02:58
4. Opposing what's not opposable: 07:54
5. Critical thinking: 13:18 - Наука та технологія
Damn, you totally nailed this video. Mad respect.
Thanks. Glad you appreciate it.
@@Codewrinkles it made me self reflect hard. I have to thank you.
My man, you are on point
Hahaha😀 Nick Chapsas Police Department Series
Humbled and encouraged by your honesty and ability to connect with, at least, this video content consumer. It drives me bonkers when I'm looking for content on a new-to-me SD concept, or new tooling, and I have to disentangle it from the buzzWordBroth the concept is drowning in.
Keep it coming!
Thank you very much for your feedback. I appreciate it a lot!
perfect !
Thanks a lot Mr.Dan for your video
I have caching service called "CacheService" and application setting call "EnableCaching", where I should check EnableCaching setting if it's enabled or not to cache the result, inside the CacheService or inside the handler?
It depends. Sorry couldn't resist....
Why would you want to not enable caching? Caching should be used where you have a performance issue. If that performance issue requires a caching solution to address it, then under what circumstance would you turn it off? To answer your question though the caching service should read the caching configuration, nothing else should know nor care.
Thank you for your useful material! What also I can add.. There are piles of trash even within recommended open-source projects which makes things a lot complicated than that if you are trying to find good examples for problems you are trying to solve. Within TOP 10 .NET projects I found 8 of them totally useless as a good learning examples. Those are over complicated or oversimplified. Often omitting usual production use cases etc. Eg it is not a problem to teach about the repository pattern on simple flat example, but what about nested stuff or database without cascade behavior etc? Also coding is an ART actually, there are almost unlimited number of ways of doing something - some are better some are worse and some are crap. Keep going, keep practicing. You find yourself slowly evolving, rewriting your old code, changing decisions etc. There is no other way to grow. Practice makes perfect. And I know - sometimes it is painful or costly, but the worst thing is to sit on your ass and do nothing or wait indeterminately for something which never came.
And some might let you think even "Hello world" should be implemented in clean architecture.
How many buzz words contest! Hah!! Thank you!
Glad you enjoyed it
It's especially overwhelming for beginners, CQRS, events, ddd, clean architecture, dry, kiss.. Too many designs and principles..
Totally agree!
Correct, too many buzzword and jargon. Event, event source, domain, cqrs, mediator, etc, what the heck is even that. Need to breakdown one by one before consuming those content that mention all those buzzwords in their videos.
Yep, breaking it down one by one is the best way to learn in the initial phases of learning. That will give you a solid foundation on which you can then build further. Otherwise, you just build a house of cards that will be blown away by the first tiny wind.
I totally agree with you that those "buzzwords" are dangerous for beginners, but when you reach a certain level of knowledge is easier to use them to be perfectly understood by your fellow colleagues.
Or Dirt architecture.