kostarelo

What are some impressive setups you've seen or you've implemented on locally replicating a microservices architecture with local DBs and other backend dependencies.

I'm looking into docker-compose with remote docker-compose yaml files but I'm not sure of how solid is going to be.

Our services are mostly Node.js based services and dockerised already. Production environment is setup on AWS ECS.

What would be the right indexes (or anything else) to evaluate a country's performance over a specific time period?

I would like to evaluate my country's (Greece) last government performance and what real effect it had over the country's wealth and the general population.

That is only for personal knowledge purposes and not for a professional/academic inquiry or something.

Thank you

Dear HN, I'm a software engineer with several years of experience in web development and generally SaaS products.

In all my experience, the agile product development process has been pretty much the same. For example, in my latest role, the PM will verbally or in a very short and vague document describe something that we want to build to the Engineering Manager (or to one of the engineers) and then they will gather the engineers to refine the problem by discussing possible solutions and as an outcome we will produce tickets that are ready to be picked up.

While this process has been working fine, we always had the same complaints, a) very vague requirements b) no documentation/history produced during the process and as a result, in a few months we will have forgotten what we've done and why c) communication between engineers and stakeholders is rare and as a result, many times, the stakeholders will receive something else that what they actually needed d) very poorly written tickets description exactly because the communication is poor.

I've been trying to figure out what could be a better approach but because my experience has been the same, I'm not able to sell any alternative to the team/stakeholders. I've reading about user stories and other agile-related solutions but I'm struggling to understand the nitty gritty details of such a process.

What is your current process and if possible, describe it in as much detail as you think someone that has never done it before will understand.

Thank you

Sometimes I'm being impressed by a very thorough, well structured, always up to date documentation page.

Stripes', Slacks' and Jiras' documentation pages are the first three that comes into my mind (I'm sure people will have different experiences but still I'm sure lots of them will agree with me that these are exceptionally good documentation pages).

I've never been in an organisation where we were maintaining such pages and I'm not sure what is the process of writing them. On the contrary, my experience have usually been a state where the product requirements, the actual end product and the documentation being somewhat out of sync.

How would you describe the process of maintaining a great product documentation page?

Thanks :)