I don't have a beard, but if I did I'm sure it would be white, beyond grey.
It's okay. It's okay to feel annoyed, you have a tough battle ahead of you, you poor things.
I may be labelled a grey beard but at least I get to program computers. By the time you have a grey beard maybe you are only allowed to talk to them. If you are lucky and the billionares that own everything let you...
Sorry :) I couldn't resist. I think I'm the oldest person in the department and I think also that I am probably one of the ones that have been using AI in software development the most.
Don't be so quick to point at old people and make assumptions. Sometimes all those years actually translate into useful experience :)
Possibly. The focus of a lot of young people should be to try and effect political change that allows billionares wealth grow unended. AI is all going to accelerate this very rapidly now. Just look at what kind of world some of those with the most wealth are wanting to impose on the others now. It's frightening.
The big problem is reward risk. Risk is 15,000,000 euros. Reward is peanuts.
In the past we could choose to work for peanuts with low risk. Now we can't. We have to work for nothing or work for a lot to have a chance of covering compliance.
The GDPR carries a fine risk of up to 20 million, but usually the fines are a few hundred/thousand euros depending on the entity. Think "300 euro fine to a driving school" rather than "300 million euro fine to Google".
And even then, you have to be unlucky enough to actually get caught and investigated by market surveillance authorities. I think you're going to be more likely to get caught up in income/donation/gift tax bracket fraud investigation than to ever feel the impact of the CRA as a hobby open source dev.
It would be foolish to ignore the risk, however, especially if you work on something potentially controversial, such as encryption, privacy tools, or any software that may have uses that the EU frowns upon. I strongly suspect that this will eventually be used as a cudgel against disfavored projects/devs to compel project changes or even kill the project outright (or force it to move overseas).
If you’re a FOSS dev in the EU who works on something controversial, and you accept donations, it would be better to outsource the project “ownership” to someone unnamed or outside of EU jurisdiction.
Now, from a US perspective rather than an EU one, even being investigated in the US carries a huge risk. It is especially bad in the case that someone wants to prove a point against you. You could suddenly find yourself having to spend huge amounts of money defending yourself because someone wants to make a name for themselves, or you pissed a large political donor off.
Our early warning AI powered polar bear detector proved it's worth this morning. The detector is a result of a collaboration between Kim Hendrikse from Wildlife Security Innovations, The Netherlands and Lars Holst Hansen from Copenhagen University.
Using training data gathered from Copenhagen Zoo and the Skandinavisk Dyrepark to train a model and this year deployed to Greenland. The system is scanning 24 video streams from just a single Jetson. In addition to provide a powerful state engine for local response and control, the system provides a publish-subscribe event callback over websockets. Each detection is checked and double checked against two different large parameter AI models before sending alerts.
The system is Greenland is using all visible light cameras, but the Wildlife Security Innovations smart camera system also supports a wide range of miniature thermal imaging modules with resolutions such as 640x512, 384x288 and 256x192. There's also a lower cost Raspberry Pi 5 based system available.
So okay, assuming they were able to tell a story. Are the people in Europe that have to listen to that story not also part of the problem?
This highlights the telling part, but the people who have to listen are also different from people in the states. I didn't read a lot of mention as to whether this population would just be reception to such story telling or not.
Very well written and so true. It's not even normal stress, which is fine, it's high stakes stress, plus sometime working under the duress of being insulted.
I once went to a job interview with Google. I built one of the first local (Global to the Netherlands) search engines of the Netherlands, but the guy in the cowboy hat at Google asked me to write a binary search with a marker and a whiteboard. I never write with my hand, I always use keyboards. Plus I'm being insulted to write a binary search when I designed and build a search index and retrieval engine.
[I did the binary search but was not happy with the whole process that did not want to even look at what you had actually done before, because that would take away the baseline they wanted].
I guess they must have been looking for cowboys. Tip for interviews, take your cowboy hat, just in case..
The last time I interviewed at Google (because they approached me, and I begrudgingly let an recruiter convince me that this time would be different) the interviewer was so awful that even though the recruiter agreed and got approval to ignore the technical interview and move on to the management interview, I declined to continue the process, and subsequent calls from Google recruiters ever since has been met with a description of what happened last time and how I've permanently lost interest.
The problems posed were all "gotcha" type problem where either you'd read the solution or you'd most likely end up with a decent but suboptimal alternative, or where the recruiter asked for knowledge about toally obsolete things (e.g. I was asked about the structure of an inode in UNIX v6 - I told him I didn't know it but gave a general response about the type of information Unix-y systems keep in inodes, and with more detail about Linux; to add to it, for the role in question a knowledge of filesystem details was irrelevant).
Companies badly need to train a pool of interviewers, and track what kind of questions get asked and provide feedback on it. The vast majority of companies I see have a hiring process where some or all of the technical questions are down to the pet peeves of the interviewer or their manager.
>>e.g. I was asked about the structure of an inode in UNIX v6 - I told him I didn't know it but gave a general response about the type of information Unix-y systems keep in inodes, and with more detail about Linux; to add to it, for the role in question a knowledge of filesystem details was irrelevant
These sort of questions are far too common in these companies.
I have once been rejected by a company here in Bangalore, for not reading the interviewer's favourite paper(The one Google published on BigTable). Which according to him was so important anyone who hadn't read it and re-read it several times like him couldn't possibly be a coder.
This is despite finishing the take home assignment, implementing 3 more features onsite, more code review sessions, general interview sessions.
Some people are not serious about getting work done, and whatever they are claiming to do with hiring people. Unfortunately they are neither looking to hire people to get the work done, nor hiring the best.
Sometimes I wish interviewers were tested. E.g. mix some current well-rated colleagues into the mix, and see how they rated them. Of course that would only work in quite large companies.
But even mock interviews with current staff they know are current staff might help, as a means of weeding out questions that current, well-performing staff would fail.
I don't even blame these interviewers - most of them have never been given any training in how to interview, and it's not a skill they've ever been properly tested on in most cases. It's cruel to both sides to put untrained interviewers in that position.
What year was this? Google mostly stopped asking these sorts of "you gotta know it to get it" questions a while ago. Probably different if you're a file systems expert, but I'm guessing that's not the case?
It was at least ten years ago. Hope you're right they've fixed this, because it soured me on even talking to their recruiters for years.
This was for a management position in an area where even the engineers on the team wouldn't need specialist file systems knowledge. The recruiter got incredibly frustrated when she got my feedback not just on that question but the entire set.
Unfortunately, this worked as intended. These companies want people who are desperate to work there and will do anything to get in the door. Both parties were successful in this case in determining that there wasn't a good fit.
That's also true. I actually was glad that I didn't get the job, because at that stage of Google development they were definately underpaying people who wanted "To work for Google". At least in Europe. It appears that the USA is very different in this respect.
I had a little ego for sure. I think under the circumstances that is not too much. Anyone who puts in really a lot of work to improve their knowledge has a little ego. Calling that "a bit much ego" in this context is harsh. I am indeed someone that doesn't like being treated like shit.
Sorry man, hats off to you if you are that humble. For myself, I don't want to be that guy though. I don't consider myself being a person with an oversized ego. But I did not appreciate someone deliberately refusing to hear anything about your past experiences because that would throw his baseline out as the entire choosing of candidates was on the basis on scoring on their tests. And I was not someone that was fresh out of school.
> I don't consider myself being a person with an oversized ego.
People with oversized egos never do.
Lots of people can talk at length at a high level about complex systems and can't even write a for loop. If you think you're somehow special and should get to skip that basic validation then IDK, sounds like egotistical behavior to me.
Your cool prior work got you the interview. The interview is to interrogate how you think and small problems are the best way to do that. You're sounding a bit arrogant, as if writing binary search is beneath you. Possible that they marked you as a bad culture fit if you acted that way in the interview.
But you don't know who voted for them. In Europe, laws are also formulated by a group called "The high level group" I believe, and the members of this group are anonymous.
reply