Latest / The FIT4Privacy Podcast | Exploring ISO Standards AI Privacy | Grow Skills Store / Will all developer lose job because of AI doing the coding

Transcript

Will all developer lose job because of AI doing the coding · The FIT4Privacy Podcast | Exploring ISO Standards AI Privacy | Grow Skills Store

• 0:00
  This AI that we are facing, it's no longer programmed to do what
• 0:05
  it's programmed to do. It's programmed by us through
• 0:08
  usage. And that's an important element.
• 0:10
  And for somebody who has set up a developers association, I'm
• 0:13
  tempted to ask how does it impact the developer community?
• 0:17
  Because the extremist or the news are saying the developer
• 0:21
  community will be wiped off. We will not have any software
• 0:24
  development companies. We will not have any developers.
• 0:27
  I know it's an exaggeration, but what's your view on that as an
• 0:31
  association of developers? What do you see going forward?
• 0:34
  How this developer industry or developer role shifting
• 0:38
  changing? Yeah, I, I think reports of the
• 0:41
  demise of the developer ecosystem have been greatly
• 0:44
  exaggerated. I, I think that I suspect that
• 0:47
  what we're going to see in the, so I saw that, I, I saw a couple
• 0:53
  weeks ago, there was an article that I, I quite enjoyed about
• 0:57
  how AI has actually generated an entire generation of decoders
• 1:01
  that are actually coding again, that the no code low code
• 1:05
  movement over the last three years where it's so easy,
• 1:08
  anybody can do. It was actually removing some of
• 1:10
  the creativity that goes into the development of software as a
• 1:13
  rule. But we're 1516 years out from
• 1:16
  the idea of software eating the world.
• 1:19
  It ate the world, it's gone. Software is everywhere.
• 1:22
  There's nothing left on the plate.
• 1:24
  So we're now into a different space where we're talking about
• 1:27
  dimensions of speed and scale more than we are creativity and
• 1:32
  engineering. There's certainly going to be
• 1:35
  downward pressure on this generation of junior developers
• 1:39
  who were working on things like front end website development.
• 1:43
  Those people are going to have to learn some new skills
• 1:47
  because, you know, a somebody with a little bit of taste and
• 1:51
  patience can use or sell to front end code an entire landing
• 1:56
  page now. Great.
• 1:58
  But we were there with Squarespace 6 years ago.
• 2:02
  Seven years ago, we were already moving in that direction pretty
• 2:05
  aggressively. The importance, however, of of
• 2:09
  an engineer, of a developer that knows what they're doing has
• 2:13
  never been higher. Because vibe coding is a
• 2:17
  complete waste of time, even from a prototyping standpoint,
• 2:20
  if somebody isn't defining the variables and setting the
• 2:23
  parameters around which you're building.
• 2:25
  And like all things, and you know this better than anything,
• 2:29
  data is going to drive the bus on this.
• 2:32
  And if you can't plug an interface into the data you need
• 2:36
  and the data you want and how you're going to use the data and
• 2:38
  comply with data rules and privacy and manage those inputs
• 2:41
  and outputs, you don't have a business, you don't have a
• 2:44
  solution, you're probably in violation of several laws, and
• 2:48
  consumers are not going to enjoy what you're delivering to them.
• 2:51
  So whether it's an enterprise solution from Cisco or you're
• 2:55
  talking about two guys in a garage like the Silicon Valley
• 2:58
  dream that we all talk about, no, the future of development
• 3:01
  and developers is as bright as it's ever been.
• 3:05
  OK, that's very clear. But before I go into your point
• 3:09
  on data, I have a follow up on the developer aspect.
• 3:13
  I think we both tend to agree that the developers will remain,
• 3:16
  the development job will remain, software development will
• 3:18
  happen, it will shift and it will become more efficient, more
• 3:22
  effective. Because if there was a, because
• 3:25
  I, it reminded me of an example. I started off as a software
• 3:29
  developer and then one time I was asked to code about daylight
• 3:32
  savings. And I understand nothing about
• 3:35
  that. At that time.
• 3:36
  It was back in 2002. I coded it, but I coded it
• 3:40
  abstractly. And when I moved to Europe in
• 3:42
  2006, 556 and I've experienced daylight saving and understood
• 3:47
  what I was being asked. One day we'll have 23 hours and
• 3:50
  one day we'll have 25 hours. And that's what you have to
• 3:52
  adjust in the daylight saving because I was building the
• 3:55
  software for some energy company.
• 3:58
  But beyond the point what was expected of a developer was that
• 4:02
  they understand what they're doing.
• 4:04
  They become human and they become business aware.
• 4:07
  Business aware. What am I coding?
• 4:09
  Why am I coding? What's the purpose and what's
• 4:11
  the effect of it? Not that somebody tells you it's
• 4:13
  23 hours and 25 hours. And that need, that desire for
• 4:18
  them to be more relevant will increase.
• 4:21
  Plus they will have tools at the disposal becomes to AI that they
• 4:24
  don't have to write the structure and everything.
• 4:26
  We used to have what is called, we used to call them ID ES in
• 4:30
  integrated development environments, those days of Java
• 4:33
  and Microsoft where they were creating C# and Java.
• 4:37
  So I think those will be more extended.
• 4:39
  You will say this is what I want to write.
• 4:42
  The software writes for you, but then you enhance it, then you
• 4:44
  enrich it with your knowledge. So their job will change, job
• 4:47
  will remain, but how would it change?
• 4:49
  Can we have a peek or preview into how it will change?
• 4:52
  I'm trying to explain from my knowledge of a development.
• 4:55
  Well, I think I think you nailed it with that.
• 4:57
  You've changed the floor, right? A a developer can replace
• 5:02
  dozens, hundreds of hours by prompting a a code IDE that
• 5:08
  supports their language, right. I want to achieve this goal.
• 5:12
  Here are the variables here are the parameters.
• 5:14
  Write the base code. That's incredibly efficient.
• 5:19
  It also removes the need to to have perfect code structure
• 5:24
  right like you have. You have enabled a machine to do
• 5:27
  a commodified job that for a long time we had heads and hands
• 5:31
  coders developing that we would, you know some people derogatory
• 5:38
  name for them as code monkeys, right?
• 5:40
  Like some of it just bangs on code and it's heads and hands
• 5:43
  and I'm moving the stuff around. But they were, they were writing
• 5:47
  lines of code to meet a demand because software development is
• 5:51
  about predicting the future. You're here and I need you to be
• 5:55
  here. Here are the steps along the
• 5:57
  way. Here are the here are the
• 5:59
  options of your experience. This is what this could look
• 6:01
  like any any piece of software that is binary.
• 6:06
  Do this, don't do that expands exponentially over the course of
• 6:12
  a user journey or commercial experience or or whatever
• 6:15
  variables you want to set because every one of those
• 6:18
  decisions is binary. I do this or I don't.
• 6:20
  I do this and then I don't. I do this and I don't.
• 6:23
  What a person can do that a machine will never be able to do
• 6:27
  is feel frustration, empathise with other people, with the with
• 6:32
  the consumer and anticipate breakage.
• 6:35
  Right? Think about why something
• 6:38
  doesn't work so that that goes from a informational news
• 6:41
  website all the way to a back end SAS system that is used by
• 6:47
  Intel. Everything that is software
• 6:50
  driven. At some point, a person sat in
• 6:53
  judgement of whether or not that was the right solution.
• 6:56
  Sometimes you're confined by the technology, sometimes there's
• 6:58
  requirements, there's laws, there's other components around
• 7:01
  the Slas of a company. But the truth is a, a decision
• 7:05
  is going to have to be made by a person that's not going away.
• 7:09
  And so the deployment, the value of that person is going up and
• 7:14
  the importance of the people who are quality assurance and, and
• 7:20
  general discernment of whether or not a good decision has been
• 7:25
  made, that value is enhanced dramatically.
• 7:28
  So certainly there is going to be efficiencies created by the
• 7:32
  ability of a engineer to say, I need to accomplish this goal, go
• 7:36
  and then have a team QA the the logic and the code and all of
• 7:40
  that. But we're pretty sure machines
• 7:43
  can write code as well as a person can, but they can't do is
• 7:47
  engineer something. To catch the full discussion,
• 7:50
  head to YouTube, Spotify or Apple Podcasts and search fit
• 7:53
  for privacy. Links are in the description.
• 7:56
  Thanks for listening.