Warning
I ran this through Chatgpt to spell check for me because I am lazy. Let me know if a link doesnt work or something is wierd.
To my own dismay, I don't have much publicly facing code of that I am particularly proud of, and the private code I have is private because I am too embarrassed to show it publicly. I'll work on this.
Most of the code I've written is in a Monorepo somewhere in Star Atlas Space. The examples below don't represent my everyday work. Most of my day to day work included more boring stuff like. I have a private repo atm of some web code but I don't want to make that public, but for an idea it is a Turborepo where I am experimenting with Solidjs and some other CSS libraries. I am also using Railway.app to deploy some code, and will eventually run some kind of crank that does something idk.
A couple of things I find interesting.
I love bots and have found packages like playwright and puppeteer insanely powerful. These were some of the first implementations I made a couple of years ago that log into services and perform actions. There is an entire engineering discipline to be discovered in botting and scraping. This talk is a huge inspiration and provides a bit of an idea of how creative botting can be another tool in the tradesmen's chest.
A Tinder bot that would drop a pickup line after a match would occur.
Note
You can probably find my music selection from that script. So long as SoundCloud is free, I will use it as my main source of music, that and YouTube.
In my mind, game devs are crazy and the breadth of knowledge to make a game is crazier. Solid game devs should be paid more. After being laid off from Star Atlas, I dipped my feet into Godot and found a lot of transferable knowledge from my web dev experience. Attempting to make something... **anything really** in Godot was eye-opening.
Note
Referencing Melancholia II. The solid could represent a couple of things, but I like the idea that it was Durer's attempt at creating a perfect form or a Quintessence. Durer is possibly admitting the futility, and eventual despair, in chasing perfection.
The code below shows a sequence something like this sequence.
- NPC fires a weapon
- Weapon shoots a bullet (potential for different bullet types exist) and attaches the NPC ID to the bullet along
- Bullet collides with the Hitbox of the NPC.
- NPC registers the Bullet Damage type and performs
take_damage()method
- if the target NPC dies, the target NPC runs something like
sender.killed_target(me)
- Bullet collides with a wall and stands still for 1 second and explodes
- That explosion collision box collides with the NPC collision boxes and registers a Blast Damage type.
The entire repo is chaos, and at the moment I like it like that. I will show you how to run the code on a call if you'd like. For reference, I took A LOT of code from this repo. It's written in CPP, but I used chat GPT to help me understand what was going on. HEAVY HEAVY HEAVY influence comes from this. Source SDK
- Also, the Damage Source File has the links to a lot of referenced code in the Source SDK
Note
In watching some Half-Life retrospectives and post-mortems, I learned that the Gravity Gun in Half-Life 2 was originally a debugging tool. Eventually, the Gravity Tool became fun to use, and the devs decided to give the player the tool, and the game of the year was born. In fact, at the same time Valve was working on Half-Life's physics engine, Id Software AT THE SAME TIME had their own physics debugging tool and opted against giving it to the player for fear it would "make the player too powerful." I take that entire history as a huge lesson. Good tools can make or break a product, so I keep my eyes out and ask myself often "Can I make a tool for that?".
I think this is the video for the Half Life Retrospective I am talking about
- Go to 52:18
Here's some other things I find interesting. Will add more in time.
I am more of a compiler than an inventor at this stage of my career but aim to evolve in the coming years to be a well-rounded inventor of new things.