I think it was a mistake stuffing the views inside a controller. This made it easy for programmers to cram everything into one place. There should have been a controller responsible for routing events and let anyone take action with respect to responsibility and intent.
Wowza. This was recommended by my coding bootcamp, and I was a bit skeptical, but DANG it delivered. Love this! I'm 45 and got my first job in tech 3 months ago. "Age doesn't matter." The right mental posture and attitude does.
@@emilioalvarado3487 I started from scratch at 43. Slowly ramped up my own personal study over the last year at my previous job, then did a web dev bootcamp at 44, and leveraged hiring connections through people at the bootcamp to land a tech job. Loving it!
This was humblingly informative. Starting my role as a Leader in an Engineering unit & it’s daunting to see how much there is to learn as it impacts the life of so many people directly. Please make more talks like this that aren’t fluffy
Very good talk! The only thing I disliked is the is the MVVM-C term (same thing with MVC-N) I really don't see the need for adding lettes to the pattern acronyms every time we incorporate a new pattern og change or architecture, I feel this is what leeds to new developers thinking that in MVC every piece of code should in one of those letters (at least thats what I thought for a long time). If I want a separate network layer in MVVM-C should I start calling it MVVM-C-N ? og just accept that all architecture evolves along with the progress of the app when we learn more about the domain. Architecture is not something that can be condensed into an acronym.
Interesting that he is not much aware of agile practices in his own teams, I would presume that as Director you should influence on how to get the work moving forward
Not a cool thing to say to a stranger who had the courage to be interviewed on stage from a faceless RU-vid account. Were you on his team or how did you arrive at this conclusion?
Your point about providing clear overall context for a screen particularly stood out for me. While I’ve been designing the individual elements of my app screens with VoiceOver in mind, I definitely need to go back to review the screen contexts for overall clarity. Thank-you.
