github.svg - GitHub in a Gitlab styled logo

javascript.svg - JavaScript written in a Java-styled font + the Java logo (Sun/Oracle)

pip.svg - Pip (the python package manager) styled in the npm logo style (node.js package manager)

rails.svg - Ruby on Rails with pretty much the rails logo, but in the color of WordPress. Also the "RubyOn Rails" text theming is in the style of the WordPress logo typography

react.svg - ReactJS in a the Angular logo, including the font style

rust.svg - (this one was truly painful, personally :P) "Rust" (the language) displayed in the node.js logo font styling, including colors

ubuntu.svg - "Ubunutu" styled in the debian (linux distribution) font styling, along with the debian logo. This one specifically, is where the hybrid feels the most accurate since Ubuntu is a debian-based linux distro, but I do believe the communities don't get along very well (or at least that's the running joke)

vscode.svg - VS Code (Visual Studio Code, the IDE/Text Editor) displayed in the "Vim" logo font styling and the logo with the stylized "V"

Comments URL: https://news.ycombinator.com/item?id=23603429

Points: 1

# Comments: 0

As such the evolution of human intelligence is largely an enormous chain of favorable mutations having been coupled and survived over billions of years. And each mutation that did occur was owing to nothing more than chance.

1. There were at the most 30-40 rows. Google Spreadsheets works amazing for small table sizes (although not as small as 30-40, I'd assume upto 1500-5000 should be fine as well).

2. All non-dev teams were EXTREMELY comfortable with Google Spreadsheets. For people with non-engineering backgrounds, a spreadsheet is an amazing, low-barrier entry to structured data which I believe is what made this solution amazing.

3. The dev team was completely removed as a dependency, and we had staging environments where they would run it first to ensure it was working properly, so a dev could be engaged only if their spreadsheet run wasn't working as expected or due to some other issue. The previous method was a huge email sent out to the devs, who would handcraft it into a JSON, which would then be passed to a script and then written to the database. This required every run to be effectively final.. there were only so many times one could engage a dev.

4. While we had to engage a dev to execute the script, it actually is very easy to integrate a menu option within the google sheets interface itself (if you are using Google Apps) for your domain, which would say something like 'Deploy to Staging', although we never got around to actually building this.

For startups where product turnaround time is required to be short, this works as an amazing solution as it makes so easy for non-tech guys to input data into the system. While there is no doubt that a fully developed panel for these operations would be the best solution, one doesn't always have the luxury of time.

The reason why I believe Kotlin is a great way ahead is - Great java interop, removes a huge amount of boilerplate, results in very readable code and extremely easy to learn (one of the reasons we could not switch to Scala was the steep learning curve which would be a big problem for new developers joining us).

Amazon is way ahead in the logistics game, even further than some of your flagship logistics companies.

[os.urandom(1)[0] < 128 for x in xrange(0, 100)]

and typed 'd' for True and 'f' for False in the array, bringing the accuracy of the predictor down to 53%. Theoretically, I'm guessing doing it for large enough numbers should make it exactly 50%.

Comments URL: https://news.ycombinator.com/item?id=11803182

Points: 31

# Comments: 33

> (python is) the wrong tool for code of any size written for pay, because you’re doing your employer a disservice