[devwastaken]

Thank you for that story. Though not related to a corporate environment, I've been going through something similiar after a few personal projects of mine have fell through, voiding me of some resume material for a switch in software environment for now. Failure is very important to build up knowledge and experience, but at some point I got lost in the details that you can't research, in the important bits that make software 'work' well and are architected nicely enough to be used professionally.

[tukelully]

Do you mean that you spent to much time with not much to show and now have an apparent gap in work history? Is it more of a present feeling of being lost in the weeds of those projects?

[devwastaken]

More of, the software I'm working with doesn't have a clear direction of how to build things 'properly' and not hack together solutions. Really all software has that problem if you're not experienced enough. For example, its like getting started building a SaaS by yourself so you can work at a company that develops them. The experience the individuals working for a company is going to far surpass your own, so you gotta throw yourself at the wall anyways trying to make it all work, and be an example you can point employers to and tell them all about how you use tests and deployments and handle data and such.