Is it possible that this person may have some form of multiple personality disorder?
The new hire who showed up is not the same person we interviewed
521–530 of 623 posts
Re: The new hire who showed up is not the same person we interviewed
#522No post body was provided.
Re: The new hire who showed up is not the same person we interviewed
#523Earlier quoted context omitted.
This is why we can't have nice things. Or in other words, why we must usually do a coding test per company we apply for, and not just 'point them at the Github'.
Or stuff that's so old, it predates Git, let along Github Here's some code I wrote back in 1987/88, for example. http://www.retroarchive.org/swag/MISC/0153.PAS.html
There's a spelling mistake / typo: it should be ensure not insure.
> This procedure allows the programmer to insure
Re: The new hire who showed up is not the same person we interviewed
#524Earlier quoted context omitted.
Sounds like that type of job might not be a good fit for you? You’d always be anxious!
It might be the fact that people are monitoring how the sausage is made with the explicit purpose of judging that process. But when working with people in the normal job, nobody is watching them type they just eat the sausage. I can relate. I don’t have anxiety generally with work and have been praised on my interactions with customers. But I feel anxious during interviews because they are actively trying to judge me…
It's my opinion that interview anxiety is almost entirely unrelated to: how well someone works with a team; how well someone handles an emergency; and how well someone can related to and work with clients. Source: I've been repeatedly told, over decades, that I'm good or great at all those things—and I enjoy all of those things, for the most part, even when they're tough—but interviews make me anxious as fuck and I hate them (though I'm actually good at the talking parts—I just tend to lock up when someone is watching me work and judging me). It's a totally different thing.
Re: The new hire who showed up is not the same person we interviewed
#525Earlier quoted context omitted.
Or stuff that's so old, it predates Git, let along Github Here's some code I wrote back in 1987/88, for example. http://www.retroarchive.org/swag/MISC/0153.PAS.html
There's a spelling mistake / typo: it should be ensure not insure. > This procedure allows the programmer to insure
Spelling mistake from 35 years ago. Strong no hire!
Wait... perhaps that's why the github account route may have issues...
Re: The new hire who showed up is not the same person we interviewed
#526It's like the flip version of the guy that got let go and then re-recruited for his just vacated position. https://twitter.com/firr/status/1456324664628846599
Hey, I kind of know that name - ran across this years ago: https://twitter.com/isfirrinjured
...though I remember it being its own site/domain, not a twitter account.
Re: The new hire who showed up is not the same person we interviewed
#527Earlier quoted context omitted.
There's a spelling mistake / typo: it should be ensure not insure. > This procedure allows the programmer to insure
Spelling mistake from 35 years ago. Strong no hire! Wait... perhaps that's why the github account route may have issues...
The comments were so good, I kinda had to point it out!
Re: The new hire who showed up is not the same person we interviewed
#528Earlier quoted context omitted.
Are you paid a fair market rate for your geographical location in India? (i.e., are other local companies offering worse or better benefits?)
These days, equavalent salaries in india are between 1/4th to 1/2 of equavalent american or uk salary for the same job. Adjusting for cost of living is a bit tricky as there are many things which are cheaper in India, but many things that a sw developer may want to buy are not so. In general electronic items are a bit more expensive in India, but things like rent, cost of food, clothing, cost of a basic car are lesse…
>but those cars would most likely be illegal to sell in the US. When the manufacturers sell the same exact model here in India,
I'm curious what you mean by illegal. Do you mean they won't pass emissions or safety?
Re: The new hire who showed up is not the same person we interviewed
#529Earlier quoted context omitted.
Plenty of companies use source control other than git. AAA gaming studios are famous for not using git due to git's poor handling of large binary assets w/o workarounds. I've used other source control systems and they do have benefits over Git to be sure. Access control is a huge one, you can have a large repository and have fine grained access control over who can access what paths in the repository. Heck with some…
Regarding large binary assets, I literally Googled "git large binary assets" and had many hits with various solutions. GitHub started offering Git LFS (Large File Storage) in 2015 -- more than 6 years ago. That said, many places still use Perforce.
It's newish (yes, 6 years is newish for projects that don't have a lot more hours, direction, and dedicated drive behind them than git-lfs seems to) and janky or unintuitive in some cases and adds another obtuse nerdy thing for e.g. artists to figure out (or be supported through) and requires extra software and server config to self-host (most of which is, uh, not as complete as one might hope) and makes backups less dead-simple than plain git and has nothing like an official server-side implementation (last I checked GH's "don't use this for production" implementation was the closest thing) and can make any kind of automation or extra tooling used with git a real pain since much of it's not lfs-aware, including some built-in git commands in certain situations (git-archive against a bare repo, for instance, which can be a super handy command in many situations).
Overall, I like it and have promoted its use and stand by that, but not every place has the time or inclination to screw around with it when they can just pay for something that solves the problem (likely Perforce).
While we're at it, git in general would be one fuck of a lot easier to support for cross-platform users and in tooling for complex projects if libgit2 caught up and took over as the official implementation. The pile-of-binaries-and-shell-and-god-knows-what-else (all living on top of a hacky, huge bundle of junk, on Windows) official Git itself is a huge impediment to doing anything with git other than just executing "git [command]" in Unixy environments. It'd also make "build my own GitHub" type projects far more tractable, cutting out some of GitHub's (and GitLab, et c.) server-side moat.
LFS is a pain, right now, even 6 years in, if you don't tie yourself to a major commercial Git host or put in a lot more effort than traditional self-hosting git requires. To reiterate: I still like and advocate it, circumstances allowing, but it definitely is not a mature solution.
Re: The new hire who showed up is not the same person we interviewed
#530I've been a hiring manager for remote positions for a long time. If your recruiting channels are good, most of your candidates are going to be honest and good intentioned. But interview enough people, and you'll start encountering people trying to abuse remote work. They're not interested in contributing to your company. They're only interested in collecting paychecks while they do as little work as possible for as l…
>> Always makes me wonder how many dysfunctional companies are out there letting deadbeat remote employees collect paychecks and do as little work as possible because nobody cares enough to press the issue.
Nearly all of them. And it's why managers who get burned just a single time hate the idea of remote work. It's not about office rent or anything else that gets bandied about here; it's the fact that a very small but significant number of remote workers are grifters and create a ton of negative emotion (out of sight out of mind) for co-workers and managers.
A ton of remote work is obviously the future, but every single negative case like this with legacy managers sets it back orders of magnitude more than the successes it generates. So it goes with everything new.