Earlier quoted context omitted.
Well .... making a website != programming. Maybe it's because I'm old (41, starting programming on a TRS-80 in the early 80s), but I'm astonished sometimes at how much fuss is made over such relatively minor achievements. This is lowering the bar on what stories are 'interesting', and - honestly - turns me off coming to HN because of the (for me) lower signal : noise ratio. And I disagree that accessibility is so imp…
>Well .... making a website != programming. Oh man, I remember when everyone looked down on web programmers and PHP monkeys. Hah. (I also did my much of my early programming on a trs-80, but mine was an obsolete tandy model 100 that I brought to school in the mid-90s, mostly to automate the 'guess and check' rote math homework.) It used to be that there was a strong hierarchy. I know in the '90s and the first half of…
IMO we've already seen the automation of web-CRUD. It used to be a lot of work to set up even a simple CRUD app on the web, now a brain-dead simple CRUD app is 15 minutes in skilled hands.
This differs from Visual FoxPro substantially. Our jobs are being automated, but instead of automating into the hands of an army of lay users, it's automating into the hands of a few skilled practitioners.
The productivity of the modern web programmer is at least an order of magnitude beyond where we were 10 years ago. What used to take a veritable army of CS majors takes 3 people and a fridge full of Red Bull.
Our tools and processes are getting better every day. So far "stuff that needs to be done" seems to be outpacing "increasing efficiency per programmer", but I doubt that will hold true forever.