if we can see the slides more often, it will be great, or at least put slides on half of the screen, what is the point of showing the speaker all the time with a green background?
I was not mad. In fact, if you wonder around goto conference videos, you will see I am not the only one who is disappointed at the editing method you guys decide to use. Goto has some good stuff and I am certainly thrilled that I have been following the talks in the last couple years; I just hope the editing can be better.
I also cannot pay attention to a video in one tab and follow a PDF in another. I also prefer to have the slide as part of the video, there is no reason to have full focus on a speaker in a presentation video unless the speaker is displaying something.
Now is 2020. I can say almost all of what she said turns out to be true, and even more advanced. Artificial intelligence and blockchain were not mentioned in this presentation
A fine talk, although I must write a fundamental critical point with several critical sub-points: Fundamental criticism: Mary's definition of software engineering's future is at least software engineering's present, if not already its history and so she might have instead called this talk "Modern day software engineering methods" or something similar. Why? 1. Scaling out: cheap, powerful VMs have made the very "web scale" distributed systems she mentions as the future the norm in the present, e.g. Elastic, Hadoop, Cassandra, whatever and frankly many of us are already trying to intuit what's next. 2. Infrastructure as Code: There are no companies not at least partially on this path and the vast majority are at least at the configuration management stage and likely fathoming, or testing with, serverless architectures. 3. The new technology stack, i.e. micromization (I hope I just made that up). Anyway, every dev team is aware of microservices though many execs may stand in the way of a monolith reengineering. 4. The "Three Ways" (CICD, Problem Solving teams, Scientific Method): I don't know any software engineering team that isn't aware of how Jez and Gene have influenced their work, at least when it comes to CICD (and CICD has been around for decades and Jez says as much directly). Let me leave you with a thought I stole from Grady Booch (IBM Watson) about the future of software engineering: The history of software engineering is about us telling systems what to do; the future of software engineering is about systems learning to do on their own what we told them to do in the past. I would expect a talk titled "The future of Software Engineering" to make similar hypotheses based on a synthesis of technologies, trends and probability.
Great talk! She reminds me of Uncle Bob Martin, the way she talks the way she walks on the stage...She is Uncle Bob Martin's identical twin sister, may be :) But, seriously, a great talk.
Queueing theory, which is the mathematical study of how different variables affect how long you have to wait in line (i.e., a queue) for someone to be available to serve you. The field is about a hundred years old, and has lots of real-world applications (how many cashiers should you have at a grocery store, or pumps at a gas station?) that translate directly to the problem of figuring out the most efficient price point for servers: fewer/faster/expensive vs. more/slower/cheaper.
If anyone would like to view the article she mentioned about Software Engineering of Big Data Systems: ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7420514 it's free it seems.
Dont Agree. u cant see the unemployed engineers , the redundant software writers dealing in archaic architecture that has been replaced with auto gen code. Not leaky, buggy rubbish. Todays database is about to change ..begins 2018 ..hardware redesign by 2020.
I had a lot of respect for Mary as I really liked her idea about lean software development. But it is very clear to me that she has no understanding about databases and treats them like the majority of other developers - it is something we need to get rid of or at least minimise our dependancy on. Databases are not legacy components that need to be reinvented. They serve a function for the entire company well beyond the APIs that developers write. For example, once the API is written and the data is stored, that data can go into a data warehouse where a BI specialist or data scientist will use. The latter know SQL very well and it is why SQL is not going anywhere. Even big data/noSQL products are putting SQL back in. The future of the intersection of microservices and databases will be sharding and ETL on SQL database as well as volatile caching, document databases, graph databases and text searching. Similar to what google spanner is doing and similar to the 'reactive microservices' pattern. The not-invented-here especially when you don't understand what you are trying to reinvent is going to lead you down a rabbit hole where the only result is that you will learn first hand why people chose to do what they did in the first place.
I don't think you are giving her enough credit for her vast experience. I'd wager she knows more about databases than you do. Saying "she has no understanding about databases" is flatly disrespectful and, to my eyes, rude. Being nice matters, you should totally try it.
Ok, lets try it. With all due respect to Mary and her very insightful book about lean software development, it does not seem that her knowledge of database reflects how companies use it beyond the scope of the software development cycle. Her efforts to simplify database for the ends of the developer, actually 'silo' access to the database behind developers and does not allow that data to flow through the company to business users, business intelligence, management... etc.
@@JonathanLevinTKY I agree with you. She simplifies the roles of the databases a little too much. She lost me when she said API's replace databases. This is a really big statement.
![Tee Grizzley - Detroit (Feat. 42 Dugg) [Official Video]](http://i.ytimg.com/vi/aeKfTtt0x14/mqdefault.jpg)
at 42:15 "We need to move from Delivery Teams to Problem Solving Teams" Best MOTTO for the year!
Highly informative. I appreciate the quality of information and insights gained.
Looks like an interesting talk. Anyone else notice that her arm keeps disappearing?
same issue here, i thought this was a combo tech-talk-magician-illusionism
if we can see the slides more often, it will be great, or at least put slides on half of the screen, what is the point of showing the speaker all the time with a green background?
Hi Hong, we don't enjoy seeing you mad. Did you know that we usually link the slides as a downloadable PDF in the video description?
I was not mad. In fact, if you wonder around goto conference videos, you will see I am not the only one who is disappointed at the editing method you guys decide to use. Goto has some good stuff and I am certainly thrilled that I have been following the talks in the last couple years; I just hope the editing can be better.
The link (for most of other videos as well) are broken :(
I also cannot pay attention to a video in one tab and follow a PDF in another. I also prefer to have the slide as part of the video, there is no reason to have full focus on a speaker in a presentation video unless the speaker is displaying something.
The links were temporarily broken, please try again.
very inspirational talk - need a lot of things to learn I guess
Great speech - lots of wonderful insights - great content - great suggestions for further reading.
amazing talk ... a lot to think about...
Now is 2020. I can say almost all of what she said turns out to be true, and even more advanced. Artificial intelligence and blockchain were not mentioned in this presentation
Brilliant!!! This should put an end to Agile Approach soon and for ever and revive scientific, experimentation for widest range of solutions.
Please 🙌🏻
Amazing talk, thank you!
Good presentation. Basically i allready thought about about some of themes. But firstly i heared everything in one place and so structured.
A fine talk, although I must write a fundamental critical point with several critical sub-points:
Fundamental criticism:
Mary's definition of software engineering's future is at least software engineering's present, if not already its history and so she might have instead called this talk "Modern day software engineering methods" or something similar. Why?
1. Scaling out: cheap, powerful VMs have made the very "web scale" distributed systems she mentions as the future the norm in the present, e.g. Elastic, Hadoop, Cassandra, whatever and frankly many of us are already trying to intuit what's next.
2. Infrastructure as Code: There are no companies not at least partially on this path and the vast majority are at least at the configuration management stage and likely fathoming, or testing with, serverless architectures.
3. The new technology stack, i.e. micromization (I hope I just made that up). Anyway, every dev team is aware of microservices though many execs may stand in the way of a monolith reengineering.
4. The "Three Ways" (CICD, Problem Solving teams, Scientific Method): I don't know any software engineering team that isn't aware of how Jez and Gene have influenced their work, at least when it comes to CICD (and CICD has been around for decades and Jez says as much directly).
Let me leave you with a thought I stole from Grady Booch (IBM Watson) about the future of software engineering:
The history of software engineering is about us telling systems what to do; the future of software engineering is about systems learning to do on their own what we told them to do in the past.
I would expect a talk titled "The future of Software Engineering" to make similar hypotheses based on a synthesis of technologies, trends and probability.
Best talk of the year. Thank you
Great Talk!! Awesone insights about software engineering!!
wasn't it
Scale Up moves to Scale Out (in the first half of the speech)
and then in the final summary slide
Scale Out >> Scale Up?
Scale Out >> Scale Up in both...
Great talk. Really enjoyed listening.
Great talk.
What about machine learning and AI
Really good presentation, thank you very much.
Thanks for the talk.
very good Explanation . thank you very much
What an awesome talk!
OMG I though she was 1 arm less until 2:30, I jumped!
Stimulus, Response...I swear some guy named Mills came up with that in the 70s.....
Wow that was an awesome talk
thank you..
very inspiring talk!
I fail to see how this is the future. Many of the ideas were proposed 10 years ago. Lean. Agile. XP.
The future is to get rid of Agile.
Great talk!
In 1996, I was in my second year of web programming.
End-to-end feedback.
Great talk! She reminds me of Uncle Bob Martin, the way she talks the way she walks on the stage...She is Uncle Bob Martin's identical twin sister, may be :)
But, seriously, a great talk.
very interesting
GE sold off Predix. Maybe that's not a failure, and maybe Amazon has monopoly power in Cloud, but the sense was that it was a failure.
Just had an 8.5 minute commercial that had no skip button. Yikes!
gorgeous move!
Great, But too abstract to understand. I will improve enough to understand everything she's saying.
The future is to get rid of Agile
OK Google: Tell me of a time when a process that took 5-6 years at amazon took a few months at another company.
better for all
what is a chewing theory?
Queueing theory, which is the mathematical study of how different variables affect how long you have to wait in line (i.e., a queue) for someone to be available to serve you. The field is about a hundred years old, and has lots of real-world applications (how many cashiers should you have at a grocery store, or pumps at a gas station?) that translate directly to the problem of figuring out the most efficient price point for servers: fewer/faster/expensive vs. more/slower/cheaper.
If anyone would like to view the article she mentioned about Software Engineering of Big Data Systems: ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7420514 it's free it seems.
www.exp-platform.com/Documents/ExP_DMCaseStudies.pdf
Dont Agree. u cant see the unemployed engineers , the redundant software writers dealing in archaic architecture that has been replaced with auto gen code. Not leaky, buggy rubbish. Todays database is about to change ..begins 2018 ..hardware redesign by 2020.
The future of software engineering is AI working for a human architect... until it takes over the architecture, too.
No. You are a nobody. Let a software engineet make such an assumption, not you.
@@Vekikev1 Hello Should I chose software engineering now or other fields
I had a lot of respect for Mary as I really liked her idea about lean software development. But it is very clear to me that she has no understanding about databases and treats them like the majority of other developers - it is something we need to get rid of or at least minimise our dependancy on.
Databases are not legacy components that need to be reinvented. They serve a function for the entire company well beyond the APIs that developers write.
For example, once the API is written and the data is stored, that data can go into a data warehouse where a BI specialist or data scientist will use. The latter know SQL very well and it is why SQL is not going anywhere. Even big data/noSQL products are putting SQL back in.
The future of the intersection of microservices and databases will be sharding and ETL on SQL database as well as volatile caching, document databases, graph databases and text searching. Similar to what google spanner is doing and similar to the 'reactive microservices' pattern.
The not-invented-here especially when you don't understand what you are trying to reinvent is going to lead you down a rabbit hole where the only result is that you will learn first hand why people chose to do what they did in the first place.
I don't think you are giving her enough credit for her vast experience. I'd wager she knows more about databases than you do. Saying "she has no understanding about databases" is flatly disrespectful and, to my eyes, rude. Being nice matters, you should totally try it.
Ok, lets try it. With all due respect to Mary and her very insightful book about lean software development, it does not seem that her knowledge of database reflects how companies use it beyond the scope of the software development cycle. Her efforts to simplify database for the ends of the developer, actually 'silo' access to the database behind developers and does not allow that data to flow through the company to business users, business intelligence, management... etc.
@@JonathanLevinTKY I agree with you. She simplifies the roles of the databases a little too much. She lost me when she said API's replace databases. This is a really big statement.
She is out of breath so fast