On choosing technology: I would say choose battle-tested technology, rather than boring and especially what you know. Sometimes the jump is well worth it if wh

On choosing technology: I would say choose battle-tested technology, rather than boring and especially what you know. Sometimes the jump is well worth it if what you know is not a particularly good fit. As an example, I recently had to create a backend and I went with Go. My original plan was to use java (because it's boring), or nodejs (what I "know" because I used it most recently). Nodejs is risky, stuff breaks down all the time in the js ecosystem and the ts issues put me off. Java otoh, puts a lot of emphasis on spring/sping-boot, which I hated, and I wasn't sure that the other microframeworks had enough popularity simply because of how java is used. Go has been a terrible experience to learn and write. But stuff like simple static builds that can easily be deployed or that the ecosystem is geared towards microservices, or the simplicity that the go culture emphasizes (even though the language itself is not simple) has paid off in dividends. Or if I was doing any kind of ML, AI, or data-processing, I'd probably choose Python.