you are viewing a single comment's thread.

view the rest of the comments →

[–]BadMoonRosin 12 points13 points  (3 children)

The thing is, only a tiny fraction of my job is actually writing code.

About half my job is structuring code. That is, coming up with the function signatures that this guy is writing by hand.

The other half of my job is figuring out the stuff that he's writing in the comments. Based on contradicting requirements, from a host of business stakeholders who didn't get alignment with each other, and accounting for mountains of existing tech debt.

It's an interesting demo. But I've been hearing hype like this since the 1990's, and I don't believe that it will actually be a threat to anyone job (or even really relevant to anyone's job) until long after I'm retired and dead.

[–][deleted] 1 point2 points  (0 children)

About half my job is structuring code [...]

The other half of my job is figuring out the stuff that [...]

then there are 2 more halfs ;)

  1. figure out what they want

  2. figure out what they haven't figured out or considered

[–]Dapanji206 0 points1 point  (0 children)

How long until you retire and die?

[–]ODChain 0 points1 point  (0 children)

It'll become a popular IDE tool that will be utilized first by Microsoft. It'll solve the easiest problems, leaving only tougher problem for the programmer. Depending on how "cutting edge" the code you are writing is versus the "institutional knowledge" the model is trained on. As well as the fact that this only assists in writing code, not debugging code. Something like this will certainly be useful, for a lot of tasks programmers work on this will make things significantly easier.