The studies you are talking about are probably outdated, it's difficult to deny the actual productivity boost of coding agents.
I'm not talking about the quantity of code produced, but about actual user needs that are now resolved that would not have been before.
The main productivity gain will not come from existing software engineer, but from people that couldn't code at all before but are now able to do things by themselves. We are still very early.
I meant that it doesn't get much love from the community, it's pretty clear it's not used much, that's why things like `dbg` gets added to the language.
Read committed (which is the default), doesn't guarantee that.
See "Nonrepeatable Read" and "Phantom Read" which are both possible in your documentation page.
I don't get the transaction bit. At least with postgres, a transaction doesn't guarantee that all statements in it see the data at the same point in time (actually, it's not even guaranteed for subqueries).
Also, often, the transactional database servers is more difficult to scale than application servers so from a technical standpoint, it makes sense to do this glue work in app code.
> Given how much programming now consists of "copy, paste,
and modify," enforcing style conventions on Stack Overflow
might do more to improve general coding standards than
anything else we could try.
I'm guessing most of developers use a formatter like black [0] nowadays so that will have less and less impact.
I'm not talking about the quantity of code produced, but about actual user needs that are now resolved that would not have been before.
The main productivity gain will not come from existing software engineer, but from people that couldn't code at all before but are now able to do things by themselves. We are still very early.