1 new brain, please!
"Would you like to try the digestive tract remapping first? It's a lot less invasive, but, if it doesn't work you'll be depressed the entire time you're making a mess of yourself."
Readit Newsblarghyblarg commented on Japan pharma startup to begin human trials of tooth regrowth drug in 2024 english.kyodonews.net/new... · Posted by u/anigbrowl
Today is the day that florianwueest learns that "spoken language" is actually a really controversial topic lol
Seriously though, I bet finishing up this project felt great, then posting it to HackerNews was a huge dopamine rush, and now... everybody's just pointing out issues left and right because they accidentally stepped on a dozen landmines that are irrelevant in day-to-day life for 99% of us but entirely relevant when you post to an audience of millions.
> You're reading the idea of language policing as some actual thing, like people are hanging over someone watching every word they say.
I’m not sure where you got that impression. I didn’t say anything like that anywhere. You’re just making assumptions in service to what appears to be some axe grinding.
the point here being: the perception of being surveilled by "language police" on its own is either anxiety inducing or the result of an existing anxious disposition.
The actual act of "language policing" is also going to induce or worsen an existing anxious disposition.
apotheosis in terry davis
RIP. Likely the Platonic Ideal of an abrasive programmer.
I'd put mid 00s Linus Torvalds as the apotheosis. Despite being an incredibly abrasive person, he has left a mark on history.
Swore at or swore while talking to? There's quite a big difference. I don't see profanity as inherently abrasive, and some of the biggest dickheads I've met in workplaces didn't swear much at all (some were of the Professor Umbridge type, so kept up an air of perfect professionalism)
literally right there in the comment. "swore at regularly".
Anyways, I definitely agree that swearing isn't the same as abrasive, but swearing at people is definitely an abrasive trait. Also agree that some of the biggest dickheads around keep up an air of professionalism.
This tells me more about the impacts of anxiety writ large than it highlights the problem of “language policing.”
"Oh, THEY are policing my language. THEY are watching everything I say!"
You're reading the idea of language policing as some actual thing, like people are hanging over someone watching every word they say. It certainly might be true in some offices or with some coworkers, but, I'm pretty sure feeling that your every word is policed is closer to a form of anxiety than an actual problem in most offices.
Or, your coworkers are basically bullying you over minor nitpicks, which will keep you in a state of mild anxiety.
Either way, having to monitor your every word is definitely closer to being anxious than not, and is definitely going to have some impact on your performance.
That’s a pretty big leap IMO. What gives you that impression?
https://www.sciencedirect.com/science/article/pii/S187704281...
It's really not a big leap, though. People who are afraid of violating a code of conduct because they're "under the watch of language police" are basically experiencing a form of anxiety that may or may not have a basis in reality.
Being afraid of being sent to the HR DEI board because you named a process 'Child1' then ran Kill(Child1) ... or any less obvious scenario similar to that ... is not going to do great things to your ability to work.
Swearing in the comments is for goodie goodies. Bad assed programmers swear in public apis like class names, functions, variables, and documentation!
The best programmers I've worked with swore at their coworkers regularly, but never in their code.
They were not great people, and I'd happily kick them in the face if I would encounter no legal or professional repercussions, but, there definitely does seem to be some correlation (in my experience) between being abrasive and being a skilled programmer.
It’s about time that tech companies go in and clean up Hollywood. There needs to be a year of efficiency imposed on these spendthrifts. The Hollywood elite needs to be held accountable, if they are not delivering ROI and maximizing shareholder value.
It should not cost so much for a TV show or movie. YouTubers with more views are producing hit after hit with nothing more than an iPhone these days. Directors should streamline their operations with AI, and on-screen talent and team members should be paid an hourly wage that is only time they are actually in front of a camera, delivering value. If they really believe in a project, they can choose to give up cash compensation for the privilege of purchasing options of a TV show. This helps align incentives and optimize risk to capital and stakeholders to do more and deliver faster with less.
Amazon and others should think about relocating production to areas outside of California where the costs are out of control and in a locale where the regulatory environment is optimized for business returns. TV shows and movies need to be evaluated on a quarterly basis and KPI’s should be enforced at all levels. To minimize risk, investment into AI that can be trained to emulate consumer watching behavior is needed and production should be run in a data-driven agile process.
If a show can’t be monetized, it isn’t worth being produced. Entertainment needs to be in the service of moving ad inventory, growing or retaining paying subscribers, or improving conversion of existing profit centers.
I honestly can't tell if you're an arts supporter writing satire, or a bean counter who is serious.
so, I can't reply to your latest message because it's too far down but...
Let me just hop on my wifi and browse the web. Lets do it on a computer from 1999. 2000. 2001. 2002. 2003. 2004. 2005. 2006. 2007. 2008... etc, etc.
Why is it that every couple years from 2012 onwards, doing the same thing keeps taking longer, even with new hardware, without the same revolutions in quality and experience that came with that new software previously?
...
you completely missed the relevant part with the "1999" part. The relevant part is the "2012" part.
Things used to get better, do more, and faster.
The last 15 years, the "do more" part has been less and less useful, and the "faster" part has turned into "slower" in a number of ways.
Software engineers are relying on an increase in hardware performance to pick up their slack, and that line is running out quickly, and there will be many years ahead where we're cleaning up over a decade of laziness.