As a web developer and CTO with over 15 years of experience, I am passionate about building profitable small SaaS products and pursuing Go-to-Market strategy for them. My areas of expertise include high performance, networking technology and APIs, SRE, automation using Puppeteer.js, web scraping, and SQL databases.
Do you know what I like about PHP? It is designed to die after execution. You should not fear code duplication, or bad formatting of code, of bad variables naming - mentioned artefacts of code smell are bad, but are nowhere close to statefulness in terms of contaminating your code.
One year ago I've published a post about reasons why our team chose Vue.js over React for our qwintry.com project rewrite. I've made some predictions back then: I expect Vue to become a primary JS framework in 16-24 months if Evan You makes right steps, at least around
Qwintry team recently started active migration to Vue.js as a frontend framework in all our legacy and new projects: * in legacy Drupal system (qwintry.com) * in our new, completely rewritten qwintry.com branch * in Yii2-powered b2b system (logistics.qwintry.com) * in all our smaller internal and external projects (mostly
While working on new Qwintry.com tasks we needed to provide our operators the interface to rotate uploaded images (and I wanted to rotate the original image file). Surprisingly, I could not find anything like that among d.org modules so I have to come up with my own solution.
I was not posting to the blog for a long time, and finally it’s time to share my experience with new project. This post will also cover some badly structured thoughts about PHP frameworks :) Qwintry Logistics (I will use QWL further in text to avoid typing these words again)
In 2013 I was invited by Packt Publishing to play a role of technical reviewer in one of their books. Just got my sample of the book Premium Drupal Themes by mail. It was an honor and nice experience for me, and now I hope to find time and become
