Group items tagged

"What is the reason to quote at all? Consider it. It shouldn't be to allow people to scroll down to see all earlier discussions. If the news client is a bit smart, fetching the older articles from the server should be just as easy as to "scroll down". If a thread goes forth and back some times and earlier quotes accumulate, an article including all those quotes might get five-ten times larger than a posting without quotes, this wastes bandwidth and hard disk space. Therefore, IMHO, no quotes are far better than a posting at the top of all old quotes."

This article is a basic list of best practices that our Grails projects follow, gathered from mailing lists, Stack Overflow, blogs, podcasts and internal discussions at IntelliGrape.

"Most internal REST APIs are one-off APIs purpose built for a single integration point. In this article, I'll discuss the constraints and flexibility that you have with nonpublic APIs, and lessons learned from doing large scale RESTful integration across multiple teams."

In January of this year, @nvie published "A successful Git branching model", in which he explained how he keeps his Git repositories nice and tidy. In addition to that, he released git-flow; a bunch of Git extensions to make following this model extremely easy. I'm astounded that some people never heard of it before, so in this article I'll try to tell you why it can make you happy and cheerful all day.

"The best article I've ever read about architecture and the management of IT."

"The new Docker Registry 2.0 was released on April 16th, 2015. It was completely rewritten in Go with added support for the new Docker Registry HTTP API V2 (thus only working with Docker 1.6+), promising to provide faster and more secure distribution of images. If you work with Docker and for some reason decided not to use the public Docker Hub, a private Docker Registry is an essential part of your architecture. But even if you don't have private images, you will likely need to use your own registry in production/testing for efficiency. The default installation, however, runs without encryption and authentication. I was wondering what's involved in securing it. There is an official tutorial on how to configure TLS on a registry server. TLS/SSL is absolutely necessary for any secure setup, but I also wanted to enable an authentication mechanism. The Configuration Reference document describes two authentication options supported by Docker Registry itself: so-called silly and token solutions. The silly one is apparently only useful for very limited development use-cases. The token solution seems to be more serious, but because of the lack of documentation (at the time of writing), I decided to find an alternative approach to secure it. In this article I'm going to show you how to set up the Docker Registry 2.0 with username/password authentication and SSL using the official Docker Registry image and a custom configured nginx as a proxy server."

"Effective Go provides guidelines for naming packages, types, functions, and variables. This article expands on that discussion and surveys names found in the standard library. It also discusses bad package names and how to fix them."

"I published two such Tables of Elements about a year ago, click here to check them out. This one is a new one, focusing on machine learning libraries (R and Julia). And it is interactive, with access to the various libraries listed in the table, when clicking on an element (only on the original article)."

"In this article, we discuss the three-way relationship between three such desirable features - fairness, isolation, and throughput (FIT) - and argue that only two out of the three of them can be achieved simultaneously."

"Technical Debt is widely regarded as a bad thing; that should be avoided or should be paid back as soon as possible."

Buen set de tests comparativos entre varias implementaciones de paralelismo local.

Interesante lo de C

In terms of language popularity, much of the late 90s and early 2000s revolved around so called "managed" languages, such as Java or C#. Currently however, industry seems to be turning back more and more to native languages, and in particular two mainstream ones - C++ and Ada.