I don't doubt that if it were very obvious that you were interacting with an AI, many people may be put off by it.
On the other hand, isn't an adaptive exam like the SAT also an instance of you having to work with some automated system to somehow "prove" yourself to that system?
I'd even argue that what I am proposing (I wrote the linked piece in case it wasn't obvious) ultimately leads to someone reading the chat transcript to gauge candidate suitability. That should reduce the stigma of having to abase yourself to an AI, no?
As an Indian, Rajpopat’s this comment struck a chord -
> Some of the most ancient wisdom of India has been produced in Sanskrit and we still don't fully understand what our ancestors achieved. We've often been led to believe that we're not important, that we haven't brought enough to the table. I hope this discovery will infuse students in India with confidence, pride, and hope that they too can achieve great things.
I can definitely attest to wondering why a country so old hasn’t added much to human scientific advancement. Maybe the knowledge is locked away behind hard to penetrate language.
Even in the modern era, the country has done tons of important research especially in medical fields.
This is also disregarding the work of Indians who did a ton of amazing research outside India.
But otherwise, if your question is why they haven’t contributed as much in a relative sense versus western countries, maybe you’ve forgotten, but India has been subjugated for many centuries, under various rules. The Mughals, the British, the Dutch, etc…
It’s one of the youngest countries today if you count from when it gained freedom. It took many decades for it to be financially stable and regain much of the infrastructure needed to compete with the west.
So as an Indian myself, I’d urge you to put your countries history in context instead of putting it to some ancient texts locking it away.
The destruction of Twitter as a viable tool for grassroots coordination _was_ the point of Musk buying Twitter with the help of sovereign funds of Arab countries.
IndieHackers used to be such a brilliant resource for genuine conversation and camaraderie. I think the homepage layout revamp with a hundred different columns and tabs and tags and sh!t completely ruined the earlier ethos.
I remember posts routinely getting dozens of comments and responses. Nowadays, if a post gets low double digit comments, it is doing very well. Sad, imho.
Yeah tbh I think they just gave up on it. It's running on autopilot these days with very little being done to turn it back into an actual community instead of a place where all you see is dead or dying low effort moneygrabs.
I thought I was the only one that felt this way about the homepage revamp.
There’s also no effort to tone down excessive self-promotion posts and posts that instead of kindle discussion on-site, they link out to third party sites.
Yeah, it’s just a spam sink nowadays. I guess Stripe figured that not a lot of indiehackers were converting into stripe customers so they decided to let it die of neglect.
I don’t think it was ever snappy and I’ve had an account there since 2017-18. It’s slow compared to other sites but not that much slower than it was say 2-3 years ago.
She asked it to generate a practice emergency medicine board question.
It left off some necessary vital signs from the scenario, then in the answer concluded that the patient had severe pneumonia and should be treated with a specific antibiotic.
Based on the prompt, the pneumonia probably wasn’t severe, antibiotics weren’t warranted, and even if they were, the antibiotic specified was completely wrong.
It looked fine to me—completely plausible. It took an expert to spot the flaws.
She also asked it to explain the work up for a febrile neonate. The answer again sounded plausible to me. But she said it sounded like a clueless med student trying to BS their way through an answer.
India's timing on "Make in India" couldn't have been more fortuitous. The Modi government started hyping Make in India in 2019, if memory serves. Nothing came off it for a while until things started moving in 2021. And now, by 2022, India seems poised to take over some manufacturing from China.
Make in India was hyped most in 2015-2016. It was always considered a failure. Recently government introduced PLI and DLI schemes which helped get some manufacturing rolling.
People generate false memories, experience phantom pain, see blue or gold depending on the angle of an outfit, and other such brain blips because of the brain making up a reality to fill in gaps. In that light, GPT-3 is behaving much like a human brain.
Executives ascend the power/respect ladder by persuading, selling, influencing, meeting, communicating, negotiating with people, and winning over others. Now you have this tech person who has achieved similar power/status by not being good at any of those things. Tech people gain power/respect by studying, doing, building, understanding technology. People tend to like/respect people with qualities they want or respect. Reminds me of the Oppenheimer and Groves situation in which both sides must gain mutual respect for each other to be successful. https://www.atomicarchive.com/history/manhattan-project/p4s2...
Even mid managers have expressed similar concerns to me about finding it difficult to work with tech. E.g., a product manager has complained to me that they wanted a feature built which would have had a direct revenue impact but were stuck because the tech team wanted to "triage" which she didn't understand.
Sounds to me that we need a "tech-to-normal" language translator.
Triage isn't a word that came out of tech, though. It's a term from the medical field, specifically for trauma care, and effectively means prioritisation under pressure.
A product manager really should know and understand this, because it's not like it's impenetrable tech jargon. They should also be the ones making those prioritisation calls, albeit with a solid understanding of the real trade offs.
In a situation like this there can be multiple reasons for the mismatch, none of which have anything to do with needing a language translator. For instance, is the product manager trying to force through that feature without moving out the team's other work to match? If so, then they will obviously get the 'triage' demand and be forced to make a priority call.
I've seen that too often in my career, where from the PM/PO side a feature or improvement is 'obvious' but because they won't take on the political battle of moving out a team's other feature work that's less valuable they either force the team to work beyond their capacity or, if they have more backbone, to refuse outright.
Or is the team intransigent and inflexible, and trying to protect low value but more technically interesting work? Then that, too, is a problem and needs to be solved through incentive changes and other measures, because it's just as unhealthy.
> A product manager really should know and understand this, because it's not like it's impenetrable tech jargon.
It's not tech jargon but it's a medical term, that has to do with people possibly dying or wounded soldiers that can't be handled, and now we're using it in tech? Ignoring the ridiculous overexaggerating that is, this is exactly the kind of jargon that techies will get mad at managers for using.
Just say what you want. "We have other priorities, how does this fit with those, and what item will have lower priority now?"
Except that the semantic shift of triage to also meaning any under pressure prioritisation of too-scarce resources, including in a project sense, is decades-old and predates its usage in tech. This is a case of tech adopting business jargon, not the other way around.
Even if the product manager wasn't familiar with the term itself, they'd surely be familiar with the idea of prioritising incoming tasks by importance and value and moving out work with lower scores. A simple question should've allowed them to link the word and the concept in their heads. This is unlike true tech jargon, where both the word itself and the underlying concept might be completely unfamiliar to anyone outside of tech and difficult to understand.
You shouldn't have to explain prioritisation to a product manager.
Aren't PMs supposed to have an elevated communication skillset compared to ICs? I don't think it's too much to ask for a manager to know what the word "triage" means in a planning context, or to look it up. Particularly a product manager; understanding that stakeholders have multiple different priorities and navigating that situation is the essence of their job.
Perhaps we're misinterpreting and the team was just stonewalling. That happens sometimes with certain teams, sometimes it's because they're chronically understaffed. However, that's obviously no representative of the "tech" (i.e. software) role as a whole.
Triage is usually a non-tech word (QA/Customer Support normally). We need a human-to-human language translator, and it exists, it is called a question.
Then its monetisation started. It isn’t yet as bad as SMS spam but inching towards parity.