Ask HN: What are you working on? (September 2025)
931–940 of 1001 posts
Re: Ask HN: What are you working on? (September 2025)
#932Earlier quoted context omitted.
Neat idea. Would you say that biggest difference from something like Kysely is the focus on extracting common calculated SELECT targets into methods that can easily be accessed when querying? Or perhaps it's more thorough with providing TS versions of all the SQL syntax available? The list of reference fields/methods in your docs is certainly massive.
Thanks! That's a great question. First off, I'm a huge fan of Kysely and it's a massive source of inspiration for Typegres. You've nailed the two big differences: * Architected for Business Logic : The primary innovation is the class-based model. This is all about co-locating your business logic (like calculated fields and relations) directly with your data model. The cool part is that these methods aren't just for S…
Re: Ask HN: What are you working on? (September 2025)
#933I’m working on an ISBN database that fetches information from several other services, such as Hardcover.app, Google Books, and ISBNDB, merges that information, and return something more complete than using them alone. It also saves that information in the database for future lookups. Mostly because I’m working on a personal library management service called Shelvica to solve my own problems[1], and none of those serv…
Re: Ask HN: What are you working on? (September 2025)
#934Re: Ask HN: What are you working on? (September 2025)
#935A side project to keep track of themes being released for Omarchy: https://omarchythemes.com/ Been enjoying using Omarchy and this is my way of keeping tabs on what's going on.
Re: Ask HN: What are you working on? (September 2025)
#936I'm working on Vedro, a Python testing framework as a pytest alternative without the magic and with clear output. The main idea is that tests should just be Python: plain `assert` statements instead of custom matchers, no fixture magic, and when tests fail you get readable diffs that actually show what went wrong. Tests can be simple functions or structured with steps that self-document in the output. https://vedro.i…
As someone that loves Python and hates pytest, you have my support. (Although, I don't like using bare `assert`s in tests, but maybe you'll convince me.)
About bare `assert`s. Vedro is actually flexible enough to use any matchers you prefer, but let me share why I stick with plain asserts:
1. In most editor themes, `assert` jumps out with distinct syntax highlighting. When scanning tests, I can quickly spot the assertions and understand what's being tested.
2. The expressions feel cleaner to me:
assert error_code not in [400, 500]
# vs
assert_that(error_code, is_not(any_of(400, 500))) # hamcrest
3. I like that there's nothing new to learn, the expressions work exactly like they do in any Python code, with no special test behavior or surprises.Would love to hear what specifically bothers you about bare asserts, always looking to understand different perspectives on testing ergonomics!
Re: Ask HN: What are you working on? (September 2025)
#937I'm working on Vedro, a Python testing framework as a pytest alternative without the magic and with clear output. The main idea is that tests should just be Python: plain `assert` statements instead of custom matchers, no fixture magic, and when tests fail you get readable diffs that actually show what went wrong. Tests can be simple functions or structured with steps that self-document in the output. https://vedro.i…
I like the promise, and it looks nice. But I'm not sure what are the selling points. - pytest already works with assert. Why brag about something that is already commonplace? - It could help if your docs explained the alternative to using fixtures. I assume it would be done by re-using givens, but you could make it clearer what is the preferred way to do it, and what is gained, or lost, but doing it that way. - Can y…
These are excellent questions, and you're absolutely right that they should be clear from the landing page. I'll work on fixing that.
Short answers:
1. Good point about asserts. When writing the benefits, I was targeting a broader audience (unittest users, people coming from other languages like JS), but the reality is most visitors are probably "pytest escapers" who already know pytest uses assert. I'll reorganize the selling points to focus on what actually differentiates Vedro.
2. The main philosophy is "all you need is functions and their compositions", no special decorators or dependency injection magic. But this is indeed missing from the index page. Will definitely add clear examples showing how to handle common fixture use cases with plain functions.
3. One diff example on the landing page clearly isn't enough. I'll add more comparisons. Since you hate pytest's diff output too, I'd love to hear what specifically bothers you about it, your pain points would be incredibly valuable for improving how I present Vedro's approach.
Re: Ask HN: What are you working on? (September 2025)
#938Been having a lot of fun building SecurityBot ( https://securitybot.dev/ ), a free security and uptime monitoring service. It keeps tab on your HTTP security headers including CSP, robots.txt, security.txt. open/closed ports, ping times, uptime, and more.
Re: Ask HN: What are you working on? (September 2025)
#939Hi HN, I am working on Circuitscript, a language based on python to describe electronic schematics/circuits: https://circuitscript.net/ Recently, I have released a simple IDE (called the Bench) to try Circuitscript online: https://bench.circuitscript.net/ The next steps are to create more schematics with Circuitscript as examples to test the limitations of the language and to generate PCB designs with KiCAD. The Circ…
I think it may be a good idea to either enable auto-save or remind the user that there are unsaved changes before navigating away from the page.
Re: Ask HN: What are you working on? (September 2025)
#940Long nights and weekends to, but is all well worth it.