the current stack is Java (spring) on the Atlassian Suite (bitbucket, jira, confluence) - there's no love for that platform within the teams I'd take over, but I'm curious to know how others do it and what they'd recommend.
Personal Bias':
SCM/CI: Gitlab
Documentation: I prefer `docs/` in the repo's themselves, but there is a need for something more architectural; maybe mediawiki is fine?
Task Management: Notion or Monday
PL: Golang + some python glue
Build system: Bazel (if anything)
Structured DB layer: Cockroach
------
But I'm extremely open to other ideas.
I know everything should start with "what problem am I trying to solve" but there has to be some sensible defaults here? right?
I'm trying to not choose tools that make people miserable, I only have experience with tools that make people miserable. The scale is pretty small.
Small team: notion
Big team: notion
Huge team: notion
FYI: I love and use notion.
But scale affects tools. Employee knowledge affects viable tech stack. It is all truly dependent on context. The thing about being a CTO/CPO etc is that you are the one that has to weigh the trade-offs and make sensible "defaults" based upon your context.
Edit: For task management, issue board etc. it’s probably best to let the team(s) choose/vote for what they enjoy working with, rather than prescribe it from the top. Your process is more important than what task management tool you happen to pick
rewritten from ground up
Now you have two problems.
For programming languages, what about C#, Rust, Python, Julia, R, or C++? Any particular pros and cons?