This is what video game programming was like in the 1970's - 1980's For example, I wrote games on the VIC-20, I had 8-bit 6502 running at 1 MHz processors with a few K of memory, I had to fit the graphics, logic, sound effects into 3.5K memory I didn't have the stuff we have today of superfast processors, gigs of space, soundcards, graphics resolutions, GPU's, etc... So when you were talking about this idea of bit-packing it brings back fond memories of those days and compared to these days we're spoiled with these nice tools and they are great, but also what you said about generating a lot of data, especially if you wanted to have different instances of them... it's good to remind people that there's simpler solutions. To think if you take the economies of the storage and algorithms with today's modern hardware it would scream! However, as technology scaled, so did our requirements and expectations... those small, simple, 8-bit games won't cut it for a modern gamer... retro gamers maybe... but I think this points speaks to a larger picture of as technology scales so do the technical challenges... yesterday's problems have be largely handled and to talk about "back in the day I had a 1MHZ 3.5K blah blah blah" is no longer relatable to people, they roll their eyes and say "whatever... did you have modern electricity or did you use horse and buggy?" LOL I had to hand assemble my 6502 in HESMON... I know... people don't care how we solved problems back then because they aren't going to encounter it today! Well of course not, the challenges today are different, problems are still hard, Challenges will continue to increase and the technology, problems get harder and scale. Like I'm sure you relate, try getting a modern game up and running from scratch... there's quite a learning curve as it was in my day (No Internet, book stores, needed to "TALK" to people... OMG... LOL but it was fun) P.S. I find it interesting how things come full Circle!

Oh man, I have to tell you, I would have never become the über programmer that I am today, were it not for my ultra super duper programmer mouse. I dunno man, it's just the way you click with it, the clicks feel so crisp and precise. Without, I could have never been so creative and productive. Everyone who wants to become a programmer, I recommend getting the best mouse they can get. 😁👍🏻

Great video, there aren't enough framework thinking tutorials out there, probably because the assumption is the SWE audience already has a certain aptitude to problem solve. An epiphany I've had recently ties in well with your method of binary thinking and this is; 1. First principles (exactly what you said break down a problem to an atomic level, 0s and 1s even) 2. Then use these ideas and facts to think in Sets (literally applying unions and intersections to make decisions) and use the outcomes as ballpark ideas for decision making eg conditions, program flows, states etc. I am not an analytical person but I have found working like this help me solve problems even beyond code.

This led me to solve a 5 year problem I was facing in only 2 days. You changed how I will think about coding forever. Just yesterday I wrote 748 lines of code naturally, today I realized a better way to do it in 138 lines and now it just works. This should be taught in schools. THANK YOU!!!!

Your videos are always so informative and well-presented. Thank you for sharing your knowledge with us!🚀😎

I'm really excited about this series! Always wondered how you get off the ground and working with application programming. Lot's of great information in this video too!!

this was definitely insightful, I figured I did some of it on an intuitive level

thanks!

You have be careful with this advice. Sure, with 4 bits you can do movement but for what type of game? If I want to solo make game as cleanly and fast as possible, say a 2D platformer with a complex movement system that depends on a lot on the environment, I *should* create objects and use components instead of 64 bits. They will allow easier management and scale, all while being extremely flexible. For me, the important thing is not losing sight of the big picture, making money.

R Studio or bust!

What does Dinesh think about this