Using the git-workflow method, in this document we explain some best practices and (naming) conventions on how to keep things organized and ‘easy’.

In this document, there are multiple references to git push --force related to rebasing on branches other than develop or master, please try to use git push –force-with-lease, or, when using my gitconfig, use git please :)

Git should be part of your main workflow when working on projects. A good branching model should be part of that as well. However, switching branches is not always auto-completed using the tab key. For this, you can find a script which fixes auto completion for you.

Coding standards

While developing within Magento, there are a few coding standards that Magento suggests, a few of which are available for PHP, JS, HTML and LESS.

Git is a great versioning tool. I use it in all my day-to-day activities and non-work projects. Basically anything I write, is versioned via git.

When wanting to time responses via curl, there’s a small layout you can use

When working with Python, it is generally so that work is done using virtual environments. Install virtualenvwrapper via pip install virtualenvwrapper --user

This small script shows how to truncate different kinds of entity tables within Magento2

In my day to day activities, I use the terminal pretty actively. I hate the idea of having many seperate terminal windows open, so I’m very happy with screen. According to the manpage, Screen is a full-screen window manager that multiplexes a physical terminal between several processes.

In order to keep track of active screens or display which screen is currently active, I use the following screen config:

You can write regular markdown here and Jekyll will automatically convert it to a nice webpage. I strongly encourage you to take 5 minutes to learn how to write in markdown - it’ll teach you how to transform regular text into bold/italics/headings/tables/etc.