KOPYA NG SALIN 🔗
WEBVTT
00:00:00.260 --> 00:00:05.640
Hi, I'm Richie, your podcast host and I'm happy to present you another episode in this
00:00:06.000 --> 00:00:06.720
quality series.
00:00:07.730 --> 00:00:11.720
As you know this podcast is a podcast for the software community, so for you.
00:00:12.170 --> 00:00:16.460
So please send me your feedback to topics and guests you would like to hear and see
00:00:16.540 --> 00:00:17.340
in this podcast.
00:00:18.100 --> 00:00:22.340
Yes, see too, because this podcast is also available with video on YouTube.
00:00:22.880 --> 00:00:23.600
Just take a look.
00:00:24.860 --> 00:00:30.280
So please send your feedback to podcast@testing-unleashed.fm.
00:00:31.540 --> 00:00:35.780
Today I talk with one of the sharpest minds in software thinking, Kevlin Henney.
00:00:36.740 --> 00:00:41.660
His author, speaker and a master of putting things in a perspective, especially when we
00:00:41.720 --> 00:00:42.800
talk about the future.
00:00:44.340 --> 00:00:46.280
Together we looked into the crystal ball.
00:00:46.980 --> 00:00:49.900
Will AI take over software engineering?
00:00:51.240 --> 00:00:58.360
And will be maybe coding look like other in the year 2035 or maybe still like the same as today?
00:00:59.820 --> 00:01:04.800
And what makes good developers stand out even in an AI driven world?
00:01:06.020 --> 00:01:11.600
And finally, why understanding people might be more important than understanding tools
00:01:11.600 --> 00:01:12.260
in the future?
00:01:13.740 --> 00:01:16.740
Are you ready for the time travel into the future?
00:01:17.340 --> 00:01:18.380
So let's dive in.
00:01:18.480 --> 00:01:21.600
Hi Kevlin, nice to have you here on the podcast.
00:01:21.940 --> 00:01:22.960
Yeah, excellent.
00:01:23.660 --> 00:01:31.420
Thank you that you joined here for the OOP and you have a talk in the afternoon today
00:01:31.540 --> 00:01:31.760
I think?
00:01:32.080 --> 00:01:37.600
Yes, so I have a talk that I'm doing the end of the afternoon with Frank Bushman.
00:01:38.260 --> 00:01:42.560
And then I have another talk that I'm doing just solo tomorrow just before.
00:01:42.640 --> 00:01:43.160
Ah yes,
00:01:43.220 --> 00:01:43.900
yes, great.
00:01:44.680 --> 00:01:50.620
I read the abstracts in front of the conference and I saw you had one abstract about the future
00:01:51.220 --> 00:02:00.580
prediction maybe or some possible future for software engineers. Will we work in 2034
00:02:00.580 --> 00:02:00.920
or
00:02:01.050 --> 00:02:01.240
something?
00:02:01.900 --> 00:02:03.520
That's right. Yeah, that's what I'm doing with
00:02:03.520 --> 00:02:05.100
Frank. We're kind of
00:02:05.880 --> 00:02:14.660
doing a little bit of crystal ball gazing. And it's the software engineers playbook 2034. So
00:02:14.660 --> 00:02:22.000
be doing. And obviously, there's a lot we could put in that talk, but it's only one
00:02:22.040 --> 00:02:24.620
hour. So we've actually spent a lot of time deleting
00:02:24.620 --> 00:02:25.760
slides and deleting
00:02:25.760 --> 00:02:27.000
content. So to
00:02:27.100 --> 00:02:29.480
come up with a kind of a smaller core message.
00:02:29.740 --> 00:02:34.420
Yeah, yeah. So that's I want to talk about this also here in this in this in this episode,
00:02:34.940 --> 00:02:40.360
because it's the future is always a part I mentioned, I'm known the future optimist.
00:02:41.060 --> 00:02:46.140
And so I'm very happy to talk about what is your prediction, what is your crystal view
00:02:46.340 --> 00:02:48.580
to the to the future of software engineering?
00:02:49.000 --> 00:02:54.800
Yeah, it's kind of interesting because I may be slightly less of a techno optimist than
00:02:54.820 --> 00:02:55.420
I used to be.
00:02:58.150 --> 00:03:04.960
And the I think my view of the future, and I think myself and Frank have slightly different
00:03:05.060 --> 00:03:07.380
paths on this, which I think is going to make for an interesting talk.
00:03:07.900 --> 00:03:10.540
one of my perspectives when I look at the data,
00:03:12.120 --> 00:03:14.180
it's not going to be as different as people think it is.
00:03:14.320 --> 00:03:14.640
It's going to
00:03:14.640 --> 00:03:17.260
be different in kind of look at the current trends,
00:03:17.440 --> 00:03:18.300
see where those are going.
00:03:18.780 --> 00:03:19.800
Yeah, there's nothing radical.
00:03:21.460 --> 00:03:23.960
There's a few things that are going to kind of shift a bit.
00:03:24.910 --> 00:03:27.260
All you have to do is to think,
00:03:27.400 --> 00:03:30.140
"Okay, if now is 2024, what was 2014
00:03:30.140 --> 00:03:30.720
like?"
00:03:31.080 --> 00:03:31.320
If
00:03:31.320 --> 00:03:34.160
you can remember 2014, what was 2004 like?
00:03:34.180 --> 00:03:36.480
If you can remember 2004, what was 1994 like?
00:03:36.660 --> 00:03:43.740
And I have been in software development for longer than that.
00:03:44.160 --> 00:03:45.920
And so it's interesting to look at the cycles
00:03:45.920 --> 00:03:46.700
and
00:03:46.700 --> 00:03:47.240
then start saying,
00:03:47.300 --> 00:03:50.280
"Oh yeah, there are real differences between how I was developing
00:03:50.280 --> 00:03:50.920
now
00:03:50.920 --> 00:03:51.420
and then."
00:03:51.680 --> 00:03:54.460
And there are also some things that absolutely haven't changed
00:03:54.540 --> 00:03:55.960
or have just moved very
00:03:55.960 --> 00:03:57.060
slightly and
00:03:57.060 --> 00:03:57.720
to look at those.
00:03:57.840 --> 00:04:01.280
And so if we look at things like 2034,
00:04:01.480 --> 00:04:05.640
I mean, one of the ones that I have been going on about to people is just like,
00:04:06.020 --> 00:04:09.320
Programming languages, yeah, they're whatever you're using today.
00:04:09.860 --> 00:04:11.840
That is going to be 80 to 90 percent.
00:04:11.840 --> 00:04:13.400
If you actually look at the data,
00:04:14.540 --> 00:04:15.660
when we actually look at the data,
00:04:16.760 --> 00:04:18.340
the top five languages in use,
Load full transcript
00:04:18.660 --> 00:04:19.680
none of them was developed,
00:04:20.120 --> 00:04:21.320
sorry, that's not true.
00:04:21.519 --> 00:04:23.840
One of them was developed in the 21st century.
00:04:24.560 --> 00:04:24.960
Most
00:04:24.960 --> 00:04:26.220
people are programming in
00:04:26.520 --> 00:04:28.300
languages that were developed in the 20th century.
00:04:28.320 --> 00:04:31.260
If you look at the top 20 languages, it's still there.
00:04:31.380 --> 00:04:33.340
If you look at the top 50, it's still there.
00:04:33.420 --> 00:04:38.900
So in other words, programming language movement is actually really not that big.
00:04:39.000 --> 00:04:43.400
The languages themselves evolve, but the makeup of the languages, no, not really.
00:04:43.490 --> 00:04:46.940
You know, I get a lot of people say, "Oh, yeah, but we'll be all...
00:04:46.940 --> 00:04:50.600
So if I'm programming native, will I be using Rust in 2034?"
00:04:50.840 --> 00:04:52.300
Actually, there's a fairly good chance.
00:04:53.000 --> 00:04:55.320
But Rust is already at this point over 10 years old.
00:04:55.570 --> 00:04:57.380
So there's nobody there.
00:04:57.900 --> 00:05:01.059
There are no languages that were developed in the 2020s
00:05:01.060 --> 00:05:03.760
that are in the top 20 languages of use at this point.
00:05:04.100 --> 00:05:07.760
So, the point there is something's moved much more slowly.
00:05:09.500 --> 00:05:12.660
If we look at other trends in terms of our development,
00:05:13.420 --> 00:05:15.800
Agile development, or at least the name has become very normal.
00:05:17.140 --> 00:05:18.920
The number of people actually doing Agile development,
00:05:19.360 --> 00:05:20.400
it's still pretty low.
00:05:20.880 --> 00:05:23.020
I suspect that that won't change 2034.
00:05:24.400 --> 00:05:26.920
We look at other things, other certain technologies.
00:05:27.320 --> 00:05:29.240
Some people think of 5G as being the future.
00:05:29.260 --> 00:05:30.600
I think of it as being the present.
00:05:31.060 --> 00:05:31.460
So,
00:05:32.220 --> 00:05:33.600
we're looking to 6G, maybe.
00:05:34.180 --> 00:05:35.800
And then we have the other areas,
00:05:36.020 --> 00:05:38.860
which some of which are hype-driven, metaverse,
00:05:40.780 --> 00:05:41.800
cryptocurrency and things like that.
00:05:42.140 --> 00:05:44.740
If we look at just the last couple of years trends on those,
00:05:44.880 --> 00:05:49.660
those are pretty much crashed as a vision of the future.
00:05:49.900 --> 00:05:51.980
They will have potentially a place,
00:05:52.120 --> 00:05:53.520
but it's not going to be a dominating place.
00:05:53.560 --> 00:05:53.640
There's
00:05:53.640 --> 00:05:54.240
no evidence
00:05:54.240 --> 00:05:54.620
of that.
00:05:55.220 --> 00:05:57.720
Web3, people have been talking about it for over a decade.
00:05:58.260 --> 00:06:00.520
By that point, if you look at Web 2,
00:06:00.840 --> 00:06:03.400
Web 2, within the decade of that term being coined,
00:06:03.510 --> 00:06:04.160
it was a thing.
00:06:04.640 --> 00:06:06.260
Ten years on from Web 3 being talked about,
00:06:06.360 --> 00:06:07.300
it's still not a thing.
00:06:07.540 --> 00:06:09.380
And you know what? I don't think it ever is going to be a
00:06:09.380 --> 00:06:09.440
thing.
00:06:09.580 --> 00:06:09.940
There's no
00:06:09.940 --> 00:06:11.940
evidence to suggest we're moving in that direction.
00:06:13.400 --> 00:06:15.680
Cryptocurrencies, central bank, digital currency,
00:06:15.940 --> 00:06:17.520
might become a thing. That's quite credible.
00:06:18.180 --> 00:06:20.380
The rest, everybody's now kind of, yeah,
00:06:20.500 --> 00:06:21.620
it's not treated as currency.
00:06:21.940 --> 00:06:24.120
So again, we don't see any evidence of change there.
00:06:25.440 --> 00:06:26.560
Metaverse is fragmented.
00:06:26.980 --> 00:06:28.180
I don't think we're going to get a metaverse.
00:06:28.180 --> 00:06:30.980
I think we're just going to get a few more AR and VR things.
00:06:31.900 --> 00:06:32.980
And there are certain niches,
00:06:33.920 --> 00:06:35.760
some industrial applications and gaming.
00:06:36.120 --> 00:06:38.060
That's I think that's where it's going to be.
00:06:38.220 --> 00:06:40.080
But is it going to be a thing that people use every day
00:06:40.660 --> 00:06:43.300
in a deep, immersive sense for all of their time?
00:06:44.160 --> 00:06:45.020
Gaming. Yeah.
00:06:45.860 --> 00:06:46.680
And we already have that.
00:06:46.920 --> 00:06:49.540
So in other words, that's a continuation of that line.
00:06:49.860 --> 00:06:51.760
But the one everybody wants to talk about is AI.
00:06:52.020 --> 00:06:53.540
Yeah. Yeah. I'm saving that one.
00:06:53.780 --> 00:06:55.120
That's the one everybody wants to talk about.
00:06:55.160 --> 00:06:55.920
I was waiting for it.
00:06:55.940 --> 00:06:56.180
Yeah, you
00:06:56.180 --> 00:06:56.300
were
00:06:56.300 --> 00:06:56.720
waiting for that.
00:06:57.780 --> 00:06:58.120
I just
00:06:58.120 --> 00:06:59.480
thought I could start with that one now.
00:07:00.140 --> 00:07:01.860
That's the one everybody wants to know about.
00:07:02.020 --> 00:07:04.360
And there are reasons to,
00:07:05.180 --> 00:07:07.600
there are certain things in the broad application of AI
00:07:07.880 --> 00:07:11.700
that are at this point uncertain
00:07:11.940 --> 00:07:15.720
in terms of the relationship between AI and big data.
00:07:15.770 --> 00:07:17.880
And therefore, where did that data come from?
00:07:18.340 --> 00:07:21.240
What are the legal ramifications of that data?
00:07:21.660 --> 00:07:23.720
What are the existing intellectual property laws
00:07:23.930 --> 00:07:24.840
that are being enforced?
00:07:25.300 --> 00:07:27.820
And that's currently going through the courts.
00:07:28.400 --> 00:07:31.160
This question of large data training sets
00:07:31.840 --> 00:07:34.200
and the relationship to copyright.
00:07:36.340 --> 00:07:37.800
There's a lot of interesting
stuff there.
00:07:37.900 --> 00:07:39.940
I can't predict the future of what courts are going to do.
00:07:40.060 --> 00:07:41.300
So, I'm not even going to try.
00:07:43.920 --> 00:07:46.360
But that is something we need to watch over the next couple of years
00:07:46.440 --> 00:07:48.680
because that will influence the future.
00:07:49.760 --> 00:07:52.719
The question of ethical considerations
00:07:52.720 --> 00:07:57.840
on how much of a relationship we have with checking the results,
00:07:58.000 --> 00:08:01.180
particularly when it comes to systems that are automated
00:08:01.380 --> 00:08:03.680
and make judgments that affect human lives.
00:08:04.720 --> 00:08:08.260
This is a question not of technical ability.
00:08:08.640 --> 00:08:11.240
Anybody who is framing it as a question of technology
00:08:11.250 --> 00:08:13.520
has misunderstood how people work.
00:08:13.980 --> 00:08:16.040
This is a question of our involvement.
00:08:16.200 --> 00:08:16.320
This
00:08:16.320 --> 00:08:16.780
is a question
00:08:16.780 --> 00:08:18.320
of what do we want
00:08:18.580 --> 00:08:20.280
and how do we want to shape that.
00:08:20.320 --> 00:08:23.220
It's very much, and I don't just mean we in the development space,
00:08:23.300 --> 00:08:24.380
that's a broad question.
00:08:25.020 --> 00:08:28.760
And we should not just let somebody who's a tech bro
00:08:28.880 --> 00:08:30.120
just tell us what it's going to be.
00:08:30.420 --> 00:08:31.500
No, we have a choice here.
00:08:31.820 --> 00:08:35.159
And the evidence is that if we don't properly take the choice,
00:08:35.700 --> 00:08:37.120
a number of people are going to be disadvantaged
00:08:37.979 --> 00:08:42.560
because that's the very nature of a statistical-based approach to AI.
00:08:42.760 --> 00:08:42.940
It is
00:08:42.940 --> 00:08:43.219
not a
00:08:43.219 --> 00:08:44.860
reason-based approach, it's statistical.
00:08:45.300 --> 00:08:47.400
And the problem with anything that is statistically based
00:08:47.760 --> 00:08:47.920
is it
00:08:47.920 --> 00:08:49.440
represents an image of the past.
00:08:49.920 --> 00:08:52.260
and it represents the most likely,
00:08:52.400 --> 00:08:54.540
but that means it ignores edge cases
00:08:55.000 --> 00:08:55.240
or
00:08:55.240 --> 00:08:57.880
the things that are seen to be less than a majority.
00:08:58.640 --> 00:09:00.280
So we need to watch out for that one
00:09:00.340 --> 00:09:01.720
in terms of the social implications.
00:09:02.120 --> 00:09:04.200
But I think we're already aware of this.
00:09:04.470 --> 00:09:05.600
I don't think that's news.
00:09:06.250 --> 00:09:08.540
I just think that that now becomes a thing.
00:09:08.580 --> 00:09:12.820
And we need to also see how legislation is going to affect it.
00:09:14.700 --> 00:09:18.200
The EU directive on this is one of the first.
00:09:18.840 --> 00:09:23.340
The question is, will it be as influential to the world as GDPR was,
00:09:23.500 --> 00:09:24.180
which has been hugely
00:09:24.180 --> 00:09:24.720
influential.
00:09:25.880 --> 00:09:28.060
And it's not entirely clear that it is.
00:09:28.120 --> 00:09:29.420
It's been a little bit watered down.
00:09:29.570 --> 00:09:33.460
It's probably not going to really take force until at least next year,
00:09:33.730 --> 00:09:36.460
and from a practical point of view, perhaps even 2026.
00:09:36.840 --> 00:09:39.320
So I think that one is too soon to tell,
00:09:39.880 --> 00:09:42.100
but we need to see what other governments are going to do.
00:09:42.260 --> 00:09:45.600
So is there going to be any kind of international consensus,
00:09:46.060 --> 00:09:47.260
or is there going to be huge differences?
00:09:47.760 --> 00:09:49.860
that also tells us something about the future.
00:09:50.480 --> 00:09:52.740
But obviously, what a lot of developers want to know is,
00:09:53.200 --> 00:09:55.780
"What is AI going to do for me or to me?
00:09:56.320 --> 00:09:59.040
Will I have a job in 2034?"
00:09:59.700 --> 00:10:01.600
And I made a prediction last year.
00:10:01.740 --> 00:10:02.920
Actually, I made a few predictions.
00:10:03.060 --> 00:10:05.860
I'm going to rest on these because I'm not normally...
00:10:05.860 --> 00:10:08.440
I always tell people, "Prediction is a fool's
00:10:08.440 --> 00:10:09.880
game."
00:10:10.759 --> 00:10:12.240
And you're most likely wrong.
00:10:12.360 --> 00:10:12.560
So
00:10:12.560 --> 00:10:13.280
I'm going to
00:10:13.280 --> 00:10:15.000
very definitely cherry pick
00:10:15.680 --> 00:10:16.800
the ones that I have got right.
00:10:17.040 --> 00:10:21.000
In 2016, I was asked a question about AI and the future.
00:10:21.200 --> 00:10:23.660
And I said, "Do I think we have a job?"
00:10:24.180 --> 00:10:24.500
"Yes."
00:10:24.680 --> 00:10:28.260
And I got my answer, and it was at MobiConf in Poland in 2016.
00:10:28.420 --> 00:10:30.840
So, you actually find this in the Q&A on the video.
00:10:31.740 --> 00:10:34.560
And I said, "Yeah, developers are going to be needed."
00:10:36.540 --> 00:10:38.340
The concept of development doesn't change.
00:10:38.600 --> 00:10:41.300
All those people who say, "Oh, yeah, we're going to have natural language programming,
00:10:41.380 --> 00:10:42.420
and that's going to be fantastic."
00:10:42.420 --> 00:10:44.620
It's like, you really need to understand history.
00:10:44.800 --> 00:10:46.100
First of all, you need to understand history.
00:10:46.120 --> 00:10:49.240
Then you need to understand the language and you need to go and talk to some customers.
00:10:49.540 --> 00:10:51.400
And then you will realize how safe your job is.
00:10:53.699 --> 00:10:56.520
Because programming is not merely the assembly of syntax.
00:10:57.280 --> 00:11:00.240
It is the application of precision.
00:11:00.580 --> 00:11:02.000
It is the seeking of precision.
00:11:02.140 --> 00:11:04.320
And what is the answer? What is it that I'm trying to do?
00:11:04.899 --> 00:11:09.000
And it turns out that if you
specify something badly in natural language,
00:11:09.000 --> 00:11:11.140
it works out even worse than if you did it in code.
00:11:11.520 --> 00:11:14.620
And we already know, for example, we can actually take
00:11:15.860 --> 00:11:19.700
inspiration from the most widely used programming paradigm on the planet,
00:11:20.460 --> 00:11:21.000
the spreadsheet.
00:11:21.480 --> 00:11:21.860
What
00:11:21.860 --> 00:11:25.200
we know from the spreadsheet is that most people who use a spreadsheet
00:11:25.660 --> 00:11:27.200
do not have a software development background.
00:11:27.640 --> 00:11:30.360
We also know that most spreadsheets are unmaintainable,
00:11:31.320 --> 00:11:32.720
incomprehensible, and buggy.
00:11:33.120 --> 00:11:36.420
If we are saying that the future of software development is
00:11:36.740 --> 00:11:40.460
people who are not software experts doing this stuff,
00:11:40.560 --> 00:11:43.980
your job is safe because that stuff will need to be understood and fixed.
00:11:44.040 --> 00:11:44.320
That's the
00:11:44.320 --> 00:11:44.520
first
00:11:44.520 --> 00:11:44.760
point.
00:11:45.360 --> 00:11:47.100
Spreadsheets didn't put anybody else out of a job.
00:11:47.880 --> 00:11:49.620
They actually create opportunities.
00:11:50.620 --> 00:11:54.640
The other thing is, when we look at AI assistance
00:11:54.640 --> 00:11:55.100
of our
00:11:55.100 --> 00:11:55.480
work,
00:11:55.780 --> 00:11:57.420
and a prediction,
00:11:58.200 --> 00:12:00.680
so in 2016, one of the things I said was,
00:12:00.880 --> 00:12:04.980
one of the things we might see is the balance of our time shifts.
00:12:05.520 --> 00:12:07.260
But I said, and I made a prediction about it,
00:12:07.580 --> 00:12:08.780
you're going to need to get good at testing.
00:12:09.720 --> 00:12:13.620
Because if you are just going to take the first thing that is generated,
00:12:14.440 --> 00:12:16.000
and you don't know what it's supposed to do,
00:12:16.740 --> 00:12:19.020
then guess what? You're going to end up being a maintenance program.
00:12:19.100 --> 00:12:21.600
I made that prediction again last year on Mastodon,
00:12:21.660 --> 00:12:22.720
and I've now managed to retweet that.
00:12:22.840 --> 00:12:24.940
So it's now out there in the written form last April.
00:12:25.620 --> 00:12:29.300
And my observation was that most generated AI,
00:12:29.600 --> 00:12:31.100
the way that programmers are going to use it,
00:12:31.120 --> 00:12:33.020
we've seen how programmers use the tools they're given,
00:12:33.700 --> 00:12:36.040
there is no evidence to suggest it's going to be for the better.
00:12:36.260 --> 00:12:38.920
The majority of developers will create legacy code.
00:12:39.360 --> 00:12:39.560
they
00:12:39.560 --> 00:12:40.540
will now just do it faster.
00:12:40.730 --> 00:12:40.940
>> Yeah.
00:12:41.800 --> 00:12:44.680
>> So in other words, they're going to take away the fun bit.
00:12:44.780 --> 00:12:46.480
This is what I think is so ironic.
00:12:47.000 --> 00:12:50.380
Many developers are going to remove the bit of the job that they enjoy,
00:12:51.040 --> 00:12:52.900
and they're going to create maintenance code,
00:12:53.000 --> 00:12:55.700
and they are dealing with code that somebody else wrote.
00:12:55.710 --> 00:12:56.320
They don't understand
00:12:56.320 --> 00:12:56.560
why.
00:12:57.740 --> 00:12:58.660
So in other words,
00:12:58.820 --> 00:13:03.640
developers that go all in on generative AI to create their own code,
00:13:03.750 --> 00:13:06.060
whether it's a copilot level or full-on chat GPT,
00:13:06.120 --> 00:13:09.660
give me this, are going to discover that they are now maintenance programmers.
00:13:09.940 --> 00:13:11.820
They've taken all of the joy out of their job.
00:13:11.880 --> 00:13:13.800
Well done. Have they become more productive?
00:13:14.260 --> 00:13:15.660
Oh, they'll be making more commits.
00:13:16.420 --> 00:13:17.740
But this is the interesting thing.
00:13:17.780 --> 00:13:21.860
A recent study has shown
00:13:22.200 --> 00:13:26.220
that already there is a downward pressure on code quality on GitHub.
00:13:27.180 --> 00:13:28.460
The study was done by GitClear.
00:13:28.460 --> 00:13:31.120
They published it a couple of weeks ago, so January 2024.
00:13:32.600 --> 00:13:34.400
The quality is dropping already.
00:13:34.600 --> 00:13:37.360
You're ready. And that's what's happening.
00:13:37.660 --> 00:13:38.600
Code churn is increasing.
00:13:39.060 --> 00:13:40.920
What we're finding is there's more duplicate code,
00:13:40.960 --> 00:13:42.160
more copy and paste code.
00:13:42.560 --> 00:13:42.720
The
00:13:42.720 --> 00:13:44.480
quality of the code is already going down.
00:13:44.580 --> 00:13:46.360
And this is what I'd say is early days.
00:13:46.900 --> 00:13:49.460
But the code churn, the idea of having to go back
00:13:49.540 --> 00:13:51.240
to something you just committed because it's wrong,
00:13:51.960 --> 00:13:52.540
that's increased.
00:13:53.419 --> 00:13:55.140
And this is kind of stuff like,
00:13:55.440 --> 00:13:56.560
if you'd asked me a year ago,
00:13:57.160 --> 00:13:58.860
I would have told you this was going to happen
00:13:59.120 --> 00:13:59.240
because
00:13:59.240 --> 00:14:00.440
I know how people use tools.
00:14:00.640 --> 00:14:02.999
- So maybe we need more developer
00:14:03.000 --> 00:14:03.460
or more
00:14:03.460 --> 00:14:04.600
quality assurance.
00:14:04.780 --> 00:14:09.840
>> Yeah. So, the thing is that we need to understand what the relationship is.
00:14:10.260 --> 00:14:12.000
We also need to understand that for some developers,
00:14:12.600 --> 00:14:13.800
they are going to get a huge advantage.
00:14:14.260 --> 00:14:16.320
I've already said, we know these developers.
00:14:16.840 --> 00:14:17.980
They are a particular percentage.
00:14:18.160 --> 00:14:19.080
When they are given a new tool,
00:14:19.160 --> 00:14:20.860
they will get the best out of that tool.
00:14:21.300 -->
00:14:24.900
Then, most developers will be through no fault of their own in
00:14:24.920 --> 00:14:29.640
an environment that doesn't encourage them to do the right thing, and they won't.
00:14:30.140 --> 00:14:31.300
It won't happen by magic.
00:14:31.760 --> 00:14:36.720
And so therefore, what you're going to find is increasing number of bugs,
00:14:37.220 --> 00:14:39.160
increasing code churn, increasing outages,
00:14:39.990 --> 00:14:42.120
therefore, more focus on the development,
00:14:42.290 --> 00:14:44.420
but not necessarily learning the right lesson,
00:14:44.470 --> 00:14:46.560
which is maybe we need to focus on quality.
00:14:46.900 --> 00:14:50.380
Maybe generating the wrong thing faster is not the end game.
00:14:50.880 --> 00:14:53.060
So, I think that by 2034,
00:14:54.020 --> 00:14:55.820
some companies will have realized this
00:14:55.820 --> 00:14:56.480
and will
00:14:56.480 --> 00:14:57.160
be acting on it.
00:14:57.520 --> 00:14:59.000
Those companies will be doing very well.
00:14:59.240 --> 00:15:03.180
Most companies won't have that and will just be micromanaging people
00:15:03.180 --> 00:15:03.980
or putting
00:15:03.980 --> 00:15:04.360
a lot of
00:15:04.520 --> 00:15:05.040
pressure on people.
00:15:05.520 --> 00:15:09.900
In the dangers, actually, software development in some companies may become very unpleasant.
00:15:10.320 --> 00:15:12.280
I don't think it's going to be a job that disappears.
00:15:12.440 --> 00:15:13.360
It may change.
00:15:13.460 --> 00:15:18.040
But I think unless we properly observe this, it's not going to be good.
00:15:19.160 --> 00:15:22.060
So yeah, software development is not going to disappear.
00:15:22.680 --> 00:15:22.780
I
00:15:22.780 --> 00:15:27.559
think it's going to splinter and there will be a real difference between people who work
00:15:27.560 --> 00:15:33.020
in the quality environments, you know, understanding what it is that they're getting from any tool,
00:15:33.140 --> 00:15:35.000
which has always been the challenge.
00:15:35.680 --> 00:15:39.880
And then there are people who are going to be, you know, as it were puppets of the tool
00:15:40.120 --> 00:15:41.800
and very poor management processes.
00:15:42.000 --> 00:15:43.440
So that's my personal prediction.
00:15:44.320 --> 00:15:50.159
I think we have to mention that the software industry and the IT industry is an industry
00:15:50.160 --> 00:16:00.320
which has reached a part they always creating new jobs and new needs of their job.
00:16:01.180 --> 00:16:03.240
And I think this won't stop in the future.
00:16:03.460 --> 00:16:03.800
So yeah,
00:16:04.060 --> 00:16:10.280
the software industry will still get needs the impact and get new people there
00:16:10.280 --> 00:16:11.140
to do this stuff.
00:16:11.200 --> 00:16:11.620
The world,
00:16:11.740 --> 00:16:14.980
the world runs on software, that is not going to that's not going anywhere.
00:16:15.040 --> 00:16:20.140
And the idea, I'm not gonna say it's never going to be a case where somebody is not a
00:16:20.140 --> 00:16:21.860
able to articulate a business need
00:16:21.860 --> 00:16:23.140
and
00:16:23.140 --> 00:16:26.900
then have a meaningful interaction with something
00:16:27.000 --> 00:16:27.460
that's AI.
00:16:27.760 --> 00:16:29.220
But that's not the AI we have now.
00:16:29.840 --> 00:16:34.940
That is at least a decade off before people start doing that because that's not where
00:16:35.000 --> 00:16:36.940
the money is, that's not where the conversation is.
00:16:37.400 --> 00:16:40.780
It's certainly a possibility, but we're a long way from that.
00:16:40.940 --> 00:16:41.680
And the need
00:16:41.680 --> 00:16:43.040
for software is not going down.
00:16:43.360 --> 00:16:46.580
So yeah, I think that that is relatively safe.
00:16:47.820 --> 00:16:51.700
What I've been telling people is, you know, your skills at being precise, your skills
00:16:51.740 --> 00:16:57.200
at being able to test, and your skills at being able to ask the right questions.
00:16:57.420 --> 00:16:58.940
What is it we're actually trying to do here?
00:16:59.340 --> 00:17:00.400
Those have always been
00:17:00.400 --> 00:17:00.640
there.
00:17:01.200 --> 00:17:04.420
But now we're going to realize that they come up, they're much more obviously the stars
00:17:04.459 --> 00:17:04.900
of the show.
00:17:05.600 --> 00:17:05.720
And
00:17:05.720 --> 00:17:08.319
that's where your skills are.
00:17:08.760 --> 00:17:13.540
And honestly, knowing how to work with a programming language or programming languages is still
00:17:13.540 --> 00:17:17.140
absolutely relevant because those are very different to working with natural language.
00:17:18.839 --> 00:17:25.240
And that's the bridge that we've always crossed, the ability to work with the kind of the soft,
00:17:25.339 --> 00:17:28.880
flexible space of humans and business and then say, "And this is what we
00:17:28.880 --> 00:17:29.820
need."
00:17:29.820 --> 00:17:35.260
And to do so in a concept and notation that is utterly precise and fixed and be able to
00:17:35.260 --> 00:17:36.900
say, "Yeah, that's exactly what we meant."
00:17:36.900 --> 00:17:39.020
And importantly, we get the same result every time.
00:17:39.120 --> 00:17:40.080
That's really important.
00:17:40.340 --> 00:17:42.000
And I can -- and importantly, it's empirical.
00:17:42.100 --> 00:17:42.960
I can show you that.
00:17:43.180 --> 00:17:43.820
Here's the tests.
00:17:44.280 --> 00:17:46.420
And here's the data that we see from the runtime.
00:17:47.380 --> 00:17:49.680
All of those things, they're not going anywhere.
00:17:49.870 --> 00:17:50.560
And if anything,
00:17:50.880 --> 00:17:54.320
those are the ones that are going to differentiate individual developers
00:17:54.400 --> 00:17:56.140
in terms of skill and also companies.
00:17:56.740 --> 00:17:57.940
That's where the competition is.
00:17:58.080 --> 00:17:58.180
Yeah.
00:17:58.340 --> 00:17:58.460
Yeah.
00:17:59.000 -->
00:18:03.620
What do you think about collaboration in the teams and in the organization?
00:18:03.650 --> 00:18:09.120
So we are struggling with with H.I. doing stuff together, interdisciplinary teams.
00:18:09.120 --> 00:18:12.160
And so it works sometimes, but not often.
00:18:12.280 --> 00:18:14.940
What do you think, where will the trend go on here?
00:18:16.080 --> 00:18:21.080
I think that this is an interesting one because we have a very much a mix.
00:18:21.800 --> 00:18:28.380
And this is something that we have some companies and some organizations go in one direction
00:18:28.400 --> 00:18:30.260
at the same time as other companies going in other directions.
00:18:30.420 --> 00:18:37.720
So if you go back many decades, software development was done inside of the companies that were
00:18:37.780 --> 00:18:38.380
using the software.
00:18:38.720 --> 00:18:40.280
Everything was bespoke software.
00:18:41.740 --> 00:18:47.840
And the distance between the business users and the developers was naturally short because
00:18:47.900 --> 00:18:50.580
you were in the company where you were actually developing the software for.
00:18:51.280 --> 00:18:54.120
Of course, it wasn't the kind of software that we have these days in terms of scope,
00:18:54.120 --> 00:18:55.640
but it gives us one baseline.
00:18:56.080 --> 00:19:01.600
But in the same era, we also had large companies, institutional style companies that definitely
00:19:01.720 --> 00:19:02.420
kept the software.
00:19:02.840 --> 00:19:08.220
They developed software for other people, whether it was governments or whatever at
00:19:08.300 --> 00:19:08.480
scale.
00:19:08.880 --> 00:19:09.460
And guess what?
00:19:10.180 --> 00:19:12.820
still have that, but we also have a lot of spaces in between.
00:19:13.280 --> 00:19:13.660
So what
00:19:13.660 --> 00:19:17.020
we find is that companies,
00:19:17.300 --> 00:19:18.300
there's the natural agility.
00:19:18.530 --> 00:19:19.640
If you're in a small company,
00:19:19.920 --> 00:19:21.760
there's a natural agility you just get
00:19:21.900 --> 00:19:22.860
by being in a small company.
00:19:23.000 --> 00:19:23.080
- Yeah.
00:19:24.200 --> 00:19:27.340
- If you are in a company where you are providing software
00:19:27.370 --> 00:19:28.620
to people in that company,
00:19:29.000 --> 00:19:31.140
you have an advantage over people
00:19:31.260 --> 00:19:33.400
who have an organizational boundary.
00:19:33.900 --> 00:19:35.160
But also we outsource more,
00:19:35.260 --> 00:19:36.660
so we introduce more organizational
00:19:36.660 --> 00:19:37.100
boundaries,
00:19:37.490 --> 00:19:39.280
and therefore we need to get over that.
00:19:39.300 --> 00:19:43.680
So, it feels like there's a constant churn and renewal
00:19:43.840 --> 00:19:47.100
that some companies are constantly being created
00:19:47.400 --> 00:19:50.540
to serve the needs, the software needs of other organizations,
00:19:50.920 --> 00:19:51.540
but they're outside.
00:19:52.060 -->
00:19:53.700
But agility is about getting as close,
00:19:53.780 --> 00:19:57.260
it's about reducing the distance and communication distance.
00:19:58.140 --> 00:20:00.060
So, we both increase and reduce it
00:20:00.180 --> 00:20:01.500
or find the need to reduce it.
00:20:01.560 --> 00:20:04.780
So, I don't think that's going to change in that sense.
00:20:04.820 --> 00:20:04.920
I
00:20:04.920 --> 00:20:05.260
think we
00:20:05.260 --> 00:20:06.740
are constantly doing that,
00:20:06.800 --> 00:20:09.280
but I think we have many more smaller companies
00:20:09.280 --> 00:20:12.080
perhaps a faster turnover rate of some companies.
00:20:12.910 --> 00:20:14.520
But we also find companies that are large,
00:20:14.550 --> 00:20:16.140
and for them, agility means,
00:20:16.620 --> 00:20:17.860
"Oh, we used to be four layers of
00:20:17.980 --> 00:20:19.000
management before you could talk to somebody.
00:20:19.080 --> 00:20:20.500
Now, we're three, and now we're agile."
00:20:20.500 --> 00:20:23.060
It's just like, "Okay, you guys have still got a long way to go."
00:20:23.060 --> 00:20:26.500
But I think that pressure is always there.
00:20:26.760 --> 00:20:29.520
I think that what we have seen in the last decade,
00:20:29.800 --> 00:20:32.880
particularly as more companies find themselves pulled
00:20:33.080 --> 00:20:37.080
into much more continuous deployment situation,
00:20:37.600 --> 00:20:42.500
is that the downside of that is a lot more pressure individually.
00:20:42.680 --> 00:20:43.720
It's the kind of pressure I was talking
00:20:43.720 --> 00:20:44.140
about earlier
00:20:44.140 --> 00:20:44.320
on,
00:20:44.400 --> 00:20:45.660
that you end up being micromanaged.
00:20:45.800 --> 00:20:47.580
Now, it used to be micromanaged on a monthly basis.
00:20:47.760 --> 00:20:48.860
Now, it's on a daily basis.
00:20:49.400 --> 00:20:52.320
And that can, if not understood,
00:20:53.000 --> 00:20:54.760
as a properly collaborative environment,
00:20:54.900 --> 00:20:57.820
that can actually make for a very unpleasant feeling.
00:20:57.900 --> 00:21:01.540
And you're constantly just bombarded with deadlines.
00:21:02.560 --> 00:21:04.660
But at the same time, I also have some optimism here
00:21:04.660 --> 00:21:09.100
that I think that when I look at other industries and other disciplines,
00:21:09.580 --> 00:21:11.400
I think in software, we talk about people issues
00:21:11.680 --> 00:21:13.700
a lot more than people in other disciplines.
00:21:14.120 --> 00:21:16.980
I think, you know, although we have this reputation,
00:21:17.480 --> 00:21:20.560
and I think it's a reputation that sometimes other people hold of us,
00:21:20.600 --> 00:21:22.640
but we also hold it of ourselves. I don't think it's true.
00:21:22.800 --> 00:21:24.800
I think we spend a lot of time talking about the people stuff,
00:21:25.300 --> 00:21:29.260
more so than many other industries, particularly technical ones.
00:21:29.500 --> 00:21:31.260
We tend to value those.
00:21:31.260 --> 00:21:35.220
We see it as a problem or a systems issue to be understood.
00:21:36.340 --> 00:21:38.040
And you find that, you know,
00:21:38.580 --> 00:21:40.680
the fact that business movements now come out of software
00:21:40.740 --> 00:21:43.700
rather than software being the consumer of business movements,
00:21:43.780 --> 00:21:48.220
it's now the producer of ideas that transform other companies
00:21:48.220 --> 00:21:50.140
that don't consider themselves to be software companies.
00:21:50.260 --> 00:21:53.460
You know, you go out there and people are quite happily using the term
00:21:54.540 --> 00:21:57.180
agile in the broader business context
00:21:57.180 --> 00:22:02.020
where it simply didn't have any meaning or attraction many years ago.
00:22:02.220 --> 00:22:02.540
And that
00:22:02.540 --> 00:22:04.560
we see these ideas going out.
00:22:04.660 --> 00:22:06.840
So I think that we're actually in a very good position.
00:22:07.340 --> 00:22:07.460
So I
00:22:07.460 --> 00:22:08.620
have a little bit of optimism there.
00:22:08.620 --> 00:22:12.520
I don't think, you know, I don't think it's all suddenly going to change overnight.
00:22:12.740 --> 00:22:16.120
But I have some optimism that I think that we focus on people issues
00:22:16.220 --> 00:22:17.900
probably a lot more than a lot of industries do.
00:22:17.960 --> 00:22:18.120
Yeah,
00:22:18.280 --> 00:22:19.600
yeah, yeah. Yeah. Thank you.
00:22:19.640 --> 00:22:21.940
It's a great, great thought on this topic.
00:22:22.620 --> 00:22:29.740
So what do you would you recommend for a QA tester, software engineer to learn and to
00:22:29.820 --> 00:22:30.940
prepare for this future?
00:22:32.700 --> 00:22:38.920
So I think it's a case of that whenever I've been asked this question, I think my answer
00:22:38.960 --> 00:22:45.480
is generally always had the same core and then the dressing is slightly different.
00:22:45.670 --> 00:22:49.540
So the same so let me focus on what is the same core, the foundations.
00:22:50.300 --> 00:22:55.400
There are things that are much slower moving, the foundations, the principles, the deeper
00:22:55.560 --> 00:23:00.940
skills, the idea that what is it that we want from this software?
00:23:01.300 --> 00:23:01.620
And that's
00:23:01.620 --> 00:23:04.960
a high-level question that we frame in terms of requirements.
00:23:05.360 --> 00:23:09.780
But to understand how to test something is to understand what it should be doing in the
00:23:09.940 --> 00:23:10.220
first place.
00:23:10.280 --> 00:23:11.900
There's a cycle between these.
00:23:11.940 --> 00:23:13.080
There's a natural cycle.
00:23:14.060 --> 00:23:14.800
Get good at that.
00:23:15.500 --> 00:23:20.940
good at describing and describing both in natural language but also in code.
00:23:21.320 --> 00:23:22.420
What does that look like?
00:23:22.760 --> 00:23:23.800
What does the right thing look like?
00:23:23.880 --> 00:23:25.120
What does the wrong thing look like?
00:23:26.400 --> 00:23:29.160
Programming languages, they're not really going anywhere.
00:23:29.820 --> 00:23:32.900
They are going to continue very much along the trends that we have seen for the last
00:23:32.960 --> 00:23:34.280
decade, two decades, and so on.
00:23:34.340 --> 00:23:38.060
There's minor shifts every now and then, but nothing huge.
00:23:39.900 --> 00:23:44.400
So you're okay with whatever you're working on, but keep a look.
00:23:44.540 --> 00:23:48.260
If you're using one of the top 10 languages, well done, keep using it.
00:23:48.420 --> 00:23:50.020
But look at what's in the next top 10.
00:23:50.240 --> 00:23:50.480
Look
00:23:50.480 --> 00:23:57.260
to the rest of the top 20 because that may be where the language that will be your
00:23:57.320 --> 00:23:58.660
primary language is coming from.
00:23:59.580 --> 00:24:03.920
The language that you'll be using in 10 years' time probably has, you know, I put very good
00:24:03.980 --> 00:24:08.260
money that it has already been invented and already has some kind of presence if not in
00:24:08.260 --> 00:24:09.500
the top 20, the top 50.
00:24:11.900 --> 00:24:14.280
But also have that idea that you're not just stuck with one language.
00:24:14.420 --> 00:24:20.260
people characterize as, "I am a Java programmer. I am a C# programmer." Take a step outside
00:24:20.340 --> 00:24:23.960
that, say, "Yeah, that's the language I'm using this year." But look around, you're
00:24:23.960 --> 00:24:30.260
obviously using lots of other languages. Give those first-class status as well. Yeah, I
00:24:30.260 --> 00:24:36.300
mean, that's JavaScript as well. So, give them first-class status. So, those core skills
00:24:36.400 --> 00:24:36.640
there.
00:24:38.020 --> 00:24:42.939
Understand that the tooling that you're using today is probably -- the tools move surprisingly
00:24:42.940 --> 00:24:51.020
fast in some cases. Some are very slow, some are very fast. If you go back 10 years, Kubernetes,
00:24:51.400 --> 00:24:51.980
people will be like,
00:24:52.100 --> 00:24:54.040
"What?" But
00:24:54.040 --> 00:24:57.100
at the same time, if you're in the Java space, hey, guess
00:24:57.160 --> 00:25:01.980
what? JUnit was developed in the 20th century. So, some things don't change. But there are
00:25:02.220 --> 00:25:05.360
the idea that many of the tools you're looking at, they're going to improve, they're going
00:25:05.360 --> 00:25:10.339
to change. And you move job, you may discover there's a different tool ecosystem that has
00:25:10.340 --> 00:25:15.340
popular where you are. Look to open source. Open source is where a lot of these ideas
00:25:15.680 --> 00:25:20.000
are coming from. So, I generally tell people, you know, keep your feet on the ground.
00:25:20.200 --> 00:25:20.340
Look
00:25:20.360 --> 00:25:20.860
for the foundations.
00:25:21.000 --> 00:25:23.560
What are the core principles? What are the good ideas in software development
00:25:23.620 --> 00:25:29.160
that have stood the test of time? And then what are those skills as related to me? And
00:25:29.180 --> 00:25:32.560
then what are the exciting new bits that I can hold on to? And where do I find them?
00:25:33.140 --> 00:25:33.280
That
00:25:33.280 --> 00:25:34.020
would be my general
00:25:34.020 --> 00:25:34.480
advice.
00:25:34.580 --> 00:25:35.440
It's a balance.
00:25:36.020 --> 00:25:38.140
Yeah, thank you very much for this tip.
00:25:38.200 --> 00:25:43.100
I think the community will join it and then go on to it.
00:25:43.960 --> 00:25:46.180
Yeah, so we are already done with the time.
00:25:46.280 --> 00:25:50.440
So, but I thank you very much for this insights,
00:25:50.520 --> 00:25:51.780
for your thoughts about the future.
00:25:52.000 --> 00:25:54.500
It's, I'm very satisfied now.
00:25:55.120 --> 00:25:57.680
I have some things about, I think about
00:25:57.680 --> 00:25:58.500
the next days
00:25:58.600 --> 00:26:00.900
and I wish you a very good conference here
00:26:01.120 --> 00:26:03.520
and good talks and a good time here.
00:26:03.810 --> 00:26:04.080
Thank you.
00:26:04.080 --> 00:26:04.500
Thank you very much.
00:26:33.919 --> 00:26:35.320
(orchestral music)