Software Architecture in Unity

[@Tarodev]

Beautiful scene, interesting code visuals, funny memes and _solid_ information. Well done Jason, it's about time you released a damn video!

[@Betruet]

Not to mention a powerful cameo

[@kingbling7571]

Solid I see whtchy did there

[@waltermunozguaman7591]

I have the same opinion, awesome video!

[@Unity3dCollege]

Awesome video

[@SojoTaku]

Sir, why aren't you verified?

[@Hazzel31337]

i am so glad you made him make a channel, such a good video

[@accountdua9375]

Love you man...

[@Ahatcho21]

I Hope you learnt something.

[@abdullah4653]

another amazing master is here@@Ahatcho21

[@iHeartGameDev]

As always, you introduce me to new concepts that I wish I knew more about! Awesome work and explanation, Jason! Keep the vids coming ✨

[@0ptixs]

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 KZbin 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

[@turkeyjerkey]

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).

[@handleneeds3charactersormore]

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

[@Rev3rence]

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.

[@Alexander_Grant]

@@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.

[@dawidblum8461]

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!

[@BigRookDigital]

Okay, we get it... you're good at what we need to get better at. More videos, thanks!

[@toastyshrimp1882]

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.

[@amitmoryosef2223]

relatable af

[@Bardent]

Don't focus on the lines of code, focus on the decision making behind it. Love it!

[@okanerkan1873]

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.

[@Tvtig]

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.

[@kevonboxill9455]

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!

[@alaslipknot]

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 ?

[@strawhenge5007]

Good video. You aren't done when your code works, you are done when your code is right.

[@beatenbykarma]

Excellent video, love the way you demonstrated how change happens on projects

[@CallousCoder]

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.

[@0ptixs]

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

[@dinkle9664]

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."

[@CallousCoder]

@@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!

[@pixeldevlog]

This is one of the most useful videos on the internet. Following exactly this solves soo many problems.

[@DoomCatcher]

Really useful video I just wish it was longer with even more examples, please make more videos expanding on this topic.

[@joshreylearning8253]

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!

[@CornCamp]

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!

[@crazyfox55]

This is the best tutorial on this subject. The distinct separation of the architectural changes from the feature changes was very insightful.

[@saltyspacenerd5581]

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!

[@acryinshame]

thank you, i have struggled understanding the 'why' behind it and you described it easily in 7 mins.

[@Passenger-vf8pp]

Thanks for the video! I have been working quite a while on improving the workflow of code development and teamwork. This video definitely helps!

[@Nihilp]

precious stuff here! mindchanging ! i'm rewriting all my code with this philosophy and i'm happy with it! thx!!!!

[@markcooke4866]

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.

[@wvaviator3408]

Excellent advice and example

[@Pdude2k9]

Great video, it's more rare to find videos about this topic than just another language feature. Keep up the good work!

[@kayumiy]

It is absolutely phenomenal explanation of SOLID and Software Architecture. You did well. Thank you.

[@GlennThomasJr]

Your page is amazing! I scour for these higher level thinking concepts!

[@kevinrobertandrews]

I appreciate how thoughtfully worded you made this tutorial. Thanks for sharing!

[@redenvalerio601]

Please continue this kind of contents!! I love it! Thank you!

[@biobear01]

Please do more of these! Great info and made me realize I need a lot more architecture training!

[@biobear01]

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?

[@henryh7140]

This practical example really helped! Great video, thank you :)

[@marche4ever]

i'm intrigued by the way you structure your scene, it would be interesting to see a video on how you set it up and the reasons behind it.

[@AlexBlackfrost]

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.

[@hernandonj]

Clarification absolutely needed. Thank you so much.

[@GordonArber]

I love the editing in this one Jason! Well produced! Also awesome content!

[@kanz0bgz]

Great stuff, really loving these videos. Looking forward to the next one.

[@VitegO4]

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!

[@dann5295]

Memes and edits are kinda distracting, to be honest. But your videos are always very informative! ty

[@ElBARTO298]

dude . you are the best. i love the passion you put into you editing and the learning experience is just on another level.

[@wilmirosa7076]

Your content is fantastic because is clear and concise. Glad to be your follower Jason,

[@jtmcfarland3512]

Great video, but I with it was longer. There are tons of resources for how to do single things in Unity with C#, but I’m struggling to understand how and when to implement them. Nobody seems to ever start the video explaining WHY you would do a certain thing. This discussion on architecture was a great start. I’d love to see the architecture of a developed game. What’s in their hierarchy? How are their files organized? How often and when are different principals used (state machines, statics and singletons, event systems, and other patterns). Great work. Keep it up.

[@nickygdev]

Incredibly informative as always

[@aktchungrabanio6467]

Absolutely beautiful solutions Jason. Thank you for these tips. You are a gem

[@teknofis2604]

Your videos are just .. Wow! Pls keep'em coming

[@willnmari5998]

wow that was eye opening! especially the Log() method - thanks!

[@goehlergamedev]

Hey Jason. I just want to really thank you for pointing me towards Uncle Bob. I've now been listening to him for 8 hours - and the stuff he preaches is SO important and valuable. This will change my way of coding for ever! Thank you. :)

[@maple7rees-352]

Subbed. Thank you for being so insightful and straightforward.

[@roydrinkwater]

I need more videos like this one. Very effective examples and to the point!

[@mongrelgaming1473]

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.

[@Juanborgesv-]

Great video Jason! Can't wait to see more 👏

[@jordanfischer3693]

Great video, love how you use simple understandable examples.

[@jirushi3028]

It's getting better and better

[@fulongfromthegrave]

I felt like all that needed to be said! Looking forward to the next one :)

[@hotroddd1]

This is a great simple video on how to take the "white paper" ideas and turn them into real world examples. Thank you.

[@MohammadFaizanKhanJ]

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.

[@asliniarayanadam]

Great content man, your points made me better in such a short time.

[@BallisticLife]

This is a very well crafted video!! Perfect example, and the concepts are explained very clearly. Something this video highlights, without acknowledging it, is that the architecture of a project has to change and be redefined as the needs of the project change. Deciding which aspects of your code are changeable involves anticipating future design changes, which can be a tricky and sometimes harmful task. By its nature, writing code is the act of creating explicit structure that limits changes in some areas and allows it in others. As such, it's counterproductive to set out creating a program that will be changeable in every area. Of course this isnt to say you shouldn't anticipate future changes. Just that it's important to make sure you're doing so intentionally. There isn't a one size fits all "best way to start a unity coding project so that you wont have to do lots of refactoring in the future". Internalizing that took me a while when I started out.

[@BallisticLife]

To be clear, I don't expect this stuff to be discussed in this video. This is out of scope for the target audience and length of the video.

[@OldM8]

I am a completed noob with C# and playing with Unity and this made awesome perfect sense ! I think I need to read a few more books on fundamental principles like this video explained :) thank you my dude.

[@gliasmarinho]

Thanks for the video, very supportive!

[@nasrodev2087]

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

[@waltermunozguaman7591]

Awesome video!, so much quality

[@vasilevsanyok]

Short and sweet :) waiting for more new videos! thanks

[@MTweedC4]

The skype call was *genius!* Would love to see more people be brave and craft some unusual audio design! Thank you :)

[@omnicatalyst]

This was a fantastic explanation

[@_stephenhubbard]

sheesh how am I just discovering this channel?! Dat quality

[@bednyakovv]

Amazing editing and content. Thanks a lot, Jason!

[@philberex]

Damn glad i found this video in the KZbin archives.

[@Korgolord]

Okay, we get it... you're good at what we need to get better at.

[@albertmontagutcasero2129]

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.

[@Gastrostomi]

Was actually looking for some interesting videos about Addressables, but the title was teasing be about other interesting topics I have thought about before. So I think I will stick around for a while.

[@hergggoor]

Great work with this video! Simple and easy to understand

[@frederickfreund1957]

Really good informative video. Thank you!

[@trickstapriestxm]

Been wanting software architecture/organization in a unity context for years!

[@larryd9577]

A proper logger can adjust its loglevel. So if you added a lot of debug logs, you can set it to a higher level (e.g. info) then it will not write debug logs. But info, warn or error logs

[@ragerungames]

Good to see video featuring Tarodev!!!

[@keelanbowker-obrien2222]

This was so helpful for me, thank you so much.

[@gerardcuello4576]

Really nice video! Clear abd simple yet powerful!

[@astrosoap]

Great video Jason, just looking at your uploads and it seems you've stopped. Would love to see more of your stuff

[@mrstruijk]

Excellent information man!

[@synchaoz]

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.

[@jeffwang2216]

這麽棒的影片我居然才看到……非常有用的思路。Thank you for sharing

[@modelworkzseo]

Jason, you are absolutely brilliant. PLEASE consider making long form refactoring videos like you used to at Infallible Code; your insights are so helpful.

[@rashidfarhan6223]

Brooo all of my favorite unity content creators are here in the comments. This is some next level stuff here.

[@gmunay420]

i want to say something nice but im terrible with words, I really like this.

[@4HandsGames]

Very well explained with easy to understand examples!

[@BatonyRobson]

Very important video and perfect example👍

[@SoaringSimulator]

Thx 4 your time, bro. Awesome explanation. As Jason pointed out, do not look at the code. In particular, if you try to extend with a function that triggers Debug.Log, when there is a message in the console and double-click it, it will not take you to the message but to the function. So it is not helpful, and there isn't a way around that. We love your channel!

[@KjipGamer]

Amazing video. One thing to note whilst doing this : You can *easily* go to far in this.

[@Kapendev]

Great video and your intro is really good. I might copy the "Focus on the design." bit for my videos lol.

[@chrisrabe]

Great video. SOLID is definitely a great principle to follow when developing code (at least just the first two, the last three are more catered towards object oriented style languages with the use of interfaces and abstractions).

[@Belliger1991]

You forgot that functional programming basicly starts at the "open for extension, closed for modification" philosophie ^^ So basicly (if you ignore the three basic rules in the video) all you do is simple basic scripting but not realy programming (as in you think of the future change consequences) ;)

[@chrisrabe]

He only mentioned the first two principles in the video though?

[@grazeen]

You are making great videos please make more! With every video i see problems differently and think the future in mind.

[@TheKr0ckeR]

I feel like i found a legendary item that i want for years while watching this video.

[@pixelart0124]

2:33 "I just gave you change!" OMG that killed me LOL

[@nanaschi]

Agree with everything except Logger being monobehavior. Good stuff 👍

[@Betruet]

My guy TaroDev! Great content thanks!

[@Ironlionm4n]

Amazing video thank you for uploading

[@KDSBestGameDev]

You got a great point with change. The solid principles for example also make it possible to unit test your code and also make bug searching less painful. If you have certain classes with specific responsibilities than searching a bug is way easier. More important if there is a slight risk that you created a bug and another team member has to fix it (vacation whatever). With e.g. single responsibility in place, the new team member should be able to narrow the possible buggy classes down significantly. TL;DR Great Video Ty!