Still waiting to see effective solutions being implemented.
Would you be interested in an open ended first date sim? It could be voice so you get used to voice; one issue I have is I can type well but the brain circuits don't trigger the same way when talking.
Possibly start with an interested date at lower difficulty - someone who asks you the questions and coaches you into interesting answers. Then ramps up to shy/unfriendly where you have to work to get them engaged.
Lonely? Why not talk to machines?
Grim.
When people say they're unattractive, often it's not because they're ugly. Ugly is a disadvantage, but not the biggest one.
For both men and women, it's usually because they lack confidence. Or they're boring. Or sleazy. If you're getting into a first date and not a second, you're likely attractive enough on the 'resume', just messing up on the actual date. You might be saying something wrong. You might be delivering a good joke the wrong way. Sometimes it's just saying things in the wrong order.
The longer they go without some form of success, the less confident they become.
I thought the diagnosis was fairly clear; sorry for jumping straight to pitching a cure. This is a good example of saying things in the wrong order.
Are you looking because you're lonely, bored or just because that's what you think is expected?
"Thanks for being honest and I wish you the best with your search.
If you have a moment, would you be able to give me a few suggestions on how I could improve? Is it something obvious I can work on but just not aware of? Like my breath stinks? Or clothes don't fit properly? Or I come off as rude or closed off? Of course, no pressure to answer. Just trying to figure out how I can improve myself. Thank you."
What are the multiple approaches you've tried?
Sample size issue?
Your framework’s intriguing. If it can map this to clear business outcomes (e.g., ‘X% faster delivery in 3 months’), I’d test it. What’s your angle—systems thinking, behavioral psychology, or something else?
P.S. For context: I lead eng at a Series B SaaS co. My ‘stuck’ example: Tech debt costs us ~20% velocity, but ROI arguments fail with revenue-focused execs.
The problem you're trying to solve is not that features get more prioritisation, but your estimations doesn't reflect the reality and your code-review process is broken as engineers are not spotting growing technical debt and refactoring opportunities and think that someone should give them a permission or create a ticket to work on that.
This is engineering culture 101 (look up the boyscout rule in software engineering).
Here is a definition of my mental illness: https://www.mayoclinic.org/diseases-conditions/schizoaffecti...
Here is some more: https://www.bridgestorecovery.com/schizoaffective-disorder/l...
Employers do not like me having it because it makes it harder to do work and some days are worse than others. Management just doesn't understand my mental illness so I am on disability because I cannot hold down a job.
/s
