1,586 karma · joined April 8, 2019
This is how it has become with job applications. So many people started lying on resumes that the job reqs starting raising the requirements for a position, which causes more people to need to lie. If you don't lie, you just don't get a job and starve/die.
But how do you avoid hiring a non-diverse person? What if the hiring manager likes them? Simple, just don’t even give them a screening at all. “Not a culture fit”
I’ve been applying for 2 years and landed maybe 5 interviews, none of which offered me a job. Two friends recommended me for jobs and I couldn't even get phone calls screenings.
Note: I am a white male.
I honestly didn't notice. The Fremen still seem heavily middle eastern to me.
Right now, the rich are disproportionately punished for having children while the poor are basically paid for it. How about flip flopping that?
Maybe it sounds good on paper but in practice it amounts to a nothingburger and is essentially the same as manually moving instances in the fediverse.
Neither does BlueSky… or if they do “have” it, it’s never been used because there is still only one server.
They have an app but it is incredibly underpowered and lacking logical features.
Each band can list their tour dates but there is no feed where users can see all of the bands that are going to be in their area, etc.
Just very frustrating because all the primitives are in place, but there’s no product vision.
I said being able to see the word shape is very helpful. I did not say that you can read based on the word shape alone.
so that is an argument in favor of using lowercase.
It was designed that way so they wouldn't have to worry about moderation so much right away.
2. People may be interested, but they’re people that are outside of the existing niche that is on Bluesky. But clearly BlueSky only wants people that are part of that existing niche. The monoculture.
Some part of that is due to the design of BlueSky. But I think most of it was ironically due to the invite system simply existing. Jack wanted an open platform.
Fundamentally, Sprints run parallel to incremental releases and are not supposed to be synced with them.
For example, a Sprint is once every 2 weeks. But the next product release could be determined whenever a certain feature is completed.
Because a Sprint is fundamentally about estimating bandwidth. You look at the old Sprints and are able to average out some kind of true estimate of capability, right?
But if you have a smaller team, everyone basically already knows what your bandwidth is.
They have absolutely done the reverse move haha
Best Practices = 95
SEO = 90
and that's using the marked.js library