torbjorn gannholm: The perfect programming language

https://cygni.se/the-perfect-programming-language/

I have always held that the act of programming is something that is done in an abstract realm and only later translated into a programming language. That programming should involve much more thinking than actual writing.

I mostly still stand by that but my years as a readability reviewer at Google raised my awareness of the fact that it takes time and practice to use a language well. Many were the hopeful C++ programmers who wrote fully functional and reasonably object-oriented code in Java but with a heavy C++ accent that couldn't quite meet the bar of elegance in Java (even if a C++ programmer might think it mostly elegant apart from the "flaws" of Java).

So how much does the choice of programmimg language matter? Is there or could there be a language that could be considered perfect?

Jacob Kaplan-Moss: How to Ace a Technical Interview

https://speakerdeck.com/jacobian/how-to-ace-a-technical-interview

Jacob Kaplan-Moss: My Python Development Environment, 2020 Edition

https://jacobian.org/2019/nov/11/python-environment-2020/#atom-entries

My setup pieces together pyenv, poetry, and pipx. It’s probably a tad more complex than is ideal for most Python users, but for the things I need, it’s perfect.

mnot.net "How Multiplexing Changes Your HTTP APIs"

https://www.mnot.net/blog/2019/10/13/h2_api_multiplexing?utm_source=dlvr.it&utm_medium=twitter

" HTTP/2 should put to rest any notion of the need to minimise the number of requests for APIs; the protocol makes them cheap enough to not practically matter. Go ahead and design a highly granular HTTP API to meet the needs of your clients. "

Tyk.io REST was NEVER about CRUD

https://tyk.io/blog/rest-never-crud/

A popular myth is that REST-based APIs must be CRUD-based – that couldn’t be further from the truth. It is simply one pattern in our API design toolbox.

This article outlines a variety of additional patterns available for REST-based APIs. The intent isn’t to be fully exhaustive, but to open the options for API designers uncertain about how to apply designs beyond CRUD to REST-based APIs.

lya Grigorik : Don't "Push" Your Pull Requests

https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/

There is nothing more frustrating than to read the threads, or even worse, be on the receiving end of this experience gone wrong. The contributor is wounded because they are not recognized, and the maintainer is caught in a dilemma: they want to build and foster their community, but they have to dig-in against their biggest fans. There is no winner here and neither side is to blame.
Next time, before you dive into the editor, open a discussion, outline your problem and solution, and offer to do the work - don't "push" the pull request, and don't work in the dark.

InfoQ: Getting to Know Graal, the New Java JIT Compiler

https://www.infoq.com/articles/Graal-Java-JIT-Compiler
Oracle recently announced the first release of GraalVM, a research project that may in time lead to a replacement for HotSpot in its entirety.
For Java developers, Graal can be thought of as several separate but connected projects - it is a new JIT compiler for HotSpot, and also a new polyglot virtual machine. We will refer to the JIT compiler as Graal and the new VM as GraalVM.
The overall aim of the Graal effort is a rethinking of how compilation works for Java (and in the case of GraalVM for other languages as well).