Hi Mark, Very nice tips. Pick your battles. Pick your battle if it concerns you. Give value to business and help ship product to market fast. Thank you.
Good one Mark!!! I always waiting for your Monday video, this time get early on Saturday itself ;) One suggestion - at the end of every video, summaries your whole video with bulleted key points and with conclude commentary. Sometimes as a viewer we lost sometimes and forget the actual topic key points.
Great tips again Mark. On the developer buy-in tips, do you ever feel that if you involve the devs too much, or too often, that you may end making yourself 'redundant' if the devs end up eventually always saying 'well we could have come up with that idea! Why do we need an architect to come up with ideas??' 😬
Interesting observation, but in my experience it is still about guidance, leadership, and the breadth of knowledge a software architect brings to the table. In some cases, particularly for small projects with an experienced team, the architect should play the role of a facilitator and generally not get in the way of a senior development team.
Love it, valuable techniques, Thanks Mark.
Really super useful presentation Mark. Thank you very much for sharing.
Great tips Mark, thank you!!!
Hi Mark,
Very nice tips.
Pick your battles. Pick your battle if it concerns you.
Give value to business and help ship product to market fast.
Thank you.
Good lesson Like always ❤️
Good one Mark!!!
I always waiting for your Monday video, this time get early on Saturday itself ;)
One suggestion - at the end of every video, summaries your whole video with bulleted key points and with conclude commentary. Sometimes as a viewer we lost sometimes and forget the actual topic key points.
Super usefullll, negotiation is all. Thanks a lot!!!!!!!!!!!!!!!!!
Great tips again Mark. On the developer buy-in tips, do you ever feel that if you involve the devs too much, or too often, that you may end making yourself 'redundant' if the devs end up eventually always saying 'well we could have come up with that idea! Why do we need an architect to come up with ideas??' 😬
Interesting observation, but in my experience it is still about guidance, leadership, and the breadth of knowledge a software architect brings to the table. In some cases, particularly for small projects with an experienced team, the architect should play the role of a facilitator and generally not get in the way of a senior development team.