Apart of specific domain-related things (geo, physics, mapping etc) , read general software books. Maybe some philosophy too.. as software is (medium of) knowle

Apart of specific domain-related things (geo, physics, mapping etc) , read general software books. Maybe some philosophy too.. as software is (medium of) knowledge, and studying knowledge is.. philosophy. Winnie the Pooh and requirements-engineering? Find other people working on similar/related topics, connect with them, offline or online. Do not fear being THE Tech Guy in the company.. just do not be over-confident / arrogant. Doubt quick-wins, check, prove things. 30 years ago such one-programmer-per-company was a normal thing. My reading recommendations are below, but that's just what i have found good.. not exhaustive list. i found some of those only after 11 years doing stuff by myself, and saw i have been inventing hot-water in many "wrong"-but-somehow-working ways, so what.. Better than only applying miracle recipes you don't understand. https://www.svilendobrev.com/rabota/ https://www.svilendobrev.com/rabota/ https://www.svilendobrev.com/1/ https://www.svilendobrev.com/1/ And, most important, have fun!