288 karma · joined April 7, 2016
Don't decide too early. If you can postpone a decision that doesn't delay your overall work, then postpone it. You may have more data later to take the right decision.
Don't optimize too early (premature optimization). Always try first the simpler approach, you will finish earlier, get simpler code and find out that some minor optimizations or not at all are needed. You should always check this with real world data / scenarios.
It does work fine, but sometimes you don't get some of the gooddies that you get in the latest js version.
> You want a stream of trees?
I was under the impression that is what GraphQL subscriptions are for but I haven't had the chance to try them. Isn't that so?
> You want to use GraphQL to upload attachments?
I have been using apollo-upload and it works quite well.
The generated key is encrypted and the user has access to it. So, you send the encrypted key and pay the randsome to get the unecrypted private key. Is that so?
She recovered quickly so she was released from ER to observation for 48 hours. In those 48 hours we would see new doctors and nurses every 8 hours, explain everything again, so they wouldn't miss any details from the history, and every now and then a doctor would come up with a new theory and order studies without first consluting with a specialist in that area.
One of this theories was epilepsy, after that we went to see a neuropediatric and dismissed the theory inmediatly, even before seeing the study.
All of this was in a stable condition, I can't imagine going through the same in critical condition. So, altough I think 30 hour shifts are excesive, I can understand why long shifts are important.
When I have to go back to programming in a language without const declarations it feels bad.
Interesting reading: How Naughty Dog Fit Crash Bandicoot into 2MB of RAM on the PS1 https://news.ycombinator.com/item?id=9737156