Software Architecture in Unity
ฝัง
- เผยแพร่เมื่อ 25 มิ.ย. 2024
- Ever wondered what software architecture is REALLY about? Why do we bother?
---
If you would like to support me, feel free to donate to:
www.ko-fi.com/jasonstorey
(and get access to my discord)
----------
00:00 - Introduction
00:06 - Software Architecture Misconceptions
00:17 - Practical Example: Sample Script
00:41 - Software Architecture and Making Code Work
01:06 - Change Requests and the Importance of Change
01:31 - Adding a Feature: Toggling Messages
01:52 - Design Decision and Impact on Future Changes
02:19 - Alternate Version of the Script
03:00 - Controlling Logs from Multiple Classes
03:25 - Separate Loggers and No Code Changes
04:51 - Understanding the SOLID Principles
05:04 - Single Responsibility Principle
05:50 - Open-Closed Principle
06:49 - Conclusion - แนวปฏิบัติและการใช้ชีวิต
Awesome video
Sir, why aren't you verified?
i am so glad you made him make a channel, such a good video
Love you man...
I Hope you learnt something.
another amazing master is here@@ahatcho138
Beautiful scene, interesting code visuals, funny memes and _solid_ information. Well done Jason, it's about time you released a damn video!
Not to mention a powerful cameo
Solid I see whtchy did there
I have the same opinion, awesome video!
As always, you introduce me to new concepts that I wish I knew more about! Awesome work and explanation, Jason! Keep the vids coming ✨
I love that you're publishing intermediate content in the context of Unity. There is very little such content available, and most YTers seem to avoid it (doesn't get the views or likes they want).
insert *shallow, overly optimistic, obnoxiously narrated video on simple functionality designed to get the views of noob users and send them in a downward spiral of pain the more unity they learn* video here
The thing is, these concepts are fairly simple and basic when you come to game development from software development. The issue is people assume the 2 can be mutually exclusive. In reality, you can't and shouldn't attempt to make a game without having proper engineering skills OR good engineers to support you. It gets worse, because working with an engine is inherently limitting. You are bound by the rules and whims of the engine and your software architecture is limitted due to that. It requires even more practical experience and theoretical knowledge to find the best practices in the specific context you are thrown into.
@@Rev3rence I recently found a community that has a bunch of hobbyists making games and put myself out there to join some games in progress, and the projects I've looked at that are already partly through are full of code that reads like tutorial code. Some of them are big enough that I have no idea how the project even starts up. I had to tell a couple of teams that their project wasn't right for me because unpacking that code or trying to add features to it was brutal. It is crazy how much actually learning computer science changes the way you think about this kind of stuff.
Just started their video and wanted to comment on the "don't focus on the lines of code, focus on the decision making behind it" absolutely love it, that is what I've been missing from all these TH-cam tutorials, I could care less about what actual code I should enter, I can figure that out with documentation, but the actual logic and decision making behind developing is what I need the most help with. Think I'm going to enjoy a lot of your videos
Okay, we get it... you're good at what we need to get better at.
More videos, thanks!
I love the presentation, easy to understand examples, great narration and that every video provides a goal to achieve on your own that improves your overall skillset and knowledge. Can't wait for more videos! Keep up the great work Jason!
cant remember commenting but watch this video 3 times.. these last two were just because you did it so well...kudos to you my bro!
This is the best tutorial on this subject. The distinct separation of the architectural changes from the feature changes was very insightful.
Don't focus on the lines of code, focus on the decision making behind it. Love it!
I appreciate how thoughtfully worded you made this tutorial. Thanks for sharing!
With so many moving parts in a project, it is so easy to miss the forest for the trees. This is a very nice video. I look forward to seeing more from you in the future!
I love the editing in this one Jason! Well produced! Also awesome content!
I love the simplicity of your example and how you explain not just what to do, but why it's a good practice.
Looking at the rest of the code, I could also see pulling out the code to compute the HitInfo from the mouse position as a separate concern.
This is one of the most useful videos on the internet. Following exactly this solves soo many problems.
Thanks again Jason, You are a great teacher. I am looking forward to more videos as your channel grows. Ill be sure to keep watching them. So valuable!
Great video, love how you use simple understandable examples.
I know it takes a lot of effort but please keep making more videos, it's hard to find mid or above level stuff with good explanation. Thanks.
Amazing content!
Jason and Tarodev are by far my favorite game dev channels now, short, accurate, and straight to the point!
Jason can you cover dependency injection in the future please ?
I really appreciate this video, I had read over the solid principles a few months ago and mostly didn't understand them, but this video made them much more clear to me. Thank you!
Your videos are just .. Wow! Pls keep'em coming
Great stuff, really loving these videos. Looking forward to the next one.
I need more videos like this one. Very effective examples and to the point!
Amazing editing and content. Thanks a lot, Jason!
dude . you are the best. i love the passion you put into you editing and the learning experience is just on another level.
Clarification absolutely needed. Thank you so much.
Incredibly informative as always
Please continue this kind of contents!! I love it! Thank you!
Your content is fantastic because is clear and concise. Glad to be your follower Jason,
Great video Jason! Can't wait to see more 👏
Awesome video!, so much quality
It is absolutely phenomenal explanation of SOLID and Software Architecture. You did well. Thank you.
I felt like all that needed to be said!
Looking forward to the next one :)
Your page is amazing! I scour for these higher level thinking concepts!
precious stuff here! mindchanging ! i'm rewriting all my code with this philosophy and i'm happy with it! thx!!!!
wow that was eye opening! especially the Log() method - thanks!
It's getting better and better
Subbed. Thank you for being so insightful and straightforward.
Thanks for the video! I have been working quite a while on improving the workflow of code development and teamwork. This video definitely helps!
Really good informative video. Thank you!
This was a fantastic explanation
This might be the greatest software design and architecture resource I've come across in my 10 years of software development. I wish every new developer knew about it and studied what you are saying in detail.
Great work with this video! Simple and easy to understand
Absolutely beautiful solutions Jason. Thank you for these tips. You are a gem
Great content man, your points made me better in such a short time.
Great video, it's more rare to find videos about this topic than just another language feature. Keep up the good work!
Really nice video! Clear abd simple yet powerful!
Really useful video I just wish it was longer with even more examples, please make more videos expanding on this topic.
This practical example really helped! Great video, thank you :)
Excellent information man!
Excellent advice and example
Very well explained with easy to understand examples!
Please do more of these! Great info and made me realize I need a lot more architecture training!
Going more in depth on solid is probably a great start for more video topics. Each principle could surely use its own explanation and unity example?
thank you, i have struggled understanding the 'why' behind it and you described it easily in 7 mins.
Short and sweet :) waiting for more new videos! thanks
SuperObjectiveLookInside(the)Development. Let me throw a bunch of flowers onto the starship board where you stand to deliver us such practical and entertaining content.
Good video.
You aren't done when your code works, you are done when your code is right.
Thank you for the information you put out, being only a couple months into this new hobby your voice is one I listen to a great deal (as are a fair few of the other commentators here which I find interesting.)
Also I think the new skills in video editing are noticable.
Thank you, Jason! Great video
Memes and edits are kinda distracting, to be honest.
But your videos are always very informative! ty
Very important video and perfect example👍
Amazing video thank you for uploading
This was so helpful for me, thank you so much.
這麽棒的影片我居然才看到……非常有用的思路。Thank you for sharing
Great explanations! Thanks
My guy TaroDev! Great content thanks!
Solid explanation! :)
You are making great videos please make more! With every video i see problems differently and think the future in mind.
Good to see video featuring Tarodev!!!
Great video, using console logs as an example was a great idea, it's something even beginners can understand. Looking forward to seeing "Unity is too slow part 2" 👀! Also, loved the colabs.
This is a great simple video on how to take the "white paper" ideas and turn them into real world examples. Thank you.
Great example thanks!
Oh man, I’ve been teaching this for ages! And it seems that the younger the developers become the less they know and understand the use of software architecture. Your examples here were well chosen; simple quick and understandable. I think I will use the logging example from now on too. It’s easy to relate too.
There’s a saying: “any problem in CS can be somber by an extra layer of abstraction”.
And that’s true, but it’s walking a fine line with over abstraction and under abstraction. I try to teach developers, to initially don’t worry too much with abstraction unless it’s obvious (like logging, configuration and M/V/C etc). But as soon as you see you start to duplicate, take the time then and there to refactor. Because now it’s still easy and has little impact.
But it just doesn’t sink in to the minds of the 25/35 year olds in most cases.
They haven’t developed on low level languages (assembly and C) where this sort of duplication makes it impossible to maintain.
Man I just started trying to make games/learn to code (I know it's a trope at this point) but wow I have a long ways to go to understand all of what you wrote, excited for the journey though
I think that programming used to be a passion and is now just another career path. Some people want to just "get the job done."
@@dinkle9664 I think you may have a good point here. All those channels that “help” people land their 6 figure salary. So it’s probably more about the salary and the job than actually being an engineer and loving the job. I think you may be right!
great presentation!
Great video man
Thanks man. Right at point.
Oh, this is a brilliant level of content!
And my words are not just for being loud. As experienced in web, i've been looking for videos that would help me to switch into gamedev. Well, I found that in terms of basic principles and architecture the most of videos are weak. But, in opposite, this video is completely coherence with fundamentals that I rely on. At first - no afraid of "additional code and abstractions". At second, it says about code for game not talking about game itself, but exactly about architecture. So, I'm excited to keep watching the channel!
i want to say something nice but im terrible with words, I really like this.
really interesting! Thanks!
Yay Jason is making videos now! woooooooo! subbed :D
Great content!
Okay, we get it... you're good at what we need to get better at.
Good video well explained and concise :)
Well said, keep it up!
Nice video, I want more 👀
Well very done video, both in terms of content and presentation. Thanks for sharing and putting in the effort. And tegridy. Thanks for not forgetting the tegridy.
Loved it!
I've watched this video 3 different times, each time coming back to this more senior and able to understand more.
I remember somehow watching this and feeling overwhelmed at how "complicated" this was, and I feel good knowing how much I've grown as a developer that this video seems basically like common sense now.
Awesome Jason, thank you for this kind of videos. You are so unique. Also, to point something about Single Responsibility Principle, Robert Martin also says -A module should be responsible to one, and only one, actor-. So, if some behavior of your application is used by two different actors, you should keep it separate to avoid defects. Your example is perfect, I would love more examples using different point of views.
Great video !!!
i had a big brain Unlocking process while watching this video Really made me rethink how to handle things entirely not just Debuggin thankss a lot
Brooo all of my favorite unity content creators are here in the comments. This is some next level stuff here.
I love you Jason!
sheesh how am I just discovering this channel?! Dat quality
Damn glad i found this video in the TH-cam archives.
This is a great Video and thank you so much for explaining the topic. I'll have to keep this in mind going forward. But your logger made me curious, too - I'll give that a try, too :)
This video pops in my recommendation and I watched it the second time completely. Good work Jason! SOLID death seems very funny to me. even the S of the SOLID has much impact on the overall of your coding architecture decsion.
Thanks for your honest review not like others trying make my life more diffuuucxxlt !
Short and sharp as sword🗡️
Thanks Jason!
Well explained man!