fabianlindfors

5 ms·

1.
by fabianlindfors 29d ago
We are! Got a few pilot customers that are using it but still early days
2.
by fabianlindfors 1mo ago
Sure. It's a bit hard to quantify because we need to run these on bare-metal machines and the unit cost is pretty high. We run our test workload as well as a few other startups' that we have onboarded on one AWS ARM bare-metal mac
3.
by fabianlindfors 1mo ago
Firecracker, with some tiny modifications to better manage memory for the deep nesting of forks
4.
by fabianlindfors 1mo ago
That's the point, we don't review the test code either. Our platform gives us a UI for inspecting not the test code but what actually happened during the test. Like a browser replay, the results of a database query, assertions aga
5.
by fabianlindfors 1mo ago
Forking! We run the entire stack (browser, frontend, backend, database, etc) in a Linux VM, so latency between each of the pieces is as tiny as can be. This is quite different from "standard" E2E tests I've seen where the tes
6.
by fabianlindfors 1mo ago
We try to avoid reviewing AI-generated code and built our own testing framework and platform to make that possible. Our principle is that our tests should give us enough confidence to not have to look at the code (which ends up being true f
7.
by fabianlindfors 1mo ago
That’s essentially what we do. The agent writes the browser tests (and the other tests), we just review the replays of them afterwards from the test suite.
8.
by fabianlindfors 2mo ago
Agreed, we had agents writing standard integration/unit/e2e tests but turned out to be a ton of work reviewing just that and hard to wrap one’s head around as a developer. We ended up building our own test platform to reduce the h
9.
by fabianlindfors 2mo ago
It’s worked out pretty well for the Norwegians!
10.
by fabianlindfors 2mo ago
My point is that it wouldn't be someone else's "clankers". The lab would be majority owned by the populace through their democratically elected government.
11.
by fabianlindfors 2mo ago
I agree, the datacenters and the GPUs inside them might be the least valuable thing to come out of the boom. The research in chips, architectures, and training, and the supporting infrastructure in fabs and energy grids still seems highly v
12.
by fabianlindfors 2mo ago
Oh definitely, not saying they are lying about working on a big model, but as you say I'm skeptical it will be any good. I hope they will get that boost, but I'm afraid that they haven't built credibility so far to convince g
13.
by fabianlindfors 2mo ago
I considered mentioning that in the footnote but my own skepticism stopped me. I'm now thinking I need to see it to believe it in terms of Mistral training a frontier model. That's not to say I don't hope they will. It would
14.
by fabianlindfors 2mo ago
Yes, it probably won't be clear until we have the benefit of some hindsight. One thing I'm inclined to believe though is that the investment being made into compute and research today may not benefit the investors, but it will be
15.
Europe's Bitter Lesson(fabianlindfors.se)
5 points by fabianlindfors 2mo ago|13 comments
16.
by fabianlindfors 3mo ago
Microsoft has been doing this for a long time: https://learn.microsoft.com/en-us/dotnet/csharp/linq/
17.
Anthropic pauses credit change for Claude Code
36 points by fabianlindfors 4mo ago|12 comments
18.
by fabianlindfors 5mo ago
Shameless self plug but check out: https://specific.dev (especially if you use coding agents) No code lock-in through SDKs and built on top of AWS with great DX for both developer and coding agents
19.
by fabianlindfors 6mo ago
Orbstack is definitely much better but far from native speeds in my experience. From our perspective of wanting all users to have a good experience, we also can't really point folks towards Orbstack as a "solution" to make th
20.
by fabianlindfors 6mo ago
Same to you!
21.
by fabianlindfors 6mo ago
Yes, exactly. Probably two different focuses between us, we are more focused on providing the full environment to build productively with coding agents, from local dev all the way to prod. The key thing for us is that the agent can write co
22.
by fabianlindfors 6mo ago
We have been trying to solve the same problem (and a bunch of other ones) with https://specific.dev as well. We’ve tried to stay away from Docker as much as we can though because of the still pretty bad experience on Mac. Our ap
23.
by fabianlindfors 7mo ago
Totally agree that AI coding makes this even more important. We are working on a coding agent-first cloud and a large part of that is ensuring everything runs locally so folks can let their coding agents define the infra and test it all
24.
by fabianlindfors 7mo ago
Better Auth is absolutely great. Was pleased with how well it could be extended here to replace Supabase Auth with backwards compatibility Part of this is a reimplementation of PostgREST, but as a Typescript library. The big difference is t
25.
Show HN: Replacebase – library to migrate away from Supabase(github.com)
6 points by fabianlindfors 7mo ago|2 comments
26.
by fabianlindfors 8mo ago
Yes. We are taking a stab at the entire infrastructure like Heroku did but with a focus on a coding agent-centric workflow: https://specific.dev
27.
by fabianlindfors 8mo ago
We have been working on this, letting any coding agent define infrastructure so we can define it effortlessly: https://specific.dev . We aren't just targeting non-developers though, we think this is useful to anyone building
28.
by fabianlindfors 8mo ago
You hit the nail on the head. > But those things are exactly things that LLMs already solve, especially for vibecoders who don't even know what the code is doing. For them it'd be so much better if the LLM just went with the st
29.
by fabianlindfors 1y ago
With that, I was referring to the definition in the article: "The spec is the main source file over time, and only the spec is edited by the human, the human never touches the code". That's how Specific works. And I think tha
30.
by fabianlindfors 1y ago
The note on how all those tools seem to mostly be spec-first and vague about spec maintenance was interesting to me. Me and my cofounder have been going all-in on spec-as-source, as we think it's really the most interesting use of spec

More ›