Another year is in the books, and we’re thrilled to present our list of the top 18 visualizations from 2018.

Understanding money should be easy, and we aim to make it aesthetically pleasing too.

We are humbled by the continued growth of our audience. A big thank you to our readers for a great year, and we wish you all the best in 2019!

@jbeallurks I think monorepo has tons of benefits for small/medium teams. It just works and it keeps the team togethers. When the company grows, engineering leadership has to decide whether to commit to a monorepo or not. Also I think people also write plenty of software with monorepo :)

Me ten years ago, on seeing a poorly designed interface “Wow, what idiot designed this?” Me, today: “What constraints were the team coping with that made this design seem like the best possible solution?” Empathy trumps fundamental attribution errors.

I took the multi quarter sequence from Professor Donald Knuth in the 1970s. It was a mind blowing experience. I still see him at Zott's every now and then on a warm day. He remains as friendly, funny, gracious and, dare I say goofy looking (tall and Scandinavian), as ever. Taking the class was surreal. Many of us were undergrads who were struggling to keep up. This class was hard. Some in the class were Ph.D. Students. A really diverse mix. Knuth was awesome. He would give us undergrads something to chew…

You should choose a monorepo because the default behavior it encourages in your teams is visibility and shared responsibility, especially…

Писал сейчас derivation под nix для IRC сервера oragono и пришлось помучаться. Сервер написан на go и использует вендоринг, чтобы не увеличивать размер репозитория автор вытащил директорию vendor в отдельный репозиторий и это стало настоящей проблемой в виду обстоятельств, которые я опишу далее.

Чтобы собрать что-либо мне обычно нужно написать примерно такую декларацию:
{ stdenv, fetchgit, ... }:
stdenv.mkDerivation {
 name = "name";
 src = fetchgit {
   url = ...;
   rev = ...;
   sha256 = ...;
 };
 ...
}

Я собираю приложение на go и mkDerivation мне подходит, но есть более удобный вариант, чтоб не писать много - buildGoPackage. Так что моя декларация превращается в что-то такое:
{ buildGoPackage, fetchgit, ... }:
buildGoPackage {
 name = "name";
 goPackagePath = "github.com/example/name";
 src = fetchgit {
   url = ...;
   rev = ...;
   sha256 = ...;
 };
 ...
}

Эта штука(называется "languages & frameworks" в контексте nixpkgs), помимо прочего, автоматически настроит GOPATH и положит код так…