Hi! I've been using Arctype as my daily driver for DB interaction for the last month or so and asides from a few quirks here and there my experience has been really great so far! Excited to see where the project goes.
Fair enough. I understand where you're coming from, at the end of the day I guess it depends on the context and the way the question is presented (left-field questions such as this one can be somewhat fun to try to answer and hypothesize about, if the interviewer creates a friendly environment to do so)
> General curiosity and interest in areas outside their field of specialty. This might not be strictly necessary to get a job done, but it probably has some correlation with other measures of technical aptitude that are hard to probe directly.
I think this is a bit misguided, since the scope of things outside of a candidate's field of specialty is tremendously large. Picking a random piece of tech within that space and drilling the candidate about it seems rather unfair.
A better way to handle this would be to actually ask the candidate about what else interests them outside of their specialty. But hey, maybe that doesn't stroke the interviewer's ego enough (:
> So, the relativity of "oh no I wish our best and brightest did something more productive with their time" becomes extremely apparent very quickly. Is it really that tempting to debate when you know the outcome of the debate?
I'd argue that the fact that we got to the point where the options are what you described might be an indicative that they (we) were never the best and brightest in the first place.
Yeah, I agree with all of this. A lot of these types of posts and responses give me strange vibes, like people going through life trying to minmax everything and 'win' it as if it was a game.
It's an attitude I encounter frequently in tech circles, but it never stops feeling very weird to me.
I mean, I consider myself Pro-office because I like to personally interact with my coworkers, and I also enjoy the feeling of camaraderie that comes when a bunch of people get together to tackle a certain problem. Depending on your company, a lot of things can also get sorted out quicker when you can talk face to face to your manager/colleagues (though good processes and practices can mitigate this somewhat).
I don't have strong opinions on whether other people should or should not WFH, however. I don't see the need to make this an us vs them issue, at least not when talking between us regular programmers (I am in favor of taking the fight to the higher-ups, though).
Yeah, definitely, I'll try to replace !g with !s in the future. It is my intention to replace whatever google services I can. But admittedly, since this change is mostly motivated by personal ethics and a desire not to give away my private info (as opposed to issues with the platforms themselves, in terms of functionality), it is a bit rough to adjust to some changes.
I've been using DDG as my default search engine for more or less a year now, and tbh I find myself using the !g bang way more often than I'd like. Basically anytime I'm searching for something dev related or anything that's broad enough that without my personal user info it would be hard to return the results I'm looking for. Which is kind of the crux of the issue I believe. For everything that's wrong with Google as a company in terms of privacy-related issues, the truth , at least for me, is that many times (not all) it ends up being... quite convenient I guess.
YMMV though, maybe I need to step up my searching game to obtain better results using DDG. That's definitely something I should work on.
FWIW I just finished building a (very) basic blog using Gatsby (which is based on React) and SEO scores are fine. Accessibility should also be achievable, though I find that failures in that regard are usually due to developers not caring/having deadlines instead of a lack of available tools.
Yup, I've never heard of that particular idiom used to describe the action of spinning up a local server, and it's not really something trivial as to not require some external tooling. So I don't know what's up with that.