Almost everything he hawks causes misery for software developers, like his whole multi-year spin for Microservices, he's turned refactoring into a fetish (honestly there are people at my dayjob who have been "refactoring" the entire 3 years i've been here) and now hes blogged multiple times about platform teams - which - having been on one - don't work. I see him as a very damaging character.
Well intentioned, i'm sure, but I don't think he has good ideas.
In my experience, it's worked out terribly when a company treats a platform team as a catch-all for any back-end service regardless the business domain. On the other hand, it's seemed to work reasonably well when the team has a narrow (and very clear definition) of which services they own and why.
That said, I've never worked directly within a platform team as an engineer, so maybe it just appears that way as an outsider.
I'm primarily looking at leadership roles, but would consider engineering work on a consulting/project basis. ---------------------------------------------------------------------------------- Location: NYC Remote: Either Willing to relocate: No Technologies: TypeScript, JavaScript, React.js, Next.js, Node.js, React Native Résumé/CV: https://timcarlock.com/resume.pdf Email: 06fiddler_zircon@icloud.com