Writing code is the "easy" part and kind of always has been. No one triggers incidents from a PR that's been in review for too long.

Conn is just a pipeline of functions, the initial Conn struct is created at request time and passed through to each function in the pipeline.

https://www.erlang.org/doc/apps/erts/erl_cmd.html#%2Bsbt

LLMs can help answer the questions. However, they're not going to necessarily make the correct choices or implementation without significant input from the user.

"Write me a server in Go" only gets you so far. What is the auth strategy, what endpoints do you need, do you need to integrate with a library or API, are there any security issues, how easy is the code to extend, how do you get it to follow existing patterns?

I find I need to think AND write more than I would if I was doing it myself because the feedback loop is longer. Like the article says, you have to review the code instead of having implicit knowledge of what was written.

That being said, it is faster for some tasks, like writing tests (if you have good examples) and doing basic scaffolding. It needs quite a bit of hand holding which is why I believe those with more experience get more value from AI code because they have a better bullshit meter.

If anything, prompting well is akin to learning a new programming language. What words do you use to explain what you want to achieve? How do you reference files/sections so you don't waste context on meaningless things?

I've been using AI tools to code for the past year and a half (Github Copilot, Cursor, Claude Code, OpenAI APIs) and they all need slightly different things to be successful and they're all better at different things.

AI isn't a panacea, but it can be the right tool for the job.

gen_stage is just a library. One could write it in Erlang. It's like asking why Broadway is only for Elixir and not Erlang.

It was hard to approach the Erlang docs when I started in Elixir. However, they've moved to an ex_doc format (is it ex_docs?) as a standard and it's so much easier to grok.

Claude says you can use a CTE to select and the run your update with the locked rows, but I have only ever used transactions.

I found an explanation on a site once but haven't found any official docs. I suppose you could reverse enegiener the SDKs.

It seems like half of it is Sonnet output and it doesn't describe how the protocol actually works.

For all its warts, the GraphQL spec is very well written https://spec.graphql.org/October2021/