NOTE This is a work in progress. Demo links on here depend a lot on your system and video card. But give them a go - you’ll know if they work. I’ve finished some of the key features of my little 3d engine. The list includes Basic Levels, sprites, sounds, and basic interactions between objects. Enough features to build a small game - which, arguably, is the hardest part.
Anyone who knows me knows I wont shut up about this “game engine thing” I am working on. I admit it, I’ve been a bit obsessed. The reason I am obsessed, I think, is because I get to solve problems that I’ve never really had to solve before. This weekend, for example, I need to make some sort of grid system (or binary space partition) to limit the number of objects I am tossing around in the engine - this kind of stuff never comes up in day to day life!
NOTE Demo links on here depend a lot on your system and video card. For example, Firefox 60 on my desktop doesn’t work, but on my laptop it does. Chrome works on my desktop, but not my laptop. And Safari, well, yeah. But give them a go - you’ll know if they work. I’ve been obsessed for the past few days trying to get my little 3d game engine closer to useful.
Web Components are the future… at least that’s what this news letter I read said. I like the promise of web components. They basically, seem to me, to be Angular 5 / React like functionality built into standard HTML. They give you the ability to create new tags for HTML that do super special things. I’ve been wanting a way to publish and share some basic .ics (ICalendar) files on my running / triathlon site.
If you’ve ever worked on a project where you’ve tried to share code between two (or more) projects, you probably understand the pain. Sadly, I’ve worked on a few. Admittedly, on the surface it seems like a tempting proposition. On paper, it sounds quite easy. For example, one system I worked on we had a single nuget library where we kept our domain objects. The logic went: “All you have to do when you want to make a change is update the domain object project, build, push the new library to the nuget server, then pull down the new library to the other projects, and then rebuild those.
I am a big fan of using CI / CD. As most software engineers are. That’s not a very controversial stance. For open source projects there are some really nice services out there. One such service is Travis CI. I really like their service for open source projects, but I have a few side projects that I don’t want to open source. My side projects are not for monetary gain so there is no revenue from them.
I’ve been playing with writing my own Typescript / WebGL 3d game engine from scratch and fumbling about with machine learning (which oddly have a lot in common). The hobby has led me to studying linear algebra, which has got me looking at lots of problems in a different light. I blame a lot of my recent thinking on the YouTube Channel 3 Brown 1 Blue. The author of that channel lays out maths in a very visual way - it is much to my liking.
When building or designing software, I love to draw diagrams. I find the old adage “a picture is worth one thousand words” to be spot on. I also find that the diagrams are the most useful when they are right next to the source code. Having to drudge though a wiki or search though a separate documents folder to find the diagram that refers to the code I am looking at seems like a waste of time.