That's pretty interesting, I look forward to see what comes out of this! People often tend to conflate "computer science" with "professional software development" and I admit my first reaction was "so what? I routinely use just a small handful of data structures, do we really need something like this?" but seeing it visually laid out in an easily-digestible format is somehow inspiring. From a scientific perspective I can imagine discovering more advanced structures much like "missing" elements from the periodic table.
I'm not trying to move the goal post. I'm only taking umbridge with the fact the previous poster said "No one has claimed that Oumuamua is likely an alien device". The person interviewed in the very article this discussion is about seems to think that maybe it could be. So we are talking semantics between "likely" and "possibly".
Ok how about the introductory paragraph that states
> The following October, Avi Loeb, the chair of Harvard’s astronomy department, co-wrote a paper (with a Harvard postdoctoral fellow, Shmuel Bialy) that examined ‘Oumuamua’s “peculiar acceleration” and suggested that the object “may be a fully operational probe sent intentionally to Earth’s vicinity by an alien civilization.”
or another spot where he says
"Every now and then we find an object of artificial origin. And this could be a message in a bottle, and we should be open-minded."
Seems to me like he is saying it could be worth considering that maybe this is an alien object.
Hopefully the manager of the team is also subject to performance reviews. Generally the manager of the team is responsible for the performance of the team, meaning the manager fails if the team fails or has significant problems.
This is highly dependent on company environment however and obviously can come with it's own set of motivations and problems.
Strongly disagree. Waiting tables or bartending at high-end restaurants could be considered gig work. Wedding photography is gig work. I have a friend who runs a stationary side business as a "gig". These jobs, if you are able to market yourself effectively and gain a good reputation and some solid contacts, can pay extremely well. I have a nice 9-5 with benefits and stability, but my friends in the above positions earn about the same I do and work close to half of my hours.
That obviously isn't the case for everyone who does these, but I don't think you can make the claim "the pay sux" for all gig work.
I've worked at a few places of vastly different sizes. From a company with only three devs, an office with three hundred devs, and a fortune 500 with over 3000 devs (not necessarily in that order). Maybe I've just been lucky, but at all of those places I've had conversations with my managers along the lines of "team x is doing something I find interesting and eventually I would like to do that, can you help me get there?" or "I have an idea for a project x that would be useful to us, can I block some hours to work on that?". Generally they have been amenable, and if not then I've moved companies. You need to be responsible for your own career, and I like working at places that encourage personal development :)
Because it sets baseline standards. Yes, I think everyone knows the US does not have the best healthcare in the world. But I also think it's 100% appropriate to say if you want to practice medicine in this country then you must meet our standards. Just like a drivers license might not be valid in any country you visit outside your own.
You tell your boss(es) about your concerns and onboard some new people, and you do something new. Either within the company; find a team that needs people or try to pioneer a new app, or change companies. Or accept being the expert and enjoy a promotion!
Well, first of all it's a puzzle so it's useful as something fun to think about. Math is kinda like science though, you never know exactly how or if a particular discovery will be useful. In this case maybe you could find some graph traversal scenario where this would be applicable. In the Wikipedia article under variants they mention
> If the number of team members and the fraction of boxes which are opened is fixed, the winning probability stays strictly larger than zero when more empty boxes are added
Replace boxes with nodes and now you have some math to determine graph traversals. Maybe a bit more math and you can expand it for multiple paths. I don't know though, I'm not a mathematician and I don't normally have to do more than DFS and BFS in coding interviews, but sure I can see some way that this might be useful.
Or, you know, all going to see whatever you want and meeting up when you can. Festival protip: there's no law saying a group must stick together the entire time
Reeeeeeeally depends. In my experience, most people who would do the early interviews/ determine candidacy for an interview probably don't have the time or desire to check out bespoke websites or other "deviations". The look at a summary of the position applied for and a summary of the qualifications and determine to go forward with an interview. In all likelihood, your interviewer probably won't look at your website either. But it's a good talking point, and if the interview is anywhere other than one FaGooNetZon etc, then being able to talk about it in an interview might win you points. So it wouldn't say it is _bad_, just that it will probably be ignored 80% of the time.