Have we? JS has its async/await syntax, and you can even handle exceptions with less pain (just uh try not to put multiple awaits in a try block). But there are still a gazillion async libraries in npm indicating things missing from the language or older libraries, and then the rest of the JS/TS ecosystem that from my perspective has only doubled down on some of its worst aspects. It looks more like regression when developing similar to how the ClojureScript guys have enjoyed things since at least 2014 seems further away now than it did then, or how it can be controversial when people like dhh push a "no build" approach.
shiny new tools but people only want to use them on the same old problems. how can we innovate the development of crud apps even more?! that was what plagued the web dev landscape for some time. Constantly seeking newer lazier means of producing the same old product. I admit it has an allure but if companies are no longer constrained by dev effort / labour then they can only ponder their own reflection as the source of their failures.
I would advise against using it. The code it returns comes from real public repos, so including it in your work could lead to copyright issues. You'd probably be better off asking an LLM to come up with gibberish.
Sure, we’ll get a tyrannical worm phase… but really I think I’d prefer that to the path of tech bros and MBAs controlling my universe. At least it makes the focus clear.
I think you might have skipped over the 10,000+ years of strict feudalism, a shrouded theocracy pushing their century-spanning agendas, aristocracy through landed gentry, and a drug-addled transportation cartel, all overseen by a massive, monopolistic megacorporation that controls all trade, economic affairs, and commerce throughout the universe. And everyone's a drug addict if they can afford it.
But sure, at least they didn't have AI! lol!
In other words, Warhammer 40K but without any aliens to trigger a massive xenophobic response that removed all warlike guardrails.
In 92 as I recall my school's unremarkable computer lab had apple iis and Macintosh mix. We never learned any programming we wrote essays in word software and got to play kidpix, Carmen San Diego, Oregon trail if we were good
I have seen people just generate large docs with Claude cowork and they themselves have not scrutinized it or know why/how it's useful. It's just kind of impressive in its volume and well formatedness. And then they dump it in your lap as being helpful
> And then they dump it in your lap as being helpful
I've been guilty of this and gotten pushback from my manager: "this feels like homework, cut these options down to 100 words each, max".
Curation and refinement are even more important when you can have genAI generate reams of text.
Seeking outside signals is even more important, like talking to customers, looking at real usage data, and more. It's too easy to trust believe what Claude tells you, even if you say "please argue against this idea", which you always should.
We often see this bizarre workflow where notes, like engineering notes, are converted to large prose using AI. And then, the large prose is converted back to short bullet points on the other end for summarization!
I know, I know. It was more a tounge in cheek comment to something I assume was irony as well. To be fair to GP, management doesn't get any of this...
Adding is always easier than reducing to the essence.
I find it interesting how herding agents has so much in common with being a team lead. Constant struggle between too detailed and too loose instructions. One difference though is that the team learns from you, but with agents it's only you who adapts. Saying that, because I don't count instructions or anything in the context window as adapting.
I have seen this happening with contracts. Using AI to help evaluate contracts is fine, but I'm getting 5-10 page Claude docs with dozens of asks that they haven't read and many of which don't make sense. I find it pretty counterproductive, because it makes negotiation almost impossible -- you can't tell what the other side wants, because they haven't even read the output.
Yes, that's the root of it. Just let Claude create a list of demands. Then you've "done the job" of contract negotiation. You don't even have to think about what the business needs or what the partnership goals are.
It matches the pattern of LLMs being very good at simulating the form of work output, which is an issue with code but it seems quite exacerbated with anything non-verifiable, like written communication.
I'm beginning to see this in my industry (consulting). I was at a client site last week and in a room with some heavy hitters both from my side and client side but in a casual setting (lunch). Everyone was discussing how they sometimes "cheat" using genAI to put together decks when one of the out-of-the-blue 1 sentence questions that takes 4 hours to answer come down from the c-suite. They all said they heavily edit the output but at least it gives them a place to start. I have my doubts though, i wonder how many times they just take it as gospel and forward the deck on.
to be fair, i've been guilty of this with code. Ask claude to generate a python script that takes X as input and produces Y as output, run it, pipe to more, output looks ok but i don't check everything, write it to a file, send it on.
We've really reached the point where one person uses AI to create an impressive report based on a few prompts with some keywords, and the receiver uses another AI to summarize the report to a short TL;DR that's almost identical to the input prompts.
This, creating order from chaos (reducing entropy) is difficult and requires real intelligence. Inflating some small prompt into a wall of text and creating a bunch of entropy in the process is not as useful as it appears.
This reminds me of that game of telephone. Eventually, the message gets morphed and transformed into something different from what was originally said. Is this really what we want?
I definitely prefer typescript to python. But typescript doesn't have a pytorch equivalent..
Also AI doesn't write code in all langs / frameworks equally. For many cases, it will almost always fail first attempt at producing working syntax in various frameworks. Unless you document those cases and mitigate via an AGENT doc instruction or something you will have to churn at least one extra turn on all those cases.
reply