I'm working on a new app for creating technical diagrams - https://vexlio.com . It's an area with some heavyweight incumbents (e.g. Visio, Lucid) but I think there's good opportunity here to differentiate in simplicity and overall experience. I'm still in the fairly early phase, and I suspect I haven't quite found the best match of features to customers yet. From a dev perspective this area has a ton of super interes…
Ask HN: What Are You Working On? (June 2025)
811–820 of 1001 posts
Re: Ask HN: What Are You Working On? (June 2025)
#812Re: Ask HN: What Are You Working On? (June 2025)
#813https://spring-agriculture.com/ Autonomous robotics for sustainable agriculture. Based in the south of the UK. Prototypes of an autonomous mechanical farm-scale weeding robot currently beginning real-world testing. Still a huge amount of work to do though. Hardware and software developed fairly much from scratch, not using ROS (for not entirely crazy reasons...); everything written in Rust which I find well suited to…
I have seen a few of these, but only one (about a decade ago) that used legs not wheels
Wouldn't it be better if the robot walked rather than rolled?
You may be able to illuminate this for me...
Re: Ask HN: What Are You Working On? (June 2025)
#814Re: Ask HN: What Are You Working On? (June 2025)
#815Turn any command into an AI-discoverable MCP tool with a few lines of YAML:
name: hello-world
description: "Greets the world"
command: "echo 'Hello, World"
Any AI agent can search for "greeting" and use your tool.
I'm also building the first registry at https://enact.toolsRe: Ask HN: What Are You Working On? (June 2025)
#816Re: Ask HN: What Are You Working On? (June 2025)
#817Re: Ask HN: What Are You Working On? (June 2025)
#818Re: Ask HN: What Are You Working On? (June 2025)
#819The insight: Most security scanners find problems but don't fix them. Industry average time to fix critical vulnerabilities is 65+ days. We generate the actual fixes and create PRs automatically, including educational content on the nature of the vulnerability and the fix in the PR description.
Technical approach: - AST-based pattern matching (moved from regex, dropped false positives from 40% to Business model experiment: Success-based pricing - only charge when fixes get merged ($15/PR at the moment). No upfront costs. This forces us to generate production-quality fixes & hopefully reduces friction for onboarding.
Early observation: Slopsquatting (AI hallucinating package names that hackers pre-register) is becoming a real attack vector. It's pretty straightforward to nail and has a lot of telltales. Building detection & mitigation for that now.
Stack: Elixir/Phoenix, TypeScript, AST parsers
Re: Ask HN: What Are You Working On? (June 2025)
#820English is weird.