Ask HN: What Are You Working On? (Nov 2025)

Polishing my dashboard for tracking profit on Solana blockchain for set of wallets: https://imgur.com/813aQsO

I want to extend it with a simple overview of most recent profitable wallets to look for new "metas" that i could profit on. This project may or may not end as open source eventually, but i currently keep it private.

A visual editor for creating video games on the browser and on Linux desktop: https://stickyfingies.github.io/g2ngine

I've done this with C++ in the past, but ran into substantial friction with the CMake toolchain, specifically w.r.t:

- cross-platform compilation with large dependencies (vcpkg ports)

- running multiple compiler chains in the same build step

That second point is necessary if, for example, there's some AOT asset processing work that uses a native tool, and you're building for web. Expressing that some targets should use the emscripten toolchain while others should use the native toolchain, and interleaving between them, was a mess. TBF, I haven't done that with cargo or build.rs yet and it may prove to be equally frustrating.

Other features:

- undo/redo using a stack of swappable states

- serialization to disk (native) and LocalStorage (web) with some integration tests in progress but I am not satisfied with the correctness of my implementation: I want to *guarantee* that all information is preserved round-trip, but I also want a Patek watch.

- OBJ, GLTF, GLB models are loaded as "blueprint scenes" which are distinct from the "world scene." I made this distinction at the type-level because "scenes" are groups of entities that use newtype IDs (`LightId(u64)`, `MeshId(u64)` etc.) as primary and foreign keys to refer to each other, and I wanted to make it impossible for an entity in scene A to hold an ID for an entity in scene B. Instantiating a blueprint requires creating new IDs for every object.

- W.I.P. Alpha rendering, depth sorting, overhauling the material system to support multiple shaders (tough) that may be compiled after the engine itself (even tougher, a lot of runtime dynamic state and schema validation stuff), physics, scripting - oh yeah!

- Scripting using JS on both web (runs in browser itself) and desktop (uses a packaged JS runtime `Boa`) but Boa doesn't perform well on desktop in debug mode so I'm exploring other options.

I’m working on a games website called https://minigames.world It’s really low budget, but the idea might be interesting to you. It’s a Laravel app that’s solely interactable through a TUI application, so Claude Code can help me operate it. To support my decision-making, I analyze collected data with Jupyter notebooks. I’ve been working on this since early October 2025.

I’ve been working on an idea wishpool.

https://anyidea.fun

Anyone can post an idea for something they wish existed — an app, a game, a tool, or anything else — and share it. When more people back an idea, it gains momentum and starts getting built, either by AI or by community makers. The goal is to turn crowd energy into real progress.

I’ve gone old school. After reviewing a few people’s CV’s the easiest format was for me to record a video with the feedback, so I put a site together for that:

https://resume.fail/

No AI, you just buy my time.

I’m also looking to do a couple freebies if anyone wants to anonymise their CV and let me use it for a promo example.