813 karma · joined March 18, 2019
You can't assume that person is going to act in good faith about anything else in that situation, so even refusing to take the bait is still ultimately a roulette wheel that can just as easily be labeled as "difficult" or "combative."
If it would be unprofessional to bring those things up freely, then it's actually more unprofessional to coerce people about them as a screening criteria -- whether that's coercing them into putting on a show of dancing around the issues, or coercing them into giving you honest answers.
A candidate can be aware that these kinds of questions are supposed to have boundaries, but that's different from whether an interviewer understands or respects that. And if they don't, those people are also in a decision-making capacity that doesn't often empower you to just say "no."
Even when those things are scoped to "...at work," there are still answers that happen at work that are equally inappropriate to go digging for. "Tell me about a time you experienced adversity," for instance, could turn up health or family details that people might have juggled with their jobs -- things that you aren't actually supposed be considering as a factor in these decisions.
I also don't know, when someone is spending 90min screening you for "culture fit," that you can assume they're asking you for things that are strictly related to the job. They should be, but that's different from whether that's always a realistic presumption you can make.
One guy -- the reason I started building a tracking tool, after I noticed that his email was autofilling when I went to send him a message -- ghosted me after I wasn't available the first day and time he suggested. Which was also a holiday.
Another place, a stealth startup, was a panel interview with their three founders -- two tech leads and the CEO. The tech leads actually had really interesting discourse, and I wish I could remember the name of the guy who told me that "testing means never having to use my brain for the same thing twice." It actually never occurred to me before that an interview could provide you with useful knowledge, let alone that an interviewer could make a point of imparting those things on purpose. However, their CEO asked me to commit 5 years of my life up while also refusing to tell me anything at all about what the company did.
Within the past year I also encountered one that expressly asked me for things I didn't like about a previous employer; badgered me when I didn't want to elaborate about a specific, traumatizing, walking HR complaint of a man; and then -- after I described vaguely how organizations and their leadership change over time -- explicitly asked me to rate that individual on a scale.
(The other two were a while ago, and Idk that they still exist, but the last company was SerpAPI, who advertises here fairly regularly.)
It's supposed to mean "at work," but that doesn't at all mean that you can assume the interviewer is going to understand that.
But in my personal projects, I myself have just stopped using libraries entirely for styling.
It gets really easy to lean on class-based CSS and use a `<div>` for everything instead of ever learning what a semantic element is.
And that contributes to other bad habits, like writing a bunch of JavaScript to define behavior that could just be natively handled by your browser.
A weird personal irony is that because no employer has ever asked me to directly write CSS, what's actually made me better at CSS is JavaScript -- namely that my understanding of selector logic has improved a lot after picking up Web scraping.
It's sort of like how we give enormous amounts of money to cops (institutionally), instead of funding the safety nets that actually reduce crime. Actually (edit), those analogies are kind of related, because the same safety nets are important for driving down both of these things. Yk, because people are more stable in other ways when they aren't in desperation all the time.
You might say it's the difference between emergency services and emergency prevention.
Edit: I did eventually find the source. https://linkedin.com/posts/tabitha-lean-5786011a3_nspc26-act...
On that note, not that I think regulation is the entire solution in the first place (see ATProto for an example of something independent of government that gives me hope for the Internet), but I feel that where a lot of the "protect kids" Internet bills fail is that many of them treat that as a separate, special concern in a lot of areas where they could cover it anyway by just trying harder to protect users.
In the US, where I'm writing this, it's sort of like how our age discrimination laws are written just to protect elders, but didn't do anything to protect them from the lower floor that came from letting businesses keep spreading stereotypes about who the minimum wage is for or otherwise pushing hustle culture onto 20somethings.
The use of the Internet to astroturf political discourse is an example of this -- you can't fully protect kids from school shootings with an Internet safety bill if you're not also going after bot farms that exist to benefit the "thoughts and prayers" crowd. But you're also never going to see that in an Internet safety bill for kids, because that (and for that matter a lot of our discourse about addictive mechanics in general) explicitly leaves out voters.
(clarifying edit: I'm not saying there aren't valid concerns around this topic. I am saying that when we say things like "experimenting on users' mental health without their knowledge is bad," the baseline should be that you don't have to add anything to the sentence for it to be taken seriously.)
I also applied there some three or so times, and didn't get those either.
Attempting to network with people here led them to promise me at least a response (since these roles were still open, and have been), but they ghosted me then -- only to blindside me about it over a year later, when interviewing me for a different role.
And while they're not the only place ever to grill me about a bad experience at a prior employer, they are the only place ever to explicitly ask me to tell them something I didn't like about one. Or to rate a previous boss (horrible or otherwise) on a scale of 1 to 10.
This, by the way, was all while I accommodated an overseas recruiter by taking an interview at 7pm on a Sunday.
I don't at all feel like I encountered the same level of respect, and while I was genuinely interested in their stated values (including but not limited to their value proposition) and their subject matter, based on my actual interactions with them I really can't recommend applying here.
Also is there a way of exposing an existing touchpad to that new control board for your external one? (Or keyboard I guess, but the use case is that I had to replace my keyboard too, and for what was available at the time ended up just going with a whole input cover. Truthfully, I was already curious about exposing it to USB-C before hearing about this, and prefer wired anyway, but am also curious about the more immediately relevant part of the question.)
I'm not saying I'm for those over open source licenses in general, but Prusa brought up some fair questions when discussing the OCL. Essentially: define "personal use." Have I violated a non-commercial license if I print this keyboard and then use it to build someone a website? Does CC-NC mean a Prusacaster -- or any guitar knob with such a license for that matter -- is strictly barred from being taken on tour? Or used to record albums that are then sold? (And I say "guitar" knob, but I'm choosing an example a little consciously that could exist in any variety of controls, instrument and otherwise.)
Where are the lines of that when it's physical things? How far downstream does that go if it isn't CC-NC-SA in particular?
I'm not really sure that Creative Commons had the idea of physical production in mind, given that it dates back to a time when we were more broadly talking about digital piracy, and I honestly haven't kept up with its evolution much in more recent years. But maybe it just doesn't make the same sense for designs of physical things, for comparable reasons to why it wouldn't make sense for code -- and, conversely, open source projects that opt to use CC licenses for assets.
(None of this would stop me from attempting to build/mod one for fun, mind you. It just raises what a more averse person might call risks, and what I will at least call curiosities.)
Whereas in more recent years, keeping a closed-source rendering engine that was no longer competitive in implementing the spec, wasn't being used when people had a choice, and was being used as a dependency for core components of the OS, probably wasn't winning many arguments.
(Edit: yes, I know Chakra was open source. I meant Trident.)
Everything from Edge as a cross-platform Chrome derivative to .NET as a cross-platform open-source toolkit to their React Native builds and experiments with Android suggest that MS itself understands this. The Linux side demonstrates it with things like Proton and the forthcoming Android desktop mode. The Web demonstrates it in general as it expands in capability and more applications skip shipping native entirely in favor of technologies like Electron. And not that I don't personally sob in system RAM, or have extreme reservations about how we got these things (see: Google and antitrust), but I can't say I hate the ease of switchover.
Ecosystem lock-in didn't go away, but it feels like it's changed a lot.
[1] https://arstechnica.com/tech-policy/2023/02/report-musk-had-...
Doesn't seem like that much of a stretch from a UI perspective to do something similar with a Markdown preview.
Though I don't really have a system for storing them effectively as of yet, and as someone with a strong preference for open source on my critical workflows, I never got on the Obsidian train myself. Current experiment is Silverbullet.md, because I do very much like raw Markdown and file-based notes, but that's different from having a meaningfully fleshed-out setup haha
This is easily one of my favorite descriptive details I've ever seen in a README.
> Inspired by (and in joyful dialogue with) motherfuckingwebsite.com, justfuckingusehtml.com, bettermotherfuckingwebsite.com, and justfuckingusereact.com. Extremism in defense of developer experience is no vice! This site made by me. Does this all sound a bit like shallow slop? Yup, please help make it better.
I agree with you, and wrote a similar one for Markdown that you might enjoy. Same overall naming scheme. (Note: open the comments before you judge the use of a Web Component for rendering purposes.)