Hacker News Reader

Totally agree with that. CTO needs to be creative so any "walkthroughs", best practices, etc should be based on logical conclusions coming out of project scope and goals.

Any ways to standardise it are deemed to produce illiterate "CTOs" who follow the notorious saying about a man with a hammer looking at every problem as a nail. There is a fair share of people like this in IT

View on HN

> "walkthroughs", best practices, etc should be based on logical conclusions coming out of project scope and goals.

Would love to see real examples of this thought process... i.e. of the form "we have these requirements, so we chose this and that, etc."

Your question is way too broad to answer it in few sentences... Normally what I'd do is analyse the project as much as possible (goals, planned growth, market, etc) then build schema with each components challenged with few similar services. Then re-analyse it again from financial perspective and possible technical debt. Then ask to review it someone else to avoid my biases holding me from optimal solution.

From what I see nowadays, it's more like, hey we have a project... Let's do it with AWS it has a ton of cool features!

(substitute AWS with GC, Azure or anything of your choice)

Reply on news.ycombinator.com