I like the post, but I was surprised with this use as well, I thought it was an anachronism at this point in any context. I remember it being used to refer to "rice rockets" or modded cars in the late 90s, early 2000s, but it fell out of use in any circles I'm in by then, but it must have survived in some community. It'll probably be hard to get an honest answer without doing your own research since it's been (I think reasonably) labeled as derogatory here, as those using it may not be aware/think of it as such.
I hear the term “ricer” fairly often when someone refers to a two-door honda with a comical spoiler and fat fenders, for example. Definitely has overlap with the rally car body aesthetic. It’s simultaneously a derogatory term and a badge of honor worn by the ricer subculture.
I did not know the etymology or literal meaning of the term, though. I appended my vocabulary list after reading this.
I saw someone using it on the top of the parking garage at Disney land. It just circled around but I found it fascinating to watch and am looking forward to when it can go down the ramp :)
To NT people not conforming to or recognizing/acknowledging social structures anchors your cognition at an adolescent level where that type of behavior is acceptable. Teens are expected to conform and some people on the spectrum can be completely “normal” in every other way, but if you asked that person to show up to a job at 8am every day or to do X socially expected thing, they’d probably just go find someone else to talk to, hence the “functioning at a 12 year old level.” I consider this to be oppressive social pressure and I’m lucky I was privilege enough to live this way without being shamed or tormented by my family. We should all function at the level of a 12 year old.
I get your point but I wouldn’t consider things like not being able to show up at work “functioning at a 12 year old level”, and i don’t think society would either.
Plenty of “neurotypical” adults suck at showing up to things on time, especially at 8am. Plenty of adults throw full-on tantrums or otherwise act like children in certain situations. Plenty of college students don’t know how to do simple things like wash their clothes or cook or keep their dorm clean. Honestly a lot of people can barely function alone and keep their shit together, and I wouldn’t be surprised if that person was one of them, but we don’t look at them like 12-year olds.
I agree - I was using a specific example but in practice I think it's a number of a class of things like this that pile on and look a lot like executive dysfunction, and the label is put on these people by NTs, not by themselves. I had no problem showing up to work every day at 11am, fwiw, and was lucky enough to have a lot of jobs that didn't think too hard about schedules, but for folks not so lucky, not fitting the average in a number of ways will get you very crude labels. Those labels are to give their caretakers power over them in the eyes of society/legally.
Agreed. These labels work because for the most part the legal system allows them to, they are ways for caregivers/parents to maintain control over someone that they think should be different.
Ok that subject I appreciated this thread which pointed out that despite propaganda on both sides, journalists are allowed to freely report the truth of what they see, unlike in Russia. Of course we all know that in the heat of the moment truth can be subjective but the absolute stranglehold the state has over media in Russia is a very different thing than pro-Ukraine war propaganda.
I think they mean micromanagers. I thrived as a middle manager of a remote team that was always distributed across three time zones. I’m not a micromanager and I built my team with that in mind, so my focus was hiring, onboarding, long term planning, and mentorship.
Maybe there’s a two dimensional chart here, but my best managers have been leaders, in which case they became mentors, or they’ve been service oriented, in which case I and my peers were up-managing them. The ones who are trying to herd cats come off as shrill, and nobody respects them. Fears them maybe, but no respect.
Problem is that if you’re up-managing your boss, they aren’t up-managing their boss. I’m sure there’s a Law in there somewhere. The leader types tend to know what’s what and shield the team from bullshit so they can get busy making the boss look competent in every other area. You can talk your way out of a lot of stuff when people are happy with the rest of your results. Delay tactics if nothing else. Sorry we can’t work on bullshit #372 right now because we’re busy being awesome on feature #784. Come back in a month or two (then cross your fingers to see if they still remember or are focused on bullshit #381).
Service-oriented would be when they make themselves available as a service to "customers" (direct reports, other teams). Think of helpdesk/customer service, where there's docs on how to communicate/collaborate/find needed info, times to schedule meetings/office hours, etc. Focusing more on the experience and needs of the people who might need the manager for something.
Up-managing is basically supporting your boss. Help them with their goals, find ways to unblock them, ask them how they're doing/let them vent, make them look good to others.
Personally I disagree with the whole "making someone else look good" management philosophy (including "only complain up"). I think it's dishonest and counter-productive. Sure it reduces friction, but it doesn't help crappy things be less crappy. It does prevent people from having hard conversations which might change things for the better. We need to take the ego and resistance to change out of work/management.
It doesn’t just have to be helping your boss. From your reports’ point of view, it’s a matter of spending less time telling us how to do our jobs and spending more helping the boss figure out how to do theirs.
Because often the people doing the thing have a pretty good idea what’s possible and what’s not, and when the management wants unicorns they will be unhappy with everyone because all they are getting from them is ponies. Someone has to tell them that’s because unicorns don’t exist and they’re being not just unreasonable but unhinged.
I hire relatively entry level folks for advanced product technical support so my funnel is naturally large since they aren’t specialists and I can teach/train the stuff to anyone who is a technical hobbyist or enthusiast. This has been my best way to keep top of the funnel high, over the years I also got more and more comfortable hiring folks with less and less technical/startup background but mostly my advice isn’t helpful for roles that require a lot of specialization. At that point it’s good to have a solid network, a good reputation, and a successful company. That’s another thing that’s kept me from having to expand my funnel much - my company has been doing really well for eight years and is only becoming more well known and mostly we get a lot of inbound. Besides that, hire good recruiters, sourcers, and recruiting coordinators. They know their shit.
From demanding all computer screens face them to micromanaging time that required logging every minute in 15 minute intervals. I've seen it. From email snooping to timestamp logging to phone call recording tracking micromanagers are alive and well .
We were using it internally pretending we were billing each other. Total employees under 5 people. Monthly an accountant would email and say you are not billing enough hours. This was full time.. weird, horrible experience I can bring with me.
It seems silly to suggest n=1, unless you somehow assumed I've only encountered one manager in 20 years.
N is the number of managers I've personally reported to (directly and indirectly), other managers I've had direct experience with at my various workplaces, the managers of my peers at these workplaces, and the managers my friends at other companies have told me about.
I've seen many bad managers, but their flaws have been: political shenanigans, technological ignorance, lack of involvement, or just general cluelessness. The one thing I've never actually seen yet is a manager who is trying to do too much in the details.
I had a CTO who would often send erratas with corrections in documentation written by and for ICs.
He would also _frequently_ request that PMs would send him draft emails before they send those to third party suppliers.
Note that all of these edits were not about content or data sensitivity or anything technical. It was purely grammar or just zero value adding re-wording.
It was definitely the shortest position in my career, i got out as quick as I gracefully could.
Ha, I send corrections (including minor grammar/spelling) to ICs under me. But I use it explicitly as a "teaching moment", and explain to them:
* They should be mindful of all aspects of their work, including docs.
* If I come across code that woefully misformatted, and comments are all over the place, with random whitespace, and zero effort on spelling (in comments or function/variable names), it causes me to think they don't pay attention to details -- that they don't care about their code. I find badly formatted code to be especially jarring with UI engineers, who should have some knack for visual quality.
* I warn them that when /others/ in the company see our code and docs, if we look sloppy, they will implicitly form a judgement of us as a sloppy team.
On the other hand, if the single contribution I ever provided for my team was spell-check... then yeah, I should leave.
> If I come across code that woefully misformatted, and comments are all over the place, with random whitespace, and zero effort on spelling (in comments or function/variable names), it causes me to think they don't pay attention to details -- that they don't care about their code. I find badly formatted code to be especially jarring with UI engineers, who should have some knack for visual quality.
This is a tooling problem, not a people problem. There's not a language I know that doesn't have at least a tolerably decent formatter and linter out there, and a delightful side benefit of having those in your build chain is the end of style bikeshedding. I find "well, if it means that much to you, you can always open a PR on the style rules," and the knowledge that they'll need to justify their preference - and own all the whitespace PRs, and at least half the merge conflicts, if they wish not to be thought a jerk - quells most folks' desire to fight about their preferred number of spaces or what-have-you.
Without any sort of reliable tooling support for a standard house style, I believe I might well come to regard the kind of insistence you describe as a demand to waste time on pointless busywork. Doubly so, if the person doing the insisting had made no evident effort to find and put into practice such tooling support.
They do; I went to a lot of effort a few years back, teaching one how not to be. We both learned a lot: I learned how to avoid a significant failure mode in my own career, and he learned he was happier in an IC role.
Error bars account for the known and quantifiable sources of uncertainty. They don't (can't) account for unknown or unquantifiable sources of uncertainty, such as aspects of the experimental design that were not properly accounted for or unpredicted/unmodeled interactions with other particles or forces.
Known unknowns and unknown unknowns, as Rumsfeld would put it.
About a decade ago I saw a very nice figure of estimates of the speed of light over time showing this effect. Unfortunately I haven't been able to find it since.
I don't know if I have a favorite part, although the weather forecasting/probabilistic prediction and estimated error in speed of light estimates might be.
I think error modeling doesn't get enough attention, nor does error due to model uncertainty per se, and the paper explains the consequences of those two things pretty well from an applied perspective. I also think it nicely integrates model uncertainty, error modeling, and complex systems modeling all at once.
I don't think there's anything really groundbreaking in it but I think it does a good job of explaining the importance of certain things that are often really overlooked.
Just a small comment about the speed of light. The way we now define the speed of light, measuring it doesn't really make sense anymore. The speed of light is now DEFINED as 299792458 m/s and the meter definition is based on the speed of light. So in principle, one can only measure the meter and not the speed of light anymore.
Would it be the same in a hypothetical completely homogeneous gas?
My assumption is that turbulent changes in pressure cause diffraction, causing the light to not take a perfectly straight path. I don’t know enough about physics to know if that’s right.
The speed of light in a medium is the inverse of the refractive index of that medium. It's caused by the interaction between the electrons in matter (bound to atoms) and electromagnetic fields. It does not require inhomogenities larger than the atomic structure.
Materials seem to have different refractive indices for some sort of complicated quantum reason that only relies on the inhomogenity because of materials being made up of atoms containing electrons, not an sort of macroscopic inhomogenity.
If this result turns out to be right, at least part of that confirmation will involve producing a theory which reduces down to explaining other results - either from previously unknown systematic error or interactions.
Even if you only consider statistical errors, there is no guarantee that the actual value is in the confidence interval. The graphs in this article seem to use 1σ bars which have a 68% chance of containing the result, assuming a normal distribution.
Even if that's not the case, a live war has to decrease productivity immensely.