My first week of vibecoding

Summary

last week, i released typelex.it may not be a super "serious" project, but it works. it's covered by 513 tests i'm highly confident in.it is also 100% vibecoded.i may have manually edited a line or two but that was it.here's how it happenedi was complaining about things as i usually do:i wish lexicon had syntax so it wouldn’t be embarrassing to post it. whenever i see that pile of json i want to scrub my eyesthen paul posted baitdan, legit, if you make one, I will give it a very close look IMO the closest option I've seen is typespec, but I give that just as a suggestionfor context, TypeSpec is a whole-ass language with its own mini-ecosystem, LSP, formatting plugins, and "emitters" which translate TypeSpec code into concrete output formats (for example, protobuf)it's difficult to tell how committed Microsoft to it. it simultaneously gives off a vibe of a super overengineered hobby project scratching someone's personal itch, and something pretty damn useful. overall i found it very pleasant to work with. in short, it's an extensible DSL for schemas with all the tooling (like LSP) already done for you.for me, it was perfect. you see, i was not planning to Create An Actual Language for Lexicons. that is way too far outside of my comfort zone (shoutout to Matt who actually did that)however, messing with TypeSpec to get a basic Lexicon emitter running sounded within my range of skills. the problem, however, was that i didn't know TypeSpec at all (not to speak of its loosely documented emitter API). i did not know Lexicon very well either.naturally, that made it a perfect fit for my first vibecoding project.i've been meaning to give vibecoding a real try.for this experiment, i chose claude code. i'm already a heavy claude user so i did it partially out of sense of brand loyalty and partially because the cli felt surprisingly polished (lots of little nice details)my previous experience with claude code a few months ago was downright shitty—it was completely ignoring my ex...