No. People do need to know about your product. What appears to be a (_very_ sad and at the same time telling about the human condition) fact is that business people ("decision makers") apparently can't spot blatant, extremely low quality and low effort, marketing-driven snake-oil, laughingly ignore it, and do a 5 minutes google search to find something better by themselves, perhaps with the apparently tremendous effort of having to click a Github link (which provides actual proof, or at least a test, of actual skill), and from there click on the heavily, kind of honest marketing driven website (i.e. it has images) that would allow them to verify the quality of the product.
It literally contains as much information as anybody could potentially hope for (public information anyhow - excluding interviews and the like). If they happen not to be able to distinguish between a “page does not exist” (90%~ of cases IME, ie no GH account), or their ego is so inflated that they cant be bothered to spend 2mins asking their CTO (or dont even have one or trust them), thats a different story and its on them. The signal is there.
I think you just explained why my software engineering career was always so disappointing. I was not getting my "product" to the right eyeballs. I also think maybe I just wasn't cut out for the work in certain ways. I'm a fantastic coder, but so little of the work these days depends on fantastic coding skills! In fact, it's not even that important to companies. What top devs do is manage complexity, but I've always hated corporate complexity because most of it seems contrived.
> I've always hated corporate complexity because most of it seems contrived.
It is contrived, but it’s usually contrived on behalf of the person who signs your checks, in my experience. Process exists to serve the owners not the worker bees.
