311 karma · joined March 25, 2014
In fact, depending on the product you've been working on Google and your seniority, there are many more fulfilling (both technically and socially) jobs out there.
What you need to do now: Start interviewing with companies. I wouldn't suggest mentioning Google, since you were capable of getting into Google, you can get into most other places without the credit of Google.
Depending on how much money you've saved, make a plan, put a deadline for yourself and start looking for a job. Go apply through job postings, email recruiters, CEOs, etc.
Update your resume, send out to 10 postings that look OK - You don't have to work with them if you get an offer, but it should give you enough momentum to get back on your feet.
In WordPress.com, "average content Joe", can manage multiple sites, including self-hosted WordPress.org sites (through JetPack plugin).
Disclosure: I'm one of the authors.
As @frik noted, it uses "I'm feeling lucky" feature of Google. It requires the page to be indexed to work. If the page isn't indexed then it won't work. But since the pages you'd like to see are indexed almost always, it shouldn't be a problem.
https://umur.io/paywall-bypass-bookmarklet-come-from-google/
Related HN discussion: https://news.ycombinator.com/item?id=9134118
They have suggested users to adjust their computer time a couple of days before the expiration to use the site.
They should really start reading about how the SSL works.
I think we should give credit where it is due, MS is really trying to work with OSS community.
Also, a lot of enterprise customer would want always on secure boot, and it is up to OEM to decide whatever they want. How is this MS's fault?
As per staying lean as stated in the article. I don't think that's staying lean at all. I must mention that I have no knowledge of the framework or codebase of the company in question, although rewriting a codebase is almost never a good idea. Well, it will require a lot of rewriting which is redundant, you would be ditching a lot of testing and bug fixing you have done ever since, and you will probably create a space a lot of new bugs.
I believe a better approach would be componentize your structure in a way that's still governed by django, every component split into apps. And if there are outlier apps that do not need to be within Django at all could be used by redirecting the requests to those services on the load balancer / reverse proxy level.
TBH, It doesn't bother me at all. I think I can even go ahead and say the latter makes much more sense. Using the former one is abusing the weaknesses of the language that has come along with it throughout its history.
We have been whining about the bad parts of JavaScript for a long, long time and I think these changes are for the better for all of us.
var _this = this;
call(function (){
return _this.value;
});
versus call(() => this.value);
So yeah, much more readable, and less issues with this binding to some other caller or window.If people were abusing variable hoisting in some way, they can continue to do so, by not using `let`.
However, most of the apps I've seen have a Share feature which one can use to retrieve the link.
If you are interrupted in while working on a very complicated subject, going back to the same focus level takes up to 30 minutes for me. The time I could spent on fixing stuff.
I am happy that most of my employers / managers understood and appreciated this.
You can explain them with this comic as well: http://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-...