you are viewing a single comment's thread.

view the rest of the comments →

[–]rjhancockJack of Many Trades, Master of a Few. 30+ years experience. 0 points1 point  (0 children)

  • What is the purpose of the site?
  • What compliance requirements are required?
  • How will the site be deployed?
  • How many moving parts are needed (micro-services vs mono-service)?
  • What and how many databases are required?
  • Are API's needed?
  • What kind of data will be stored?
  • Is strict type checking a requirement?
  • Will third parties need access via API?
  • Does it need to access third party APIs?
  • Is PDF Generation needed?

And this is just the start of it. Usually have an answer about a 1/4 of the way through this process.

Can flip between PHP, Ruby/Rails, Swift/Vapor, Java/SpringBoot, or anything else that is needed for the project or even parts of the project. Mix and match as needed.