Looking for books & other references mentioned in this video? Check out the video description for all the links! Want early access to videos & exclusive perks? Join our channel membership today: ruclips.net/channel/UCs_tLP3AiwYKwdUHpltJPuAjoin Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇
Wow, a really great talk 😃!!! Especialy the 'economic constrains' part explains a whole lot of things happening in the software development world. Thx Btw: 29:56 made me smile as we had the same discussion shortly 😂
So how to prepare an application for expansion without design? Should the design be based on loose coupling to such extreme that in the future, expansion of the application can be smooth and easy? Thx for this material
I am, I do, and if you’re a developer that understands how to navigate human connection and economics beyond the dev team and tech department you’d be a great hire.
51:19 made me smile very hard. -“What? In six months from now, I'm gonna have software and it's gonna do exactly what it does today!? - Eh... it's the best case...
I'm unsure of the point Kent was making when comparing Product-led and Engineering-led orgs. Presumably sepaeate examples, but then suggested they need to 'come together' to get each 'party's needs met'. This felt like a false dichotomy; but what _did_ he mean here? I can understand if the example was internal teams _at the same org_... Excellent observations about the folly of up to date documentation. Why don't leaders, even in tech, understand this?? Documentation won't fix the culture.
He means in the same company. Engg org wants code quality and architectural improvements. Prod org wants features. It's usually how almost all companies are structured. This is not a false dichotomy!
Why do the more documentation a library or a framework have, the more successful they are? Why does nobody like to adopt an undocumented product? Why does it need to be different in companies?
Looking for books & other references mentioned in this video?
Check out the video description for all the links!
Want early access to videos & exclusive perks?
Join our channel membership today: ruclips.net/channel/UCs_tLP3AiwYKwdUHpltJPuAjoin
Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇
Great to hear Kent
Wow, a really great talk 😃!!!
Especialy the 'economic constrains' part explains a whole lot of things happening in the software development world.
Thx
Btw:
29:56 made me smile as we had the same discussion shortly 😂
I feel like this is a superb summary of all three sections of Tidy First? Thanks Kent!
So how to prepare an application for expansion without design?
Should the design be based on loose coupling to such extreme that in the future, expansion of the application can be smooth and easy?
Thx for this material
Thanks for sharing!
If you are employer and believe in this talk and looking for a software engineer to hire, let me know. I'd love to work for you!
Ditto!
I am, I do, and if you’re a developer that understands how to navigate human connection and economics beyond the dev team and tech department you’d be a great hire.
51:19 made me smile very hard.
-“What? In six months from now, I'm gonna have software and it's gonna do exactly what it does today!?
- Eh... it's the best case...
Great stuff!
We're still in the stone age of software
I'm unsure of the point Kent was making when comparing Product-led and Engineering-led orgs. Presumably sepaeate examples, but then suggested they need to 'come together' to get each 'party's needs met'. This felt like a false dichotomy; but what _did_ he mean here? I can understand if the example was internal teams _at the same org_...
Excellent observations about the folly of up to date documentation. Why don't leaders, even in tech, understand this?? Documentation won't fix the culture.
He means in the same company. Engg org wants code quality and architectural improvements. Prod org wants features. It's usually how almost all companies are structured. This is not a false dichotomy!
Why do the more documentation a library or a framework have, the more successful they are? Why does nobody like to adopt an undocumented product? Why does it need to be different in companies?