Magento

You might have been at the same point where i have been a few times: You want to start with integration tests on an existing Magento 2 store. You follow the steps to setup your IDE, start the first test and wait. After a while you get one of these nasty non descriptive errors:

This is question is asked and answered on Stack Overflow before, but it always surprises me how many people still don't know the difference. The difference is quite simply though.

To get your extension in the Magento Marketplace you have to comply with there rules. One of these rules is that your code must pass their Magento Marketplace Extension Quality Program Coding Standard, or Marketplace EQP in short. This is a set of custom Code Sniffer tools which inspects your code on quite a few common mistakes. For example:

Sometimes you need to share your local Magento environment with the world. This may be to share it with someone, to test it on a real phone, or to test some kinds of api response for example.

For my daily work as a freelancer i tend to use a lot of disposable environments: I use them to check a bug in that specific version for example, and them throw them away. Setting up Magento can be a lengthy process, but with this one liner i can bring it down to ~10 minutes, depending on you internet & cpu speed. It installs the required Magento version including sample data.

In my day to day life i tend to switch between Magento, Laravel and Symfony on a regular basis. Each system has it's pros and cons, but Magento has one pro over the other two: If you are using Magerun you can run console commands from any directory inside your project. It always bugged me that there isn't such a thing for Laravel, Symfony or other frameworks. That's why i created Shorty

In 2015 i started my company, Control Alt Delete. As a developer, i was always building websites for friends and family. As this started to get out of hand, i decided to make it official and start a company. I did this next to my fulltime job, but eventually started doing this for 2 days a week, and in 2018, i decided to go fulltime.

Recently I was in the process of migrating a Magento webshop to a SaaS webshop solution. Normally I would access the product and other data by using the API. In this case this was a problem as there was a lot of data that I was not able to access. I needed the output of blocks and some custom modules which where not exposed to the API.

Recently i was working on a Magento 2 webshop. It had a bug that when you visited the order grid you would get an exception. It was very generic, from the exception trace i was not possible to find the source. When i had a similar problems in Magento 1 the first step i would do was disable all non-Magento modules. This was simple, just move the xml files of the module you wanted disabled out of the app/etc/modules directory and you're done.