nijiko

Best thing I've found is to get someone to tackle a problem you've recently faced or are going to face and see how they handle it.

Not on a whiteboard, but with actual code and examples. Some companies will pay for this, and others just take it as a part of the initiation process.

It really lets you see what people focus on, how they handle it (time, code, style, design, etc), and how dedicated they are to the actual problems you face.

yes, vihart has been working on it for a while:

http://elevr.com/elevrant-camera-circles-for-stereo-spherica...

Pretty much this.

Thank you, glad to hear my hard work has paid off :)

You no longer have to code certain features into your API and can let Kong handle it for you :)

Saving you time and money!

   Some features: http://getkong.org/plugins/

Any time you use the web, be sure, thousands of people have your IP instantly.

Yes, its an ongoing issue that people are increasingly unable to read simple if statements. The world has been plagued with academics attempting to analyze the simplest of statements without success. This is what led us to form the "Leave No Academic Behind" (LNAB) group. To inform academics in the err of their ways and show them the path to success.

There have been increase in tin-foil theories about these scripts even when the source is available and very easy to read through. It honestly blows my mind.

I prefer the backcalls of LiveScript to any implementation I have seen thus far, coupled with do, you can do some pretty complex things

It's still Comcast though.

That's what boring technology will get you.

I would say marketing, and describing what is actually happening or problem you are solving (along with features), security concerns and how you handle them, and what happens after you publish (meaning examples).

Check dribbble for "landing" pages, or just view some common technology examples like https://consul.io/

None of the technologies you mentioned are boring, pick the right technology for the job and don't worry about what others are using.

That's not free. You're spending time in exchange for goods. Time you otherwise could save by just spending a few dollars.

The real annoyance is surge pricing.

I'll give this a shot, perhaps make a blog post about my perceptions on all three

overt complexity for no real gains

Wow, didn't even know this company existed.

Currently use Caviar, and Postmates.

pretty much.

> atom

nope, been there done that.

It's cumbersome and laggy, which is a major pitfall for me, I like the responsiveness of sublime text.

I made a gist with a collections of one-liners here:

https://gist.github.com/Nijikokun/d6606c036d89d3b1574c

It will probably be closer to 6h of actual usage.

Just because you changed the market doesn't mean you'll stay in the market forever.

TL;DR

Create github profile, fill with projects you make in your spare time, create linked in, link github profile. Job offers will flow in like you've never seen and many times you won't even have to do a technical interview because your profile proves your worth.

This means:

- Write tests for your repositories

- Have repositories that display your expertise (whether in one language or many)

- Keep up on trends depending on what area you want to be in (devops, backend, frontend, full-stack, data science, growth, etc.)

- Show some marketing initiative, small number of stars / forks, by sending to various blogs.

It may seem like a lot, but it takes maybe an hour a day.

Be the change you want.

TL;DR It might be legal or scrutinized today, but tomorrow is not set in stone.

you mean twitter?

It wasn't meant to discount it, I just happened to watch it without sound and found it amusing and thought others would enjoy both the technology plus a little humour :)

It requires the client id and secret to obtain a refresh token, some also choose to skip this and ask the user to re-authenticate completely.

I agree that people implement it differently so vastly different that it takes almost 40 sources to compile a decent down-to-earth explanation of common practices (same for OAuth 1.0a). However, that doesn't make the protocol bad, it makes the implementation bad, you can avoid XSS, OOS Origin Attacks, and the others with the exception of Vector attacks, but both are vulnerable to this.

Thank you for this, was about to post the exact same reply.

Please, put a link to the github somewhere near the top of the site.

It looks great, however it feels a bit sluggish when hovering over points and doing drag operations in the major browsers, few hundred ms of delay.