The evidence is easily accessible - next time I suggest you just research a little bit first instead of going straight to speculating.
817 karma · joined July 2, 2009
The evidence is easily accessible - next time I suggest you just research a little bit first instead of going straight to speculating.
From Wikipedia [1]:
> Following Google's corporate restructuring under the conglomerate Alphabet Inc. in October 2015, Alphabet took "Do the right thing" as its motto, also forming the opening of its corporate code of conduct.[1][2][3][4][5] The original motto was retained in Google's code of conduct, now a subsidiary of Alphabet. In April 2018, the motto was removed from the code of conduct's preface and retained in its last sentence.[6]
- FX "expand/collapse" functionality seems way better for exploring APIs whose shape you don't know
- jid is maybe marginally better for APIs where you have instant recall of the exact shape and need to rapidly query it
Overall, I like FX better because it provides feedback on your query faster.
I am grateful to the author(s) for creating it and I'll be using it instead of JQ whenever I need to wrangle APIs from the CLI.
I know I’m being a beggar and beggars can’t be choosers, however, I believe that there are folks here who could solve this problem and make a nice living off of it. Hope someone reads this comment and builds something to address this.
1). On HOWTO articles about infra (1/2): I'd like to see more articles that lead with requirements, rather than setups that then justify the setup with requirements. Like, congrats, you managed to host a bunch of web applications via containers on a dedicated server. It's really nice for a super personal project and I'm sure it helped OP gain a lot of operational experience across several domains, but I just find this type of article to be "DYI porn" for a highly specific subset of DYI.
2). On HOWTO articles about infra (2/2): Is there any sort of comprehensive infra setup guide out there? Even something that just covers "core" AWS services (CloudFront, EC2, ELB, ECS, Lambda, CloudWatch, CloudTrail, and a few others...) feels like it would be incredibly useful for so many people.
3). "AWS on Rails" - I feel like we're getting close to a time when "AWS on Rails" emerges and we see the birth of a new opinionated tool that says "Most people just want to ship their product, not fiddle with cloud infra. Do it our way and you can focus on product instead of infra"
Someone going on a rant about how miserable they were about having too much sunlight, while at the same time being incapable of applying incredibly common trivial solutions to solve this calamity - I found this quite silly and it made me a bit upset.
1. joining any one of the other 99.9% of companies where the CEO is not a sun worshipper?
2. if (1) not an option, using blinds?
This seems unnecessarily complex - have you considered replacing this with rsync + cron job?
Solving problems is incredibly important. You can often succeed with that alone. The most successful ventures do both.
The paper was originally graded by a TA who gave the "C" grade. Watson appealed the grade to the professor. The professor reviewed it and upheld the "C" grade, stating that he had not sufficiently convinced her that the amendment was still alive.
https://en.wikipedia.org/wiki/Twenty-seventh_Amendment_to_th...
Crazy that no one’s made this before
Protagonist visits a highly advanced planet where everyone lives on their own plot of land. People lead lives of leisure, all of their needs are taken care of by highly efficient robots. However, they are terrified of physical contact, especially with the protagonist, due to a risk of infection with off-planet viruses. Here’s where it gets kinda scary:
- all interactions are done via advanced telepresence. It’s been perfectly replicated to mimic physical interaction. People only meet in person, apprehensively, for reproductive purposes
- one of the main supporting characters is an extreme extrovert who subliminally craves physical human contact. Due to society’s rules, the only thing she’s able to do is take lots of socially distanced telepresence walks with a friend.
This book was written in 1957.
I’m curious - how do Elm and Kotlin solve these problems in a way that balances the often competing goals of “add types to reduce errors” vs “have a high productivity environment where it’s quick and easy for engineers to write new code”?