The readme was very clearly AI-written (or at least heavily AI-assisted)... not saying that's a bad thing, and I agree it's fairly well written... but it is very obviously AI
k, I just looked through it for where the latest is. First of all, the earliest version were fully written by me, and then lightly edited with AI. The current state are as follows: intro sentences written by me, "why lightspeed" section too. Quickstart AI written, Features mostly written by me, but AI keeps interfering there. Design was also written by me several times, it also used to be much longer, but I just noticed AI put one a few paragraph of slop in there, I think that's the most egregious--shame on me for not caching it. So, if I look at the readme right now, I would say it's about 60% me. It can be better, I'll make the effort because it really bothers me if readmes are not (mostly) written by humans.
I really don't have a problem with you using AI, as long as you review and validate/test what it writes, and seems like you did that. Great project btw!
Stripe has already existed for a while, and has gone through ups and downs. There was a period where customer experience was first, and the systems inside were built fast and in rather cavalier ways (See Greg Brockman famously telling everyone in a MongoDB convention about using Mongo's oplog as a queue). There were times where internal tools teams could spend all the time they needed to get about as much shine internally as the external facing websites were. Huge investments in everything. But there's just so much churn, as some staff burns out, and others realize that they have so much vested stock that continuing in such a high intensity environment is pointless, that whatever Stripe might have been during your tenure might be very different from other people's, and you can both be right.
I worked at stripe too. Sail design system at time was exemplary. A ton of effort got invested in little details. They spent an insane effort in making ruby fast with their own jit, formatter and type checker they built.
I think it has more to do with the fact that Stripe has already 'won' in a lot of ways, and the company has now basically transitioned from the innovative tech startup phase to the MBA/marketing/bureaucracy phase. Quality, efficiency as priorities are replaced with marketing and 'strategy'...
I've been working on a general repository linter. The idea is to declaratively define a set of rules/conventions for your repo, (for things that language-specific linters don't cover), covering things from directory structure, required files, file staleness/freshness, file size, rules for binary files, rules around use of invisible Unicode, etc. - which can be checked deterministically. Many/most large repos have a set of hand-authored scripts for doing these kinds of checks, the tool I'm building basically packages these in a fast, reusable and extensible tool, with some niceties added.
It would be great if I could integrate this into our existing (and rather extensive) eslint config as as a plugin of some sort rather than integrate yet another new tool to our dev environment. Any plans for that?
Yeppp, I've been seeing this Jacob Coxon [0] guy popping up all over legacy media for the past couple days nonstop...he claims he quit OpenAI and Anthropic because the models are getting 'too smart' and that's dangerous, etc. The typical AI fears mongering drivel, without seemingly any criticism, at all, of the companies he quit supposedly because of these AI fears... and of course the mainstream media appearances prefix the interviews with this guy with 'this is not a marketing stunt'[1]... which, obviously, it is.
Seems just like another case of collusion - continuing the story of VCs pushing all of their companies to use each other and 'stay within the network'. The good news (kinda) for the rest of us, is that many of these VC marketing/product/'strategy' people aren't actually all that competent - this is literally the best they can come up with.
I use alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it run as a pre-commit hook or in CI.
I use alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it run as a pre-commit hook or in CI.
You can also use something like alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it to run as a pre-commit hook or in CI.
I use alint [0][1] to define and enforce rules about files/globs that should or shouldn't be committed, among other things. You can configure it run as a pre-commit hook or in CI.
reply