Sounds fun! Working on small projects is the best way to learn.
These fantasy consoles, and we’ll the concept of them at all, is quite facinating.
So i’m doing a Snake game in JS for a class project and, well, i mean JS is strange but that’s not really the point here. The thing i like about this is that with these projects is how little we have to work with. Teacher doesn’t want us using any sort of API so i really have to build the most basic things (spent some hours trying to build my own time delta calculations to enable timed game updates til i figured out setInterval was a thing, i do want to go back to the delta thing tho), like, we have to figure out how game logic works, the “check state/handle outliers/update logic and objects/draw” rhythm and how it should be set up. It’s such a cool challenge. Literally no one else in the class is as excited as me tho >_> project group included it seems, but they’re not so comfortable as i am so i’m trying to just build the most essential things and leave the code easy enough to read and handle that they can actually build on top of it with ease.
I don’t know what it is about code but it puts my mind in such a a state of work that nothing else really does. It’s like a lie, like the code you build is a fantasy that makes you feel life is somehow ordered and loggable to console.
Sounds like you have the programming bug. When I’ve tried to make games in the past, I always enjoyed working on the lower level things, creating the tools to make the game than the game itself.
Now I’m tempted to write my own game engine.
Oh wow just noticed the need to commit ever change is kind of like the obsession to reload after every shot
I generally commit complete features, classes or functions. The most important part is to never commit code that will break other parts of the project. That doesn’t mean that they have to be large. Today I fixed a bug with two words of code.
We’ve been deploying plenty this week. But I am working through the holidays so whatever.
That rings very true.
Having worked at two large companies, one more traditionally enterprise at this point and another that is large enough but is still transitioning into “enterprise” I’ve faced all of those issues to varying degrees.
You can put it simply as, which is harder to start moving: A pebble or a boulder? Enterprises are harder to get projects and changes going and on the flip side, harder to stop momentum. The less people involved with any change means it is that much easier to make that change.