I've since worked with some brilliant devs who were too smart for their own good and a lot of that came down to the difference between being able to create a solution and being able to explain a solution. There's a reason I hold Richard Feynman in very high regard, and it's down to his ability to pluck things from a very high shelf and hand them to 'shorter' people.
The last person to find his way onto my Do Not Hire list, was one of these too smart but inarticulate folks. Since that list is only about half a dozen people over almost 30 years, I think that says a lot about his character and what an absolute bull in a china shop he was. I'd need an Uber after discussing his many flaws over beers. Or maybe a stomach pump at the ER.
I don't share them with my hobby communities because I don't want to hear feedback because I don't want these finished projects to become eternal projects.
That's cool you're able to make what you want with that tech.
* Cardsphere (Magic card trading website) wishlist to inventory comparer * Scryfall (Magic card database) search result CSV Downloader * Cube Tagger, an app to easily tag cards with function tags for easy categorizing in cubes (boardgamified collection of Magic cards)
The vibe coding part is wonderful because I can "make" the software I want. However, it always takes hours of runs to get to where I need it to be because I'm unpracticed at project planning. I constantly hit critical edge cases and UX problems.