No, I haven't asked anyone to upvote or comment. It was posted 2-3 days ago, there were no upvotes. And I was feeling concerned. (I am doing this full time and getting on top of HN for my own work was a dream). I had written articles on bevy and also posted on HN (in last 6 months). But they hardly got any traction on HN.
Not sure what happened today, I saw traffic from HN and was surprised to see this on #8.
I also noticed few comments looked LLM generated (they got deleted), but I am not sure why someone would do it, I mean the incentive.
Most Rust resources dump theory first. This book flips that: Fun First, Rust Second. You start by moving characters, then add procedural world generation, particle effects, A* pathfinding, and combat systems as you progress.
You master ECS architecture and Rust fundamentals by creating a complete game, not reading theory.
Chapters 1-7 are available for free online:
Chapter 1: Let There Be a Player: Setting up a Bevy project, understanding ECS basics, and implementing player movement.
Chapter 2: Let There Be a World: Creating procedural tilemaps and world generation.
Chapter 3: Let The Data Flow: Building a data-driven character system using RON configuration files and generic animation logic.
Chapter 4: Let There Be Collisions: Implementing spatial queries and collision detection.
Chapter 5: Let There Be Pickups: Building an inventory system, UI, and understanding the borrow checker through practical game patterns.
Chapter 6: Let There Be Particles: Adding visual polish and particle effects to bring the game world to life.
Chapter 7: Let There Be Enemies: Implementing enemy AI behavior and A* pathfinding.
If you are looking for someone to tinker around with your developer product and come up with innovative possibilities and use cases and communicate them, I would love to work with you. (Part time preferred)
I have been in the SaaS space for the last 12 years (B2B SaaS - 6 years). Though I am an engineer at heart, I have worked on building different departments at Tars(HelloTars) for the past (5 years, 11 months), building the engineering team, building the design team (2 years), leading partnership efforts (1 year), and also building the marketing team (1 year). Presently, I have been tinkering around with novel approaches in Reasoning AI (built on top of the LLM layer) and have a different take on the approach than how most folks are building it.
I would love to share learnings and understand your priority problems even if you are not interested in immediate hiring.