I think if you set expectations that you both will be learning together (about the tech) as you go and that there 100% will be some unknown roadblock you come a

I think if you set expectations that you both will be learning together (about the tech) as you go and that there 100% will be some unknown roadblock you come across it might help. Everyone feels like an imposter and that is a good thing compared to being over-confident and unaware that you are implementing things in a poor manner. My advice would be to start small and follow agile principles as you go. You don't need formal SCRUM or other methodologies if you are the solo dev but you should build things in vertical stacks. By that I mean as an example: a feature is logging into the system, build that out so it is ready to ship. Sure you don't have other features at this point (its just an example) but you should have the UI, server-side handling of data and database parts all figured out to the point that you could ship it if you want. It's like breaking a large math problem down into more manageable parts - same thing with developing the software. Small, shippable, testable parts. Figure out your deployment process, this often isn't taught in CS and is more of an "ops" thing. This will help make it easy to ship new things into your environments AND to roll it back if things are messed up. It is liberating to know you can just type a couple commands and restore things - you feel more free to make mistakes.