Yes, anyone from Thoughtworks will use plenty of buzzwords. They are the original source for some of them that being the case I don't think she's saying anything we haven't really heard before but just summarizing the same old. 1) postpone big decisions if you can until you know better 2) ease of change, the ability to deploy without huge pain and talk about the system with biz people, etc. all depend on ease of understanding 3) put tests where they can tell you if you're breaking someone else's code 4) don't focus on that which is most broken, focus on what's costing you the most in terms of sleep or velocity 5) talk to business people in their own language so they can understand why what you're saying is important to them too So all in all very familiar common sense stuff.
@@nyrtziWhile this may be the same old for some, this definitely isn't the case for others. For example, I work for a client which insists on not making changes to the architecture as described after implementation has started. I.e. they are not allowing any significant changes because they are highly risk-averse. Watching videos like these gives me new ideas on how to conver the intentions behind allowing changes in your architecture and why this is important. Sometimes its not "what" people are saying, but "how" they're saying it. As for the "buzzwords". I didn't hear any buzzwords in this talk. Only words that carry a very specific and applicable meaning in the context they are meant to address.
ChatGPT approved ❤🎉
Buzzword salad
Could be worse
what is your point?
You'd have to be a person who eats your vegetables to be able to understand it.
Yes, anyone from Thoughtworks will use plenty of buzzwords. They are the original source for some of them that being the case I don't think she's saying anything we haven't really heard before but just summarizing the same old.
1) postpone big decisions if you can until you know better
2) ease of change, the ability to deploy without huge pain and talk about the system with biz people, etc. all depend on ease of understanding
3) put tests where they can tell you if you're breaking someone else's code
4) don't focus on that which is most broken, focus on what's costing you the most in terms of sleep or velocity
5) talk to business people in their own language so they can understand why what you're saying is important to them too
So all in all very familiar common sense stuff.
@@nyrtziWhile this may be the same old for some, this definitely isn't the case for others. For example, I work for a client which insists on not making changes to the architecture as described after implementation has started. I.e. they are not allowing any significant changes because they are highly risk-averse. Watching videos like these gives me new ideas on how to conver the intentions behind allowing changes in your architecture and why this is important. Sometimes its not "what" people are saying, but "how" they're saying it.
As for the "buzzwords". I didn't hear any buzzwords in this talk. Only words that carry a very specific and applicable meaning in the context they are meant to address.