preds

Everything you've said lines up with exactly what the author said. Carbon fiber bikes are made for and good for racing. If you're not actually racing you probably want to be on something more durable. It's almost like you just read the (intentionally sensationalised) headline..

The last place I worked at had some serious issues going on internally. A couple hundred people but a basically non functioning HR department. People being yelled at by managers without repercussion. Also just bad engineering culture - top down directives that didn't make sense to be spending time on.

About once a month there'd be an extremely negative review show up on glassdoor highlighting what it was actually like. Directors go into crisis mode then a few days later the review is gone. Apparently if you pay Glassdoor you can have reviews removed by just telling them it's not factual. So unfortunately it just can't be trusted.

Nowadays I talk to someone that works there off the record, outside of the interview process. Ideally a friend of a friend.

Location: NYC / New York City

Remote: Yes

Willing to relocate: Not immediately

Technologies: Python (Django/Twisted), Java/Scala/Kotlin, postgres/MySQL/redis/hbase/elasticsearch, rabbitmq/kafka/sns/sqs etc etc

Résumé/CV: www.linkedin.com/in/nathanoorloff

Email: [email protected]

---

I have around 12 years experience (mostly with startups) and prefer backend / infra work these days. Currently enjoying some time off between gigs and starting to think about what's next. I've led sizeable projects, worked directly with clients (gasp without a pm!), been responsible for launches at scale, set standards for eng orgs and much more.

Ideally I'm looking for something that makes the world a better place but I'll hear you out on Airbnb for cats if I get to learn Rust/Go or improve my FP skills along the way. Nothing in finance or advertising please!

Caveat: I'm Australian and would need an E3 Visa sponsored.

I had exactly the same experience coming to SF from NYC. I took taxis in NYC every once in a while, the only bad experience was on new years eve where everybody turns their lights off and operates without the meter. After moving to SF I had such poor experiences with taxis that when I raised it with a friend they exclaimed oh, nobody uses taxis here they're awful - use uber (I now use Lyft regularly).

Some of those experiences include:

- very obviously driving me around the block after I asked to be dropped off at a particular location. The driver refused to let me out when I asked

- driver refused to drive me with a "I don't want to go that way"

- two drivers claimed their card machines didn't work and insisted on cash, the second tried it even after I asked before the ride if paying by card was okay

I did replace the # with %23 in my testing, it works on the S2 but not the S3. You can view for yourself at: http://kristofferr.com/samsung.html

I've tested this using both a galaxy S2 and S3. On the S2 the above page is safe and triggers the exploit to view the IMEI. On the S3 it launches the dialler however, the dialler is empty and does not display the IMEI.

After investigating further, the S3 does not launch codes that begin with * # but will trigger the factory reset code which is in the format of * 1234 * 1234 #

Edit: Those with an S3 can confirm this by visiting http://no.tl/s.html in which I've embedded * 1234 * 1234 # (which is not the reset code, but is the same format)

Testing this myself, any USSD code that begins with * # launches the device's dialler with no characters dialled. Looking at the list of codes: http://umitem.blogspot.com.au/2010/10/samsung-galaxy-s-i9000...

The factory reset appears to be the only USSD "auto dialled" code that doesn't begin with *#. Which is rather unfortunate.

Edit: Actually, the IMEI code works on the Galaxy S2 running 2.3 (just tested) but not the Galaxy S3 running 4.0. My above comment refers to the S3.