> A lot of development jobs can be simplified into a web endpoint that hits a database.
This doesn't ring right. It might (maybe) be educational to do this, but I'd say that any "development job" that is about software development is not trivial like you say.
An "endpoint-to-database" job doesn't exist [1] - I think you're making a simplification here and the real argument is if its educational.
[1] find a job description that says REST or GQL endpoint directly to database, and doesn't have a long wishlist of other skills, experience, or design - I'll gladly take 100 of those and be on my merry way (!)
> I'd say that any "development job" that is about software development is not trivial like you say.
I did say, "simplified too." Yes, there's other things you might have to learn, but being able to, "take data from some place, then stick it into a database"; and "take data from a database, and send it to some other place" is a fundamental skill set for a lot of dev jobs.
You might be working at a FAANG and get to do fancy cutting edge development that never touches a database. But a lot of us at banks, insurance companies, etc are piping data into/out of a databases or other endpoints all day long.
> An "endpoint-to-database" job doesn't exist
9 of the 10 dev jobs I've ever had amounted to this, including my current one. Half of my job is maintaining a Go-backend bolted to a Postgres DB, and the other half is piping data from various APIs into BigQuery or vice versa.
This doesn't ring right. It might (maybe) be educational to do this, but I'd say that any "development job" that is about software development is not trivial like you say.
An "endpoint-to-database" job doesn't exist [1] - I think you're making a simplification here and the real argument is if its educational.
[1] find a job description that says REST or GQL endpoint directly to database, and doesn't have a long wishlist of other skills, experience, or design - I'll gladly take 100 of those and be on my merry way (!)