Taking Back "Software Engineering" • Dave Farley • GOTO 2020
Вставка
- Опубліковано 25 лип 2024
- This presentation was recorded at GOTO Oslo 2020. #GOTOcon #GOTOoslo
goto-oslo.com
Dave Farley - Continuous delivery and DevOps pioneer, award-winning author, and founder and director of Continuous Delivery Ltd.
You can find more content like this on Dave’s "Continuous Delivery UA-cam Channel": / @continuousdelivery
ABSTRACT
Craftsmanship is not enough
Would you fly in a plane designed by a craftsman or would you prefer your aircraft to be designed by engineers? Engineering is the application of iterative, empirical, practical science to real-world problems. Craftsmanship is a wonderful thing, and as a reaction to the terrible abuses of the term Engineering in software development Software Craftsmanship has helped in our learning of what really works.
The term "Software Engineering" has gained a bad reputation. It implies "Big up-front design" and "Mathematically provable models" in place of working code. However, that is down to our interpretation, not a problem with "Engineering" as a discipline.
In recent years we have discovered what really works in software development. Not everyone practices approaches like Continuous Delivery, but it is widely seen as representing the current state-of-the-art in software development. This is because at its root CD is about the application of an iterative, practical, empirical, maybe even science based approach to solving problems in software development. Is this a form of software engineering?
Software isn't bridge-building, it is not car or aircraft development either, but then neither is Chemical Engineering, neither is [...]
Read the full abstract here:
goto-oslo.com/2020/sessions/1...
RECOMMENDED BOOKS
David Farley • Modern Software Engineering • amzn.to/3GI468M
Dave Farley • Continuous Delivery Pipelines • amzn.to/3rjetdi
Dave Farley & Jez Humble • Continuous Delivery • amzn.to/3ocIHwd
Dave Farley & many more • Software Architecture Metrics • amzn.to/3M3XqG5
/ gotocon
/ goto-
/ gotoconferences
#SoftwareEngineering #Programming #DaveFarley #ContinuousDelivery
Looking for a unique learning experience?
Attend the next GOTO Conference near you! Get your ticket at gotocon.com
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
ua-cam.com/users/GotoConf... - Наука та технологія
One issue I see here is that the popular science narrative of what science is like mostly ignores the idea of science being an evolving tradition contained in books and other texts through which experts develop and maintain a consensus on what are considered the best theories, why and in which context. Peer review, literature review and dealing with questions of methodological validity are just as much part of the scientific method actually employed by researchers as any empirical testing. It's precisely the limitations science places on itself that makes it so effective and on the other hand the reason why humans need science to produce reliable information is exactly because humans as individuals and communities have such a hard time trying to be rational to any extent.
This talk should be the launch pad for revamping all software engineering textbooks, including the SsaS software engineering textbook from Berkeley. We should really begin by explaining what problems are unique to software engineering.
Having said that, just like Electrical Engineering (closest cousin to Software Engineering) isn’t just about methodology, but have some basic domain knowledge if you will, such as control theory, signal processing, hardware architecture, circuit design and device physics, shouldn’t we as nail down some tech topics every software engineer should possess, such as software architecture, data structures and algorithms, operating systems, programming languages, CICD?
Fantastic presentation.
Apply an engineering mindset to amplify creativity and increase quality and speed.
Thank you
I Always remember my teacher on "Introduction to Engineering": Anyone can do what an engineer does, they will just take 3 times the time and spend 3 times the money.
Which is of course complete bulls..t. I have seen apps written by non-engineers that took 10x the time, but resulted in 100x the complexity, no tests, and 100x as many bugs as properly engineered software. With no complex requirements whatsoever. This statement only works if you take people into account that have no business in calling themselves engineers but do anyway.
7 minutes in and I'm really liking the level of the presentation.
You should check this dude's youtube channel
Thank you for taking us back to the first principles.
such a good presentation! thank you!
This dude is a genius
39:26
I just want to make game's
What do you mean by "just"😄