[flagged]
Ask HN: What are you working on? (June 2026)
341–350 of 1001 posts
Re: Ask HN: What are you working on? (June 2026)
#342Tmux control-mode client for Emacs
https://github.com/csheaff/tmux-control
I found myself ditching Emacs for iTerm when running TUIs inside tmux on remote hosts. I'm trying to replicate how good tmux is inside iTerm, but it's tough. wip.
Re: Ask HN: What are you working on? (June 2026)
#343A json schemaless stream querying engine that would run several sql queries over the same kafka consumer (not a consumer for each query).
Re: Ask HN: What are you working on? (June 2026)
#344I've been working on a CLI that converts performance profiles to human and LLM friendly Markdown:
https://github.com/TomerAberbach/profiler-md
Currently working on a diffing feature to compare before vs after profiles.
It also comes with a skill to have a coding agent profile and optimize your code!
Re: Ask HN: What are you working on? (June 2026)
#345I’m getting back into it again after a long break due to burnout. I’m still burned out but it’s getting easier to think through problems.
I’m building a home server. This was something I put off for years due to some perfectionism. Eventually I just threw together something with old hardware and headless Ubuntu. Much to my surprise, the power draw is only about $4 a month. I can live with that so no need for specialized hardware.
I’m doing the common -arr stack using docker compose. I’m using plex because the jellyfin doesn’t work as well on an Apple TV.
Having a server running is nice. I can set up some stuff on a whim. Most recently was the Mealie recipe manager. It’s great knowing my data won’t be paywalled. I’m using syncthing as a simple backup method between my devices - everything but media of course. It’s fine if I lose media.
An unexpected benefit of having the server is that it inspires my wife. She decided to give vibe coding a try. She’s an artist, not an engineer, but with a little help she was able to make a task tracker for us. She tailored it to the way we tackle our tasks and, again, it’s really nice knowing it won’t get paywalled in the future.
I’m still burned out, but having a server to tinker with is helping.
Re: Ask HN: What are you working on? (June 2026)
#346Filing an 'actually useful' defensive patent suite, finalizing investor-facing demos, and raising for autonomous manufacturing of a 100% autonomous food distribution play (the cooking direct from fresh ingredients, packaging, cutlery provisioning, and optional drone delivery all require zero humans) https://infinite-food.com/ (capital welcome, 100x expected)
Re: Ask HN: What are you working on? (June 2026)
#347Working on my programming language. Goal is to perfect the interpreter's code embedding mechanism. I'm adding adding features to the language until it can self-host an ELF patcher, then I'll rewrite the ELF patcher I wrote in C in my language with a lot of enhancements.
I'm also hardening my development virtual machine system. Properly firewalling it so that it can reach WAN but not the host or the LAN.
Re: Ask HN: What are you working on? (June 2026)
#348[flagged]
Re: Ask HN: What are you working on? (June 2026)
#349Just a few little things to help me.
World Cup schedule with no spoilers. Where you can save the teams you follow and make cal events for upcoming matches.
https://worldcup26-schedule.pages.dev/
A tech events listing page for New Zealand. Where approved organisers can freely post upcoming events and people can subscribe to hear of new events.
Re: Ask HN: What are you working on? (June 2026)
#350An API documentation generator for Laravel apps: https://github.com/Radiergummi/laravel-openapi
In contrast to most other libraries in this space, it knows about Laravel conventions and its ecosystem, and tries to infer as much as possible without explicit annotations, using type hints and doc comments and static analysis. Where automatic inference isn't possible, you can use targeted attributes to annotate your route handlers.
The result is written as an OpenAPI specification, and (by default) served using a Scalar playground.
We also include a linter command that checks whether all API routes are documented properly, typed correctly, and following your style - this also supports dirty files only, reporting coverage in standard formats, and even automatically fixing some classes of errors!
I've also written tooling to regularly test the library against a set of open source Laravel applications with a published OpenAPI spec. This has proven very solid in detecting improvements and regressions, so much so that I can delegate new features to an AI agent and rest confident that it can verify on its own whether a change breaks anything.