I must confess, @ben , that as a more experienced programmer, there were several steps along the way to this lecture where I was saying to myself “Why would we do it this way?” and “Wait, I was sure this guy knew good architecture”… so I was just about screaming at my tablet when I got to this video where you, too, had a confession that… you set us up for this… That’s my confession… I almost threw my very expensive 10" Galaxy Tab S2 at the wall.
Especially since before we got to this video, you’d hinted where we wanted to get our architecture to, and I decided to give it a go (and owing to understanding coding well, but not entirely familiar with the Unreal architecture (the reason I’m taking this course is not to learn C++, but to learn the Unreal architecture), I did a pretty good job at mucking it up.
Of course, I was also thinking… what about those blokes who are pretty new to programming altogether who are probably hitting their heads against the wall in frustration in triplicate…
Then I finished watching the video, and you’re absolutely right. This sort of reengineering of one’s architecture is a vital skill, and it’s something that every programmer will have to know when (and I mean when, NOT if) they find their architecture in spaghettiville. Looking forward to seeing your refactor method, and hopefully where I tripped up in the Unreal architecture.
Loving the course, so far, by the way. I still haven’t decided if Unreal will be my new environment of choice, but I’m starting to feel more comfortable with it.