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.
![[DISCONTINUED] Scraping Instagram in 2021: avoiding 302 and 429 errors](/blog/content/images/size/w720/2021/01/IMG_20210112_114636.jpg)
Disclaimer: I don't do Instagram scraping anymore, and none of the approaches mentioned below are working reliably now, I think. Instagram is a tough target for scraping. For one of my side projects, I needed to get information from several public accounts, on a daily basis – for example, their followers
I've just started building a dashboard for my new project, which is an opionated Node.js API gateway (still in its infancy), with Clickhouse for logging: https://github.com/restyler/api-gateway. Here is what I'm telling you: in case you forgot, frontend world is full of bloat. Transpilers, bundlers, and
UPD 2020: Clickhouse is getting stronger with each release. We are using Clickhouse as an ELK replacement in our ApiRoad.net project - API marketplace with ultimate observability and analytics of HTTP requests. Clickhouse is an open source column-oriented database management system built by Yandex. Clickhouse is used by Yandex,
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
