Diego Pacheco Tech blog

Branches are almost a religious topic on technology. Git made branches easier and the default approach nowadays. However, do branches always help us and improve the status quo? Do we understand where we are going and what goes do we have or are we just following the herd and choosing technology as a fashion choice? Branches can impact your Refactoring, Code Review, and Collaboration habits. Branches also have high relation with software architecture or the lack of then. Many teams want to do CI/CD or at least talk about modernizing the release technologies but do all teams understand the principles behind it. To answer these questions and many others: Today I want to share a slide cast I made about branches and SCM in general. Doing some reflections and thinking about the benefits and the issues around branches. So Let's get started! 

So this is a hot and problematic subject: Monorepos. IMHO there are good use cases for mono repo when your project is really one thing such as angular. However, there are good use cases for microservices. IMHO we should avoid extremes and just have one big monorepo for the whole company and at the same time avoid having microservices for everything. There is a need to strike some balance between maintenance, isolation, and organization. This is the first post about the monorepos, today I will cover the solution from Google called Bazel . In the next post, I will cover the solution from Facebook called Buck. All posts will have practical videos building mono repo with Java.  IMHO the IDE integration is not ideal for both Bazel and buck. There is some support for VSCode and IDEA but is far from being ok. So Let's take a look at the video.

Git is a awesome SCM solution.  Today GitHub is where everything happens.  Pretty much everything in sense of open source is there. It`s a great model todo contribution based on the idea of Pull Requests or just PR.  However git and github could be complicated sometimes and there are situations you need do some commands get things done properly. IMHO command line tool is best them UI tools - maybe because when i start using git was not good tools around. So today i just want to share a very simple Cheat Sheet for GitHub/Git that i use pretty much everyday - I would really love to create less branches and spent less part of my day doing this but unfortunately everybody is doing git full witch is not nice.

Hoje o dia começou bem. Quando abri o site do infoQ , via a notícia de que o svn 1.5 tinha sido lançado. Essa é uma excelente notícia para todos. O bom é que os clientes como por exemplo o tortoise para windows já foram atualizados também. O mais importante nessa versão são as questões de melhorias em relação aos merges. Isso vai nos facilitar a vida absurdamente. Outra opção interessante para quem utiliza o windows é o VisualSVN Server que também foi atualizado para a versão 1.5 do svn. Esse cara(VisualSVN Server) nada mais é que o bom e velho servidor Apache com o mod de SVN, mos o legal é que ele já tem tudo isso integrado e com uma interface facilitada para a criação e manutenção de repositórios bem como configuração de usuários e grupos. Valhe a pena conferir. Mas como eu disse antes a solução de merge Tracking que irá dar toda a diferença desse release e acredito isso facilitar mais a adoção da solução.