Excellent as always. Only feedback would be it was a bit like reading a book backwards with the section headings at the end. Great material/insight though.
There is good statement but moslty buzzwords and good on paper as for modern web application. Yes to testing business logic and testing UI but not testing the whole with the web involve also is a pitfall.
Great talk with a new perspective. I would have wanted an idea/suggestion of how to achieve a folder organization structure that depicts project purpose.
Good keynote, but there wasn't much info on how to relate this stuff back to the PHP world. Possibly because of the fact, demonstrably, the speaker doesn't really use PHP, and at one point (can't remember exactly what was said) treats it with a little contempt, which is a shame. Nevertheless, the talk was full of good advice, but it's kinda rubbish that we still need to be told this stuff. This talk is sadly a requirement, but it shouldn't be.
Fantastic talk. This is the type of keynote I'd like to see more of at technical conferences. I've watched it before on YouTube, but getting a live refresher was great.
Uncle Bob was awesome, as usual. I struggle teaching my teammates these concepts and move the "model" away from the MVC paradigm into DDD mindset, which totally fits the architectural perspective of the speaker.
So I think I discovered my issue with Uncle Bob's analogies. They (to me) seem to rely heavily on the idea of software architecture being relatable to real world architecture when in fact the two are fairly distinct.
Real world architecture, when I walk into a building I have to instantly know such things as where the exits are and be able to find and coordinate myself with a party and possibly find and locate things that aren't in my immediate vision. Software has no real world analogy to this type of problem. In addition, a building is required to accommodate a greater variety of use cases and number of different capabilities/ages/etc of humans. A building may one day be a mall with an open area and in another day be a spot for an auction or a fashion runway or a concert. Software rarely has to accommodate this many different uses cases for the same overall software product. Also buildings, are constructed and engineered using an almost completely waterfall approach, with almost nothing decided at the last minute. The idea of delaying for instance how many floors or even as simple as what materials the floors of the building will be made of until after you poured the foundation is laughable, yet that is exactly the principle we should attempt to achieve in software.
The software engineering/architecture principles are good and valuable, the issue is the analogy causes me to just be frustrated with the whole talk and to find myself poking holes in the talk rather than learning something new.
Great Keynote. He effortlessly and engagingly mixed a highly technical discussion about architecture design with a relatable message about keeping things simple and understandable. He laid out a clear strategy for breaking down interface elements into testable entities, which can be difficult. I wish there was a video of this talk, so I could re-watch it.
Comments
Comments are closed.
Absolutely amazing talk. Mixing a lot of good information with a very nice and pleasant way of delivering the talk. Thank you!
Excellent as always. Only feedback would be it was a bit like reading a book backwards with the section headings at the end. Great material/insight though.
Outstanding talk. Would love to get a video and slides to share with my team.
Enchiladas!
Great keynote! Amazing way of covering a very technical topic but making it approachable and engaging.
Hmm, we should have some kind of standard for requests and responses to make this work. :-P
Brilliant
Good and interesting talk! I was fascinated...
Excellent talk. Good material and great presentation.
Funniest!!
Such a great keynote! I could listen to Uncle Bob talk all day.
There is good statement but moslty buzzwords and good on paper as for modern web application. Yes to testing business logic and testing UI but not testing the whole with the web involve also is a pitfall.
Great keynote, and food for thought
Interesting talk and a few new insights.
Very good presentation!
At first I was not sure where he is going with all that.
At the end I realized that I am already practicing what he was talking about.
Another amazing keynote!
Great talk with a new perspective. I would have wanted an idea/suggestion of how to achieve a folder organization structure that depicts project purpose.
Good keynote, but there wasn't much info on how to relate this stuff back to the PHP world. Possibly because of the fact, demonstrably, the speaker doesn't really use PHP, and at one point (can't remember exactly what was said) treats it with a little contempt, which is a shame. Nevertheless, the talk was full of good advice, but it's kinda rubbish that we still need to be told this stuff. This talk is sadly a requirement, but it shouldn't be.
Fantastic talk. This is the type of keynote I'd like to see more of at technical conferences. I've watched it before on YouTube, but getting a live refresher was great.
Uncle Bob was awesome, as usual. I struggle teaching my teammates these concepts and move the "model" away from the MVC paradigm into DDD mindset, which totally fits the architectural perspective of the speaker.
So I think I discovered my issue with Uncle Bob's analogies. They (to me) seem to rely heavily on the idea of software architecture being relatable to real world architecture when in fact the two are fairly distinct.
Real world architecture, when I walk into a building I have to instantly know such things as where the exits are and be able to find and coordinate myself with a party and possibly find and locate things that aren't in my immediate vision. Software has no real world analogy to this type of problem. In addition, a building is required to accommodate a greater variety of use cases and number of different capabilities/ages/etc of humans. A building may one day be a mall with an open area and in another day be a spot for an auction or a fashion runway or a concert. Software rarely has to accommodate this many different uses cases for the same overall software product. Also buildings, are constructed and engineered using an almost completely waterfall approach, with almost nothing decided at the last minute. The idea of delaying for instance how many floors or even as simple as what materials the floors of the building will be made of until after you poured the foundation is laughable, yet that is exactly the principle we should attempt to achieve in software.
The software engineering/architecture principles are good and valuable, the issue is the analogy causes me to just be frustrated with the whole talk and to find myself poking holes in the talk rather than learning something new.
interesting talk
Great Keynote. He effortlessly and engagingly mixed a highly technical discussion about architecture design with a relatable message about keeping things simple and understandable. He laid out a clear strategy for breaking down interface elements into testable entities, which can be difficult. I wish there was a video of this talk, so I could re-watch it.
Awesome talk! Very engaging.