Not really. Those tests will probably have gone through 1, 2 or 4 eyes. Also code linters and code quality checks. Hundreds of lines of code in a single function are not a good idea; and if it's got branches it will probably need code coverage tools to see if…

Aquí he venido a hablar de mi libro. Así que me lo quito de enmedio desde el principio. Helo: Venecia con calma: 1 (Venecia paso a paso) Venecia con calma: 1 (Venecia paso a paso) : Merelo, JJ: Amazon.es: Librosamzn.to ¿Conoces Venecia? Venecia es parte de la bucket list de mucha gente; un sitio único en el mundo, en la vieja Italia, los canales, las góndolas, Rialto, San Marco. Es muy…

En 2004, desde la revista Redes, se nos propuso analizar las redes de pases de los partidos de la Eurocopa de ese año y tratar de vaticinar el resultado. Lo publiqué en mi blog Atalaya y BloJJ, en varias partes. Los bits se han ido pudriendo y las imágenes desapareciendo…

Venecia lleva recibiendo turistas desde hace un buen puñado de años. Era una parte esencial del Grand Tour, que comenzó en el siglo XVII. Por eso, indicaciones como las de arriba, llamadas nizioleti, existen por toda la ciudad. Puedes imaginarte al diletante noble, dieciochesco, recién descendido del barco y queriendo…

Or how to solve puzzles in architecture and art (and tourism) using wisely your search engine

That make everyone’s life easier (including your own) — Most code is added to the main branch via pull requests. Many eyes (and tests) find more bugs or simply confusing code that just your own, so most projects nowadays, either closed- or open source, incorporate code to the main branch only through PRs. That’s just as well, but there…

Because the future is in the cloud(s) — A few years ago, I attended MS Build invited by Microsoft (and wrote about it quite extensively here). I guess that, in a way, I saw the light. But the light I saw was that of a cloud-centric future with a side serving of artificial intelligence. These are the notes…

It’s one of the best experiences you can have as a coder — This is kinda a reply to this article stating exactly the opposite: you should never code for a startup. As matter of fact, you needn’t dig a lot to find another article that says you should never do any kind of work for a startup. Well, my experience has been exactly the opposite. All my stints outside academia have been in startups. All of them amazing experience. And it’s been so for the following reasons

The Larries are sometimes the first to fail reviews or to be fired. Or to go to a place where they're paid better leaving a mess of barely comprehensible legacy code. Larry will probably be OK no matter what. But having Larry on a team? Not so keen on that.