They also treat newlines (\n) in the XML payload as an invalid character for <airquotes> security reasons </airquotes>. Authorize.net is an antiquated company that is slowly disappearing, having lost the race versus Bluesnap and Braintree, just to name a couple of providers in the field.
As someone living/fighting through the performance degradation that the kernel patches have done to IO loads at AWS, I'm wondering if their Xen patches have had this or may include it in the future.
Would really really rather that there were no more negative changes.
We run 1.5 million messages per minute through our NSQ framework and we're starting to run into architectural limitations i.r.t to the number of workers in each producer/consumer pool, and are now testing/benchmarking Kafka in our staging environment.
All you need to do is sum up the numbers on each row/column. Horizontal will produce the latitude (except after the 1,), and vertical will produce the longitude.
Great write up. There needs to be more mobile development writeups like this, they aren't popular compared to, say, developing something functional in a backend language such as Go, Node or Python that HN seems to love.
Life360 is the largest family network in the world. Our 150 million users make up approximately 50 million families, with a million new families added just last month. Our APIs process over 800 million location points a day, so we have plenty of traffic to play with.
We're looking for sharp senior-level Platform engineers.
You:
* Code polyglot: we primarily use Python, Go and PHP
* Healthy experience with scale; thousands of requests a second don't make you sweat
* Excellent understanding of data stores, distributed systems, data modeling and their associated pitfalls.
* Play a key role in the product development cycle
* Lead technical architecture discussions and review technical plans
Chiming in here - I've got congenital profound loss in both ears, but I have a cochlear implant. I've grown in my career over the last 15 years from junior dev up to my current engineering management role, and what I've observed was:
1) The biggest hurdle in most cases is communication, especially in meetings. That being said, I still do fine in them, because I rely on lip reading as well as vocal cues/context, but I also rely on my coworkers to be understanding from time to time, and they are.
2) Slack has been hugely beneficial to me, but it requires the organization to be engaged with it.
3) I have accented speech because I drop some consonants (f and s sounds mostly), and it can be a challenge for some to clearly understand me shortly after meeting me. This usually resolves itself after 2-3 weeks.
4) Job interviews: I'm always up front about what I can and can't do - this usually comes up around the topic of phone interviews, I can't do them. People appreciate this, and I make it clear that I'm not ashamed or hindered by my disability. The confidence goes a long way. If you come off unsure, then of course others will be unsure. I've definitely had interviews where there was a communication disconnect, but typically that comes along with other circumstances that make the job a poor fit. I've never had the situation where the job/culture/people fit was there but it didn't happen because of a communication issue.
For other deaf developers out there, just own it and show that there is no hurdle out there that you can't overcome, and you will be successful. Always be trying to help others and others will help you in return.
Good riddance.