Existen ocasiones en las que requerimos que el contenido de una rama esté disponible en otra, sin realizar un merge
, ya que esto implicaría arrastrar otras partes del historial. Esto se logra mediante el uso de cherrypick
y, para simplificar la tarea, comenzamos realizando un squash
. A continuación la receta:
Este libro fue escrito en 2006, con una segunda edición en 2017 - yo lo leí en 2022 y siento que lo leí 16 años más tarde de lo que debería!
El uso de ambientes virtuales permite isolar las dependencias del proyecto de otras instaladas en las carpetas de sistemas. Cada .venv
contiene su propia version de los binarios de Python y sus dependencias. A continuación una simple demostración de como se podria organizar venv para compartir el proyecto de forma efectiva.
A couple of years ago I created a Spotify’s playlist where I add all tracks I liked, just as the main repository of things I’d like to listen to, no matter the mood I was when I added that song. As time goes, this playlist became less enjoyable to listen due to the change in rhythm - From listen to a Metal song it jumps to Bossa Nova, which is very annoying. This post contains a few data science approaches I applied to organize this playlist and what worked and what didn’t.
As I’m building a new startup I’ve been installing several Macbooks and helping engineers on their own setup, of course, we all have our kinks on configuring our machines but there is a base that would be nice to share and keep as standard as possible. Those are my (hopefully sane) defaults.
I’ve been working with static-typed languages for several years now, C# / Java / Scala developer and I like the safety and guarantees of having type checking, also the whole JVM ecosystem aged well with great building tools, libraries and lots of experience from the community. But I cannot ignore all the buzz around Javascript and I don’t want to be prejudiced about something I didn’t work directly for several years.
This is a very overdue blog post that I had on draft for almost an year, but I believe it is still very relevant yet.
Compartimos nuestra experiencia migrando de 100+ VMs a un cluster de Docker Swarm, los componentes y prácticas que brindaron estabilidad, control y cuales son nuestro planes futuros basado en ese aprendizaje.