342 karma · joined April 21, 2008
These issues could be due to the different composition of the 3 compared to the S and X - more steel, less aluminum - or with them trying to build a denser automated production line, or just general gremlins setting up new production.
[1] https://electrek.co/2017/09/29/tesla-model-3-production-ramp...
Wait, we do know what would have happened - the Motorola ROKR, which everyone should be forgiven for forgetting.
They're amazingly deliberate in how they mingle bleeding edge R&D and commercial activity. Something that fascinates me. And rockets.
I did this for the previous launch, Iridium-1, and was treated to unbroken views live from the first stage on the technical stream, while the hosts narrated and switched views more frequently on their stream.
1. Node Inspector (https://github.com/node-inspector/node-inspector), the most prevalent Node.js debugging tool, at least until Node v6.3.0. And which also happens to be mentioned by Jam3/devtool in the Comparisons section.
2. Built-in Chrome DevTools debugging support as of node v6.3.0 (https://medium.com/@paul_irish/debugging-node-js-nightlies-w...). Simply by running:
> node --inspect foo.js
For example, "GSL is likely a good choice at <abstract problem description>, such as <some very concrete examples>. And it may not be appropriate for <abstract problem description>, such as <other concrete examples>. Because of <some specific reasons>."
I looked through the GSL website and also Scalable C and wasn't able to find any descriptions that place limits on the applications of GSL. A description of what a complex something isn't, from an expert, is almost as important as what that thing is.
Your writing style in Scalable C is incredible and enlightening. I will be studying and referencing that book, even if I'm not directly coding C.
I feel either this distinction isn't important to many or that Square Cash is just widely unknown.
As an example, let's say that my graph DB has People nodes and a MARRIED_TO relationship between two people to indicate they are married. A MARRIED_TO edge could have a "married_on" property containing the date of the marriage.
Where would the "married_on" attribute be represented in JSON API? I could stuff it in the "meta" member of the link object, but that feels loose and hacky. Maybe it could live in the "linkage object" along with the "type" and "id" members. But the linkage object appears to currently be a closed set of only those two members.
Is this requirement to present a full property graph model not as common as I would imagine? I'm a bit behind on my sync with the current state of the spec. This is the first time I've tried to elaborate this need.
One challenge with the churn is a lack of any high-level changelog (git commit history doesn't count). I have a team working off an earlier version of the spec, and I check back semi-frequently. But I haven't been able to find a document outlining "here are the major changes since the previous versions." I understand that would represent more work on top of work, but for such a large spec, the changes have been disorienting.
It would be helpful to know more about what you do versus what you don't.
The ideal project would be something used within Comcast that doesn't otherwise have a corporate sponsor.
Coursera said as much that the Scala + Play community is modest in size.
My bank has free bill pay, so my wife and I have an automatic check sent out every month to a local all-volunteer charity that does very worthwhile work. We never see that money and we budget around the income we have left over. Whenever I peek at my bank statements and see those debits, I'm reminded of what we're doing.
Even a small amount, say $50/month, is a great start. This also forces you to find a worthwhile cause now, and to attach yourself to and actively re-evaluate that cause on an ongoing basis. It becomes a part of your life instead of your future.
All that said, thanks for the honest discussion. This stuff is important.
Second, the mirrored imgur photo is much smaller and compressed than the original photo to which the New York Times linked. If a crowd of people are attempting to identify an individual, it's unfortunate if many are looking at a suboptimal image. This should be a lesson NOT to use imgur for such a task. Just throw the original on S3 behind CloudFront.
Original, high quality photo: http://graphics8.nytimes.com/images/blogs/thelede/posts/susp...
Which brings up the fact that Yahoo did give us an organized Design Pattern Library replete with nomenclature, descriptions, and examples.
The bro connection had nothing to do with your photo. I didn't even look at your photo until you asked.
By the way, the earliest version of the Pixel Qi technology was used by the first OLPC XO laptop model.
Edit: Pixel Qis are not actually E Ink.
Is that still under debate? Would you be able to say "bitch" in front of your mother and not feel uncomfortable?