When working with Git, we often clone existing projects, since this is part of a typical collaboration workflow. What if we want to bootstrap a whole new project of our own?
It is a common practice to use `git rebase` to squash commits before creating or merging a pull request; nobody needs to see that you fixed 10 typos in 5 separate commits, and keeping that history is of no use. So how does a rebase look like?
But when multiple developers need to work in the same Git repository, it is important to define a process that allows collaboration. That's when branches become essential.
One of the most consolidated misconceptions about programming, since the early days, is the idea that such activity is purely technical, completely exact in nature, like Math and Physics. Computation is exact, but programming is not.
When we're getting started with [Git](), it can be difficult to understand where our files live, how they change state, and when exactly they leave our local machine to reach the external repository. I have an analogy for that.
Part 3 part of "Building minicli"
In this short guide, we'll set up an existing Laravel 6 application to use an S3-compatible object storage service for storing user generated content.
Tudo começou com um tweet criticando brasileiros "sem relevância no exterior" que compartilham coisas...
Remote work, when well supported, allows introverts and all sorts of neurodivergent folks to feel safe for expressing themselves better and at their own pace.
The DigitalOcean Community Monthly: Flask and Django on Docker, CI/CD with Semaphore, Building your Personal Brand and More!
The most popular tutorials of the last month, as well as other news