Woman on Rails

In one of my last articles, I was writing about improving names in the project. One of the tips was tell what pattern you use. Then I read a newsletter from Sandi Metz “Don’t Name Classes After Patterns. Mostly.” which have a different opinion about patterns in names. I think it is a good topic to write about it. There is no one silver bullet rule on how to do programming or create names. We have some tips, but those are the signpost. There are always some pros and cons, so it is good to have a wider perspective.

Some time ago, I was participating in an Instagram challenge called #30devstories. During that challenge, I create a lot of nice and short materials related to programming. I would like to share them with you using a more permanent way then InstaStory. I will start with TDD - Test Driven Development. In more details, I described this topic in the article TDD - Basics. Today I will focus only on a very short introduction to TDD.

As developers, we are often talking about high-level architecture. I mean DDD, hexagonal architecture, and so on. We want to introduce those concepts to our project. We want to do that now! The new concept, new architecture, new language, new framework. We fall into a trap. Technical news is for us like drugs. We want more and more. And we don’t think about the consequences. The goal is noble. We want to have a good quality project which can easily adjust to new requirements. Unfortunately, the way we do that is not always the best. We need evolution, not revolution. We need small, conscious steps. Today I would like to discuss one of those kinds of steps. Very important and also very hard. I would like to talk with you about naming thing.

In my current project, I use yarn for managing JavaScript packages. A few days ago, I needed a very specific version of a package from the GitHub repository. To keep it in mind, how to add a package from GitHub repository using yarn, I prepared this short note. I hope you will find it useful. I plan to do more this kind of short tips in the future.

Some time ago, I was using Sublime Text Editor for my programming work. For a very long time, I was satisfied with this text editor. But after some time, Sublime Text didn’t fit me as well as at the beginning anymore. So, I started research on something new. I found Visual Studio Code - free, built on an open-source text editor. Today, I will tell you more about this tool.

We had many Rails Girls workshops around Poland. The most known are in Warsaw, Poznan, and of course in Silesia ;). A few months ago, for the first time, I was a mentor on Rails Girls Bielsko-Biała. This was also the first time when workshops in Bielsko-Biała take a place. Let me show you a short report from these workshops.

There was a very simple code to implemented. It brings me a lot of fun when I started the research. I had an array of different objects and I wanted to join them into one string in a special way. An important question here was: How objects will look like after casting into a string? The answer was short - good ;) But this is not the clue of this article. The most important question is: Why objects are cast into string in this way? Here is what I discover during my research.

In article How to change parent branch in git? I talked quickly about using git rebase --onto in a case when you want to replace the current parent branch. But git rebase --onto is more than just replacing parent branch. We can do much more with git rebase --onto help. It’s a good topic to take a look closely. To use it freely first, you need to understand it.