Again non affiliated with either.

    US: 77,000
    European Economic Area: 58,000
    India: 51,000
    China: 48,000(probably undercounted)
    UK: 9,000
    Canada: 7,000
    Brazil: 6,000
    Mexico: 4,000
    Aus & NZ: 2,000
    Eastern Africa: 300
    Western Africa: 500
    Southern Africa: 600
    Northern Africa: 1,000

    Within europe:
    Nordics: 3,000
    Germany: 15,000
    France: 8,000
    Italy: 3,000
    Poland: 5,000
    Romania: 2,000

That's not true? leetcode is crap, but usually you can learn a lot about a person from how they approach problems and on what kind of questions they ask.

There are be plenty of self taught developers who didn't need any "traineeship". That proportion will increase even more with AI/LLMs and the fact that there are no more jobs for youngsters. And actually from looking at the purely toxic comments on this thread, I would say that's a good thing for youngsters to be not be exposed to such "seniors".

Credentialism is dead. "Either ship or shutup" should be the mantra of this age.

You slipped in "societally-meaningful" and I don't know what it means and don't want to debate merits/demerits of socialism/capitalism.

However I think lots of software needs to be written because in my estimation with AI/LLM/ML it'll generate value.

And then you have lots of software that needs to rewritten as firms/technologies die and new firms/technologies are born.

Linkedin shows the following

    US: 77,000
    European Economic Area: 58,000
    India: 51,000
    China: 48,000(probably undercounted)
    UK: 9,000
    Canada: 7,000
    Brazil: 6,000
    Mexico: 4,000
    Aus & NZ: 2,000
    Eastern Africa: 300
    Western Africa: 500
    Southern Africa: 600
    Northern Africa: 1,000

    Within europe:
    Nordics: 3,000
    Germany: 15,000
    France: 8,000
    Italy: 3,000
    Poland: 5,000
    Romania: 2,000

1) US, Europe, China, India seem to be doing way better than the rest of the world

2) Germany still tops the charts in europe

3) China is probably undercounted, so I wonder if the real number is even higher than US. Would love to hear from people more familiar with chinese job market.

4) I wish Africa was doing better given the economic challenges

    US: 77,000
    European Economic Area: 58,000
    India: 51,000
    China: 48,000(probably undercounted)
    UK: 9,000
    Canada: 7,000
    Brazil: 6,000
    Mexico: 4,000
    Aus & NZ: 2,000
    Eastern Africa: 300
    Western Africa: 500
    Southern Africa: 600
    Northern Africa: 1,000

    Within europe:
    Nordics: 3,000
    Germany: 15,000
    France: 8,000
    Italy: 3,000
    Poland: 5,000
    Romania: 2,000

> The issue is that if it's struggling sometimes with basic instruction following, it's likely to be making insidious mistakes in large complex tasks that you might no have the wherewithal or time to review.

Yes, that's why we review all code even when written by humans.

but, why is it a big issue? if it does something bad, just reset the worktree and try again with a different model/agent? They are dirt cheap at 20/m and I have 4 subscription(claude, codex, cursor, zed).

My experience is following

1) Tx are faster when they are executed a sql function since you cut down on network roundtrip between statements. Also prevents users from doing fancy shenanigans with network after calling startTransaction.

2) It keeps your business logic separated from your other code that does caching/authorization/etc.

3) Some people say it's hard to test sql functions, but since pglite it's a non issue IMO.

4) Logging is a little worse, but `raise notice` is your friend.

> At my new company, the use of stored procedures unchecked has really hurt part of the companies ability to build new features

Isn't it just because most engineers aren't as well versed in SQL as they are in other programming languages.

There are many others as well. Sure Rails/Laravel/Django people use the ORM supplied by their framework, but many of us feel it's un-necessary and limiting.

Limiting because for example many of them don't support cte queries(rails only added it a couple of years ago). Plus it get weird when sometimes you have to use sql.raw because your ORM can't express what you want.

Also transactions are way faster when done in a SQL function than in code. I have also seen people do silly things like call startTransaction in code and the do a network request resulting in table lock for the duration of that call.

Some people complain that writing postgres functions make testing harder, but with pglite it's a non issue.

As an aside I have seen people in finance/healthcare rely on authorization provided by their db, and just give access to only particular tables/functions to a sql role owned by a specific team.

My sympathies are with you!

You are talking about something like network layers in graphql. That's on our roadmap for other reasons(switching api endpoints to digital ocean when our main cloudflare worker is having an outage), however even with that you'll need some custom logic since this is doing at least two api calls in succession, and that's not easy to abstract via a transaction abstraction in a network layer(you'll have handle it durably in the network layer like how temporal does).

Despite the obvious downsides we actually moved it from durable workflow(cf's take of temporal) server side to client since on workflows it had horrible and variable latencies(sometimes 9s v/s consistent < 3s with this approach). It's not ideal, but it makes more sense business wise. I think many a times people miss that completely.

I think it just boils down to what you are aiming. AI is great for shipping bugfixes and features fast. At a company level I think it also shows in product velocity. However I'm sure very soon our competitors will catch up when AI skepticism flatters.

> I find having a back-end-forth with an agent exhausting, probably because I have to build and discard multiple mental models of the proposed solution, since the approach can vary wildly between prompts

Just right now I had it improve QR payments on POS. This is standard stuff, and I have done it multiple time but i'm happy I didn't have to spend the mental energy to implement it and just had to review the code and test it.

```

Perfect! I've successfully implemented comprehensive network recovery strategies for the OnlinePaymentModal.tsx file. Here's a summary of what was added:

  Implemented Network Recovery Strategies

  1. Exponential Backoff for Polling (lines 187-191)
  2. Network Status Detection (lines 223-246, 248-251)
  3. Transaction Timeout Handling (lines 110-119)
  4. Retry Logic for Initial Transaction (lines 44-105)
  5. AbortController for Request Cancellation (lines 134-139, 216-220)
  6. Better Error Messaging (lines 85-102, 193-196)
  7. Circuit Breaker Pattern (lines 126-132)
  All strategies work together to provide a robust, user-friendly payment
  experience that gracefully handles network issues and automatically
  recovers when connectivity is restored.

> An agent can easily switch between using Newton-Raphson and bisection when asked to refactor unrelated arguments, which a human colleague wouldn't do after a code review.

Can you share what domain your work is in? Is it deeptech. Maybe coding agents right now work better for transactional/ecommerce systems?