Development Evolving Dark’s tracing system One of the things that makes Dark truly unique is what we call "Trace-driven development". The best way to write a HTTP handler in Dark is to start by making a request to the non-existent handler, then: using the 404s list to create the handlerusing the actual trace value to
Startup First Dark contributor meetup On Friday we had our first contributor meetup. Thirteen folks showed up to a zoom call to discuss how to contribute to Dark. Obviously, the point of the conversation was to get to know each other. We're all hanging out in the #contributors channel, but the room isn't super chatty
Development Dark devlog #3: onboarding An annoying thing about coding is that some days you're on fire, producing masterpieces, knocking down obstacle after obstacle. And some weeks, you're trapped figuring out bugs that ultimately come down to having a semi-colon out of place. Most of the time for me, the difference between the two is
Development Dark devlog #2: what next? After spending the last week on some extremely urgent things on my plate (helping the team get jobs, moving, infra stability, costs, and legal and transition work), I have time to get back to the product. There's still not a clear sense of what to work on next. The positioning
Startup Dark devlog #1: fresh start So right now Dark is made up of 100,000 lines of code, a hosted service with 6000 users, a 1600 member Slack community, 39 people who have contributed or intend to contribute to our repo, and 500ish "real" projects. And—as of recently—just me to build it. This
Startup Dark Residency We’re opening up for a couple more alpha users in our residency (so far, we’ve had two people build their business on it through a similar program, see below¹). Dark lets you write a backend really easily, and your infrastructure is set up as soon as you write
