You have the .com? That's a no-brainer imo. I have a domain for a saas where the .com is squatted so I settled for .ai (and other surrounding TLDs / host permutations) and right out of the gate ran into some issues with firewall vendors in corpo environments.
I have definitely noticed other people using LLM-choice words, myself included, more frequently. It's a strange phenomenon to witness. Obviously the models got them from us first so there must've been some popularity there prior, but the boost is clear. Blast radius, load-bearing, shape, and so on. Or maybe they were always there and my confirmation bias is in high gear.
One I've started noticing is the "quotation marks around a phrase awkwardly trying to bundle a concept" thing. Like all LLM cliches it's something that has been used in writing for a long time, but I've seen it so much more recently. I think lots of people have picked this up from seeing LLMs use it. But like you said, who knows.
I do have a sneaking suspicion it's a mix of things, I'm at the point now that I do get a bit of an odd feeling whenever I'm reading AI produced content
I suspect over time it will get good enough that I'll need a larger sample size to identify it, however that won't solve what I think of as the "why does this need to exist" problem, I've noticed that a fair bit of AI content hits that mark, it can be fun, but I've not experienced that feeling of engaging with something that's been well thought out / executed, maybe we'll hit that point[0], but I suspect it will take a while
But crucially they used "--" and not "—" which means they're safe. Unless it's learning. I may still be peeved that my beloved em dash has been tainted. :(
Indeed it does. I maintain one such application while an in-progress rewrite develops. Gotta say, it's not been that bad and the Lucee docs have served me well, but for whatever reason I tend to be pleased/impressed by all kinds of tech, even when popular opinion is negative about it.
I know exactly the streamer you're referring to and this is the first time I've seen an overlap between these two worlds! I bet there are quite a few of us. Anyway, agreed on all accounts, watching someone like him has been really eye opening on how some people use these tools ... and it's not pretty.
I just shipped a feature exactly like this... Jira has the same thing with JQL, which is what inspired my work. Safe from SQL injection and can be used directly by power users or managed through form inputs for basic search/filtering. We use Elasticsearch for other data atm, but I'm hopeful this new PostgreSQL only approach wins out as it makes authz so much simpler since it all composes into one query.
My personal goto-solution for those requirements -- well 1 cloud provider, I'll follow up on that in a second -- would be using ECS or an equivalent service. I see the OP was a critic of Docker as well, but for me, ECS hits a sweet spot. I know the compute is at a premium, but at least in my use-cases, it's so far been a sensible trade.
About the 2 cloud providers bit. Is that a common thing? I get wanting migrate away from one for another, but having a need for running on more than 1 cloud simultaneously just seems alien to me.
Last time I checked ECS was even more expensive than using Lambda but without the ability of fast starting your container, so I really don't get the niche it fits into, compared to Lambda on one side and self-hosting docker on minimal EC2 instances on the other side.
I may need to look at Lambda closer! At least way back, I thought it was a no-go since the main runtime I work with is Ruby. As for minimal EC2 instances, definitely, I do that for environments where it makes sense and that's the case fairly often.
Actually, I totally agree. ECS (in combination with secret manager) is basically fulfilling all needs, except being not so easy to reproduce/simulate locally and of course with the vendor lock-in.
