Our industry is a great one. It’s filled with a lot of awesome people building a lot of inspiring things and constantly seeking out ways to express just how much they love doing so. We’ve had blogs and podcasts, and right now hosting conferences is the big thing. Ever more people are organizing conferences, arranging meetups and creating memorable experiences. It’s fantastic to see.
Nothing compares to a good conference: the atmosphere of being immersed in a crowd of people who share the same passion as you, the lessons you learn and advice you take in, and the friends you get to meet and the new ones you make. You leave a good conference re-energized — full of zeal for your job and bursting with fresh ideas.
Suppose your company decides to change its code-hosting provider or you wish to move your own Git repository to a different host. It doesn’t happen often, but it happens. When I had to move a number of Git projects to a new host, it took me quite some time to find an accurate method.
Having made many attempts, and a couple of fails, and carefully reading Git’s documentation, I found a solid and effective way. I thought, then, that every developer would benefit from knowing how to migrate a Git repository to a new host quickly and easily. The most important thing is to make sure that your branches and tags and your commit history are all moved.
Coding or designing a page, it's always nice to have some basic templates you can quickly modify or adapt to your needs. However, at least once you have to know, how to create this "universal" template. In this case tutorials prove to be an ultimate solution, particularly if you just want to get an idea how something works and where to start from. In fact, you don't have to re-invent the wheel all the time - you can use existing solutions, modify and improve them and publish them as well - just the way other people did it for you.