Marcadores de Jose Alcántara

libro para aprender a trastear cifrado y criptografía con python

proyecto en python para facilitar la programación contra la API de Linkedin

Bueno, si Saturn es clase media, el listón está jodido ¿eh? Mi experiencia de haber vivido en Alemania es que tenían edificios enteros para ellos à la FNAC de Callao y cosas así… Así que si a ellos les ha podido esta situación creo que vamos a tener que ir pensando en hacer showrooming en las «flagship» de las grandes marcas rollo Apple Store, Amazon Store, ¿Google Store?, etc.

Interesante resumen de Leandro sobre cómo andan de demanda los diferentes lenguajes de programación

El ahorro es, básicamente, una obligación que tiene el banco de devolvernos el dinero que tenemos depositado allí. La deuda(por ejemplo, una hipoteca) es una obligación que nosotros tenemos con el banco. En el caso de una quiebra de una de las partes la solución puede venir dada por una quita de la obligación. En el caso de la quiebra de un banco la cosa se pone complicada, ya que los saldos no se compensan entre sí (no se resta ahorro menos deuda) sino que cada cosa va por su lado: el ahorro puede que tenga una quita o puede que tenga que pagarlo el Fondo de Garantía de Depósitos (si tiene saldos) y la deuda seguramente sea vendida a otro banco o empresa.

Creo que es interesante sobre todo el tema de las «jornadas laborales». Es un debate ya viejo en sectores aburridamente «antiguos» (que lo tienen fácil para mejorar en ese aspecto, claro… como los ¡abogados! http://www.forbes.com/forbes/2009/0112/026.html), pero que hace no mucho saltó a cuestionar no ya el hecho mismo de estar contratado para trabajar 8 horas al día (GigaOM http://gigaom.com/2011/09/21/social-media-multi-tasking-and-the-death-of-the-billable-hour/). Lo deseable es que hubiera avances en este ámbito, para evitar tener «empresas zombificadas» con personas cuyo mayor objetivo es encontrar un «trabajo-agujero-escondite» en el que poder escondernos del mundo real, olvidarnos de buscar trabajo aunque pueda ser mejor que el actual, etc. Pero soy moderadamente pesimista… al fin y al cabo, muchas personas prefieren ese trabajo estable aunque aburrido, y no todos los trabajos son intelectualmente reconfortantes (por más que sea un trabajo digno, alguien tiene que limpiar la oficina, etc.),… un tema interesante :)

Licencias más sencillas, menos fricción y mejor ecosistema que .NET 1 The licensing. My God, the licensing. It's not so much the money, as the infernal, mind-bending tax code level complexity involved in making sure all your software is properly licensed: determining what 'level' and 'edition' you are licensed at, who is licensed to use what, which servers are licensed... wait, what? Sorry, I passed out there for a minute when I was attacked by rabid licensing weasels. I'm not inclined to make grand pronouncements about the future of software, but if anything kills off commercial software, let me tell you, it won't be open source software. They needn't bother. Commercial software will gleefully strangle itself to death on its own licensing terms. 2 The friction. If you want to build truly viable open source software, you need people to contribute to your project, so that it is a living, breathing, growing thing. And unless you can download all the software you need to hack on your project freely from all over the Internet, no strings attached, there's just … too much friction. If Stack Overflow taught me anything, it is that we now live in a world where the next brilliant software engineer can come from anywhere on the planet. I'm talking places this ugly American programmer has never heard of, where they speak crazy nonsense moon languages I can't understand. But get this. Stand back while I blow your mind, people: these brilliant programmers still code in the same keywords we do! I know, crazy, right? Getting up and running with a Microsoft stack is just plain too hard for a developer in, say, Argentina, or Nepal, or Bulgaria. Open source operating systems, languages, and tool chains are the great equalizer, the basis for the next great generation of programmers all over the world who are going to help us change the world. 3 The ecosystem. When I was at Stack Exchange we strove mightily to make as much of our infrastructure open source as we could. It was something that we made explicit in the compensation guidelines, this idea that we would all be (partially) judged by how much we could do in public, and try to leave behind as many useful, public artifacts of our work as we could. Because wasn't all of Stack Exchange itself, from the very first day, built on your Creative Commons contributions that we all share ownership of? You can certainly build open source software in .NET. And many do. But it never feels natural. It never feels right. Nobody accepts your patch to a core .NET class library no matter how hard you try. It always feels like you're swimming upstream, in a world of small and large businesses using .NET that really aren't interested in sharing their code with the world – probably because they know it would suck if they did, anyway. It is just not a native part of the Microsoft .NET culture to make things open source, especially not the things that suck. If you are afraid the things you share will suck, that fear will render you incapable of truly and deeply giving back. The most, uh, delightful… bit of open source communities is how they aren't afraid to let it "all hang out", so to speak. So as a result, for any given task in .NET you might have – if you're lucky – a choice of maybe two decent-ish libraries. Whereas in any popular open source language, you'll easily have a dozen choices for the same task. Yeah, maybe six of them will be broken, obsolete, useless, or downright crazy. But hey, even factoring in some natural open source spoilage, you're still ahead by a factor of three! A winner is you!

donde decimos teléfono, podemos hablar del coche y muchas otras cosas que compramos y luego tratan de limitarnos el controls que tenemos sobre ellas. En EEUU se aprobó recientemente una ley que, entre otras cosas, prohibiría desbloquear el teléfono. Es un tema viejo: las telefoneras evitan que puedas arreglar/instalar/configurar tu teléfono como te de la gana. Pero no sólo ellas: los fabricantes de coches hacen todo lo posible para que tengas que pasar por el servicio técnico oficial y lo mismo pasa con muchos otros cacharros.

If it works, then it means more advanced intelligence-gathering systems, less spam, and Minority Report-style self-driving cars of the future. Sounds like a pretty good deal. But to produce a machine-learning system that’s “effective,” the agency states: “Improvements on the order of two to four magnitude over the state of the art are likely necessary.”

Bonito tour fotográfico

The reason it matters whether LBT is covered is that if it is then it would either be necessary to join (£££) the regulatory process or to face certain (rather than not quite certain) financial ruin should someone commence a legal process about any of the content of the blog — and since our group’s academic work is occasionally contentious, that’s not just a theoretical risk. It’s clearly most unsatisfactory that legislation this important is so unclear, and that the Government are determined to rush it through Parliament within days rather than thinking the complexities through… the 1991 Dangerous Dogs Act is usually cited as the poster child for knee-jerk legislation that is much the worse for the rush to put it on the statute books. We seem to be heading the same way here.