undefined | Better HN

0 pointsboltzmannbrain5y ago0 comments

> "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."

0 comments

jesterson5y ago

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)

j / k navigate · click thread line to collapse

0 pointsboltzmannbrain5y ago0 comments

> "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."

0 comments

jesterson5y ago

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)

j / k navigate · click thread line to collapse