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.
Some bigger companies still require wet signatures on documents, which was a source of constant hassle for me during recent years. My workflow was: * Receive email with the PDF document * Download the document * Print the document on my old friend HP Laserjet 1020 * Sign the document by hand, using a
![How to bypass CloudFlare 403 (code:1020) errors [UPDATED 2023]](/blog/content/images/size/w720/2021/11/andre-benz-Mn9Fa_wQH-M-unsplash.jpg)
I've recently started getting Cloudflare 1020 (403) errors when scraping some random e-commerce website. At first, I thought that the website didn't like my scraper IP address, but changing IP addresses to a clean residential proxy and even my home network didn't fix the issue. Strangely, when the website was
I develop all my new projects on a remote Hetzner Cloud machine, using wonderful and almost too-good-to-be-true VS Code Remote. I recommend this setup for everyone who does not like spinning fans of their Macbooks - and I really prefer Ubuntu and real Linux environment to brew when I setup
In 2018, I've written an article about Clickhouse, this piece of content is still pretty popular across the internet, and even was translated a few times. More than two years have passed since, and the pace of Clickhouse development is not slowing down: 800 merged PRs just during last month!
For one of my projects, I needed a widget which would render posts from an Instagram hashtag. It turned out to be very cumbersome to implement nowadays, because Instagram shut down its legacy API in 2020 and now the developer needs to go through a real nightmare to get approved
During my development career I used a lot of different solutions to daemonize processes (mostly, node.js scripts), and I decided to do a quick writeup with very short description of each approach to help fellow developers to choose. 1. Forever URL: https://github.com/foreversd/forever Github stars: 13.
