Ask HN: First time starting a greenfield project at work. Seeking advice
In a few day I'm about to catalyze a new greenfield project at work, together with one other colleague (we'll be starting a new fullstack team, to which more developers will join in the near future. The team will work on this project full time).
We will be creating a web based Decision Support System that will mechanize a process currently done manually by domain experts (they basically look at a printed map with some interest points, and make decisions based on certain constraints and priorities).
To my understanding, there's currently a pretty basic specification and UX designs. From the technical aspect, almost no decision were made, so it's mostly up to me and other developer catalyzing the project. (Our company using mostly Angular, so we'll probably use it as the frontend framework - but it's up to debate just like anything else).
We are expected to start some-sort of development in a few days. Our team will build the core app, while a dedicated team will work on a basic algorithm to support decisions. We will also interact with multiple services & data sources within the company.
I would love to hear your thoughts about the aspects of starting a greenfield project from scratch, including but not limited to technical and interpersonal aspects (technical considerations, choosing a stack, development process, interactions with product owners, future users, teammates and other teams within the company, team culture, bootstrapping, etc..)
I'm looking for any piece of wisdom I can get, and would love to hear ANYTHING you have to share on the subject. Not just advice, but also your own experiences or anything else you think might be insightful or worth sharing. Will greatly appreciate any input.