jc4p

This is a pessimistic view of what I'm recommending! I don't want fake praise, I want reasons why they're a good fit for my company and why my company is a good fit for them. Even if it's a company they've never heard of, a "I think it'd be really cool to work on a product in the {$FIELD} space" catches the eye on a cover letter.

This is really interesting, I think we've experienced some very different companies! Where I currently worked, I've been the "inside source" for 4 people (2 of which I initially reached out to first), all of them were rejected :(

Out of curiosity, what do you focus on instead? I've found resumes in general to be a poor way to judge developers quickly. I tend to read the cover letter, jump to their Github or Stack Overflow (if listed on it or the resume), then go to the resume last if I still need more context.

What you describe is one of my biggest annoyances too, and very common with contingency recruiters. Luckily, our internal recruiters are fantastic and a couple have taught themselves how to program to be able to carry on introductory talks better!

Stack Overflow Jobs (our job board) also explicitly disallows this sort of behavior. If a first-touch e-mail doesn't list why the person in particular is being contacted, again, I think it's spam.

I really don't agree with this. I customize my cover letter and resume for every job I apply to.

I actually started doing this when I worked at a 3 person start-up. In a small team I want someone who's also interested in the actual idea we're working on, not just any random developer. It helps that being excited about the idea/platform/etc also helps attract engineers at lower salary than bigger companies.

The additional page thing makes me feel better. I think it's a really cool project, and sharing the percent match with the person is genius. The cover letter in the example isn't really a cover letter, though.

A bare-minimum cover letter would to me include _reasons_, e.g. "I've been teaching myself Rust in my off-time and migrating over from a mobile engineer to working in Rust full time really excites me."

When I'm reviewing an application, the most important thing to me is the cover letter and the specificity in it. If you don't state why you want to work at the company, how you think you could grow being a part of it, or even mention the company by name explicitly, I ignore the rest of the application.

Spray and fire might work if you don't actually care about your job, but this really seems like spam to me.

I used to use AsyncTask way more, I now stick to other ways to doing background processing. What you have is pretty close to what I described as a "headless fragment", it's a pretty common (but ugly, imo) paradigm, from the looks of it you either made something similar to or followed this: http://www.androiddesignpatterns.com/2013/04/retaining-objec...

Nowadays I've pretty much drunk the RxJava kool-aid. For this kind of thing, I would make the HTTP method exist inside of an Observable which would be observed on a shared single instance Looper provided via Dagger.

To be honest with you all my experiences with Services have made me never want to use them.

What you described sounds a lot like what I used to do for years. It works fairly well, and you can tack a headless Fragment onto it for things that you don't want directly connected to an activty's lifecycle (rotating the screen mid user sign-up shouldn't restart the HTTP call, etc).

This works well, and I'm at the point where I develop it without thought while creating new apps, but I've been playing with a less constrained DI flow instead using Dagger 2.

The more business logic and multiple copies of shared UI elements in different Fragments are directly connected to their parent Activity, the harder it is to re-arrange and re-use them. I've been working on migrating all core elements of our application into a shared library project, and that would've been impossible with a closely tied codebase.

AHA! Thanks, I'll try this later tonight!

Weird, when I try keytocard it errors about the size of the key, but when I tried it with a 2048 bit key it worked fine

While on the subject, does anyone know how to actually put a 4096 bit key on a Yubikey 4? I've been trying for months and their support is non-existent.

If you choose what you read carefully, it's still a great source. I find it a lot better during the quieter times on the weekends, and I use the number of comments on a post as a negative indicator when considering clicking on an article.

Elixir is the name I see thrown around the most when it comes to stuff like this: http://www.phoenixframework.org/blog/the-road-to-2-million-w...

It's in his profile, Vivisimo: https://en.wikipedia.org/wiki/Vivisimo

I love this. Am I wrong or is it "if you don't believe me, try the social engineering hack yourself!"

I used Lob for a small side project, it was fantastic. We simply sent HTML to them, which worked out great since we didn't have to deal with any real typesetting and got to design letters with HTML/CSS.

> Wow, my first thought was “headers are messy and this is so restrictive”. As a lazy developer, I’ve shied away from dealing with headers, relying on abstractions provided by libraries and frameworks.

I'm sure this is a common thought, but oh man it hurts me to read it.

super minor but unless I'm mistaken SPA stands for "Single Page Application", so the first sentence in the post is a bit jarring:

> AlphaSights’ recruitment platform evolved from a Rails application into a _classic SPA app_.

Update 20s later: is "Wepack" in the diagram supposed to be "Webpack"?

Update 60s later: Can you explain _what_ you're actually using that runs into CORS issues? Are browsers talking to the api.* address directly? The diagram seems to imply that all api.* communication is routed through app.*, in which case CORS wouldn't be an issue, right?

I know it's just an example, but both of the games you mentioned have had Mac versions for a very long time, if not initial release.

I think the bigger issue (which another article I read on this last week described, but I sadly can't find it right now) is that low punishment for when it's caught means its more likely to happen and not be caught. There were 3 cases reported in 2015, how many went unreported? If the culture is "oh it's fine, just don't be egregious about it" I expect it's happened a lot more than 3 times in the last year.

Do they not maintain proper audit logs? I work for Stack Overflow and I can't look at a user's PII without it being logged in multiple systems, do we have higher internal security than the police department?

SXSW also refused to give a US Olympian her badge until she removed her hijab: https://twitter.com/IbtihajMuhammad/status/70872225098001203...

And this is what play.google.com/music/listen looks like: http://i.imgur.com/9dmTu6h.jpg :)

For Python my coworker (and friend) Tom has a great project called timetravelpdb: http://everythingsysadmin.com/2014/04/time-travel-pdb.html explains a bit on it, the repo is https://github.com/TomOnTime/timetravelpdb

Basically it's an extension of pdb that allows you to jump back and forth in time.

This isn't what anyone except you is talking about. The issue is being unable to access CF secured clearnet websites using the Tor Browser Bundle (or any other way to route your traffic through Tor).

When the ESP8266 successor, the ESP32 comes out you'll be set: https://www.sparkfun.com/news/2017

For now, you can always buy your own bluetooth LE modules and attach them to a small microcontroller, for buttons, you could make your own wall buttons with nice enclosures or go the ridiculous route: https://www.adafruit.com/products/1185

Or at least use `replaceState` not `pushState`. I scrolled from the top of the page down one section and when I hit back it just went right back to the top of the page.

As stated in the full comment thread here we limit ads for users above 200 reputation. That puts it right between "Vote down" at 125 reputation and "View close votes" at 250.

Funny enough, we often get asked to implement the opposite: http://meta.stackexchange.com/a/273653/229741