792 karma · joined January 16, 2014
My dad taught me lots of tips on conserving fuel and thankfully I've exceeded the sticker numbers on every car I've owned.
* Urban environment. Lots of deliveries in a short period of time.
* Amazon DH is conveniently located near I-95 for easy access to the city as well as I-695 and surrounding suburbia.
* Traffic actually isn't that bad compared with other urban areas.
1. Verbatim definition the positions job description. 2. I'd be golfing or laying on a beach. 3. My attempts to probe deeper lead them to specific answers and I end up with my dream job and not theirs.
The article is a little light on details about your follow-up questions. Care to share some more?
Tangential to the article. But, I find it kind of surprising that the employee to user base growth was linear. I would expect it to be closer to logarithmic in a well run company. Although I have no data points. Am I off base?
Our first major improvement to this work flow was a tar of the app with all of the dependencies coupled with `npm rebuild` after unpacking. This worked quite well.
However, recently, we have switched to using Docker to generated this sealed packages which is working great.
We used a piece of software to lock down the PCs, IIRC, called Fool Proof. I'm not sure if it was supposed to be ironic, because it didn't take long to figure out that it kept the clear text admin password in swap. The machines didn't have BIOS passwords, so it was pretty easy to boot into a hex editor and dig it out.
When my teacher found out I did this, he praised my ingenuity and even got me involved in vetting alternative options, despite the fact that I had been handing the password around to friends like candy.
For example, the rogue / maverick type can be very important at early stages. They drive innovation, take risks, and get absurd amounts of things done. But, later that same risk taking can become absolutely destructive.
The truly amazing people demonstrate it in action not words.
But, then how do you catch bugs where shared mutable state is not compatible with multiple changes?
I have exactly one exception to this rule and I would love is someone could provide a recommended way to not make it an exception. Debouncing. For example, if you have a input field that lets you type a number for pagination, debouncing the change of that value with the displayed copy of it.
This is implemented with a debounced input field type that uses props to get and update the value, but maintains it's own state for what is displayed. It uses `componentWillReceiveProps` to stay in sync.
EDIT:
After re-reading, it looks like the author uses this exact same exception for the "select". This is considered UI state and should be fine.
It seems (to me), that it would be useful--in addition to the static html--load React on the client and from that point navigate with push state and small static (JSON?) files. It might perform better if your blog has a lot more interactivity. Although, here I can definitely see that as being fluff.
For example, search for a Joss Whedon show and get Joss Whedon shows recommended.
When you do a 1-to-many join and return the same fields very many times, do the binary drivers optimize that or is it return many times? With JSON serialization (or serializing to arrays), you only get the one row.
Throw in ETAGs and you can do a lot of cool stuff to make things scale really well.
"It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch."
"If you're used to servers written in interpreted languages (or named after precious gems), prepare to be pleasantly surprised by PostgREST performance."
Unfortunately, much of this can even be business specific. It would be helpful to find out if they have any of this documented. It probably isn't documented within the software team, but, it most likely is for other business units!