I don't think government shutdown affects VISA processing. What I've heard is that VISA processing is funded by the application cost itself.
575 karma · joined January 8, 2015
I think a pivot like this is an incredibly complicated thing for a company like Microsoft to perform. It requires multiple years of planning from the ground up to port internal libraries and tooling, train engineers on Rust best practices.
Not to mention the tricky business of going around and hiring Rust developers at the scale MS needs. :)
I think, simply waking up one day and changing the language / frameworks / tools used by your company is a privilege only smaller companies and startups might enjoy.
As the top comment on the article, you have clearly and succinctly expressed everything I have felt.
Can you elaborate?
> It may be fast but it's fragile FWIW.
Go explicitly focuses on language stability over fancy new features.
There is also a bluetooth version which is not manufactured by Yubikey.
https://www.amazon.com/dp/B01LYV6TQM/?coliid=I3IA8VD7QRRZDT&...
https://blog.keras.io/using-pre-trained-word-embeddings-in-a...
Isn't that the opposite of good practice? You shouldn't rely on obscurity. It's better to have the security processes out in the open so that it can be audited and flaws pointed out.
Trust me, the interviewer is never gonna pile up requirements on you. In fact, they are trained to ensure that what they ask can be completed in the time allotted (with time to spare for candidate's questions). More often than not, when you ask clarifying questions, you will end up with a much different problem (and sometimes simpler) than what you expected.
> Asking too many questions sounds like you're trying to delay coding something up.
No it doesn't.
> If you can code a prototype as fast as asking question, why not. Code it up and then ask, "how about this: what requirements are missing from this that require changes or a rewrite?"
This is terrible, you are now making the interviewer do your work. You need to tell the interviewer what the boundary conditions of your solution are. That gives valuable data about your understanding of the solution space.
A Google interviewer expects you to ask questions and clarify any simplifying assumptions you may have made.
For eg: Are you assuming right at the beginning that the entire tree fits in memory? If so, Google interviewers expect you to clarify that at the beginning. They might later ask you to modify your solution for cases where your assumptions don't hold true.
From what I know, the biggest mistake people make during tech interviews with the big 5 is directly jumping to solutions without probing deeper. At the scale at which the big 5 operate, many routinely simple assumptions can be problematic.
General purpose computers are no longer necessary for a significant chunk of consumers.
Using Keras has made me appreciate this a lot.
Most deep learning layers have a bunch of parameters that need to be configured for best results. A lot of research has gone into figuring out best practices and Keras uses those as defaults. Saves me a lot of time.
This is precisely the point. Most companies just needed something that worked. It doesn't really matter if it's proprietary, if it gets the work done.
Paying a little money to slack is much more convenient that getting you entire company to setup and use IRC.
Out side the HN bubble, people choose convenience over open and free.
Out of curiosity, why do you assume the person is a "he"?
But with smart home devices, you have much finer control over what device you want to control. How can someone do something fine grained like "Switch on external lights" or "show me who is at the door (Alexa does this)" with a clapper?
Just an example:
> I'll walk over to the lightswitch and turn the lights on.
What if you are someone who has trouble walking or has mobility issues. Can you imagine how convenient getting things done with voice could be? These sort of things can be life changing for some people.
The silly thing is, there is bipartisan bill in congress and Senate to fix it (HR 392). But it is stuck is legislative limbo.
For example, you could be working at Google / Facebook earning top $$$$ every year and you paperwork could be spotless. But the stress of having to go through an uncertain renewal process every 3 years prevents you from investing in big things like buying a house or having kids. You are always worried about being able to return back to your stuff when you leave for a trip overseas.
Even though most top companies immediately apply for Green CArds, the "country of birth" based green limits ensure that you have to remain in H1-B status for 15 - 20 years (if you happen to be born in India).
TL;DR: It's not the increased vetting that we fear, its the uncertainty and complicated appeal procedures that can affect genuine H1-B cases.
https://static.googleusercontent.com/media/research.google.c...