News for hackers. Stuff that matters.

A comment on A robotic sewing machine could throw garment workers out of a job. Parent comment

Re:A robotic sewing machine could throw garment workers out ... by cheepin on Tuesday October 06, 2015 @08:15PM (#10343350)
Interesting how they predict Programmers have a higher chance of automation than the other areas of engineering since programmers are the ones automating other things. I figure once programming is fully automated, pretty much everything else is automatable.
[ Parent | on HN ]
Re:A robotic sewing machine could throw garment workers out ... by gutnor on Tuesday October 06, 2015 @08:23PM (#10343380)
I guess they are actually talking about the actual translation of precise requirements to code.

Most of the programmer in western countries handle a lot more than the coding of things. If your job contains even a tiny bit of analysis, the probability drop significantly. Computer system analyst has a 0.6% chance of being automated according to this. Software Developer is 4.2%.

[ Parent | on HN ]
Re:A robotic sewing machine could throw garment workers out ... by jabgrabdthrow on Tuesday October 06, 2015 @09:33PM (#10343647)
> translation of precise requirements

I think code can be recursively defined as "the translation of precise requirements to code". Seems like it's word games and everyone just wants to name the "last automatable thing" after what their current role is

[ Parent | on HN ]
Re:A robotic sewing machine could throw garment workers out ... by bendykstra on Tuesday October 06, 2015 @10:57PM (#10343968)
I'm having trouble imagining any sufficiently specific and unambiguous format for writing requirements that does not look like programming. Even something like SQL, which only needs to describe database queries, is still the domain of the programmer.
[ Parent | on HN ]
Re:A robotic sewing machine could throw garment workers out ... by techdragon on Wednesday October 07, 2015 @01:06AM (#10344274)
Diagrams, other visual and high level declarative programming are all readily grasped by non programmers. The full impact of their "program's" behaviour may not be. But since when has there never been a junior dev position who's work couldn't be made better by knowing more. The very notion of junior dev implies they have more to learn.
[ Parent | on HN ]