2,117 karma · joined July 26, 2011
[ my public key: https://keybase.io/vkravcenko; my proof: https://keybase.io/vkravcenko/sigs/rieRINFNWw8KYyOl6u5k7V9uX8mZqkJmHJYvmHV0Hm0 ]
Even though, in my case, users add their own domains, it's still took me quite a bit of time to reach 99% chance to crawl a website — with a mix of residential proxies, captcha solvers, rotating user-agents, stealth chrome binaries, otherwise I would get 403 immediately with no HTML being served.
And I'm trying to offer this "data advantage" to website owners, so they can grow, and also this is something that will be hard to replicate (at least quickly) with AI.
So I built a SEO/GEO Automation Tool for Small to Mid-Size Businesses who don't have a full-time team for that. [0]
The goal is to provide teams visibility across all the channels — Search and AI and give them the tools needed to outrank their competition. So far so good, the fully bootstrapped venture has grown over the last year and I've built quite a few big features — sophisticated audit system, AI Responses Monitoring, Crawler Analytics, Competitors Monitoring etc.
> Different naming conventions (DW_OP_* vs DW_op_*)
I’m working on SEOJuice [1], an automated tool for internal linking and on-page SEO optimizations. It's designed to make life a little easier for indie founders and small business owners who don’t have time to dig deep into SEO.
So far, I’ve managed to scale it to $3,000 MRR, and recently made the move from the cloud to Hetzner, which has been a game-changer for cost efficiency. We’re running across multiple servers now, and handling everything from link analysis to on-page updates with a bit more control.
The journey’s been a mix of hands-on coding (and a lot of coffee) and constant optimization. It’s been challenging but incredibly fun to see how much can be automated without compromising on quality.
Happy to chat more about the tech stack or any of the growth pains if anyone’s interested!
This was written 10 years ago when I was struggling with pulling and installing projects that didn't have any requirements.txt. It was frustrating and time-consuming to get everything up and running, so I decided to fix it, apparently many other developers had the same issue.
[Update]: Though I do think the package is already at a level where it does one thing and it does it good. I'm still looking for maintainers to improve it and move it forward.
I'm really curious to hear your thoughts and experiences.
Cheers :)
Mostly I help developers grow — I share my thoughts as a CTO about building digital products, growing teams, scaling development and in general being a good technical founder.
Some of the popular posts are:
- https://vadimkravcenko.com/shorts/things-they-didnt-teach-yo... - Things they didn't teach you at the university
- https://vadimkravcenko.com/shorts/project-estimates/ - Rules of thumb for Project Estimations
- https://vadimkravcenko.com/shorts/contracts-you-should-never... - Contracts you should never sign.
Most of the blog posts have ended up on the Frontpage here, here's the list: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
Cheers, Vadim
I made a note in the article to mention that there are a lot of different definitions of the roles, but usually, the definitions are the same, just a different naming convention.
We've switched from JIRA to Linear.app more than year ago, and never looked back. With JIRA our team members were getting blocked in the flows quite a bit, now with linear we're much more efficient.
Cheers, Vadim
https://en.wikipedia.org/wiki/Silent_majority#:~:text=The%20...
1. Many companies are agile, and the requirements constantly change, which makes implementing TDD even harder.
2. TDD does not bring enough value to justify the investment of time (for writing & maintaining the test suites), the benefits are negligible, and the changes are often.
3. Everything is subjective [1], and there's no reason to have such strongly held opinions about the "only right way to write code" when people write software in a way that is efficient for their companies.
[1] https://vadimkravcenko.com/shorts/software-development-subje...
In my opinion, good approach to avoiding the hedonic treadmill is to think in “processes” rather than “goals.” If you achieve some goal, you get back to the equilibrium and get used to it. But if you’re on a journey, there’s nothing to adapt to as every day is a journey and brings something new. So it's like smaller pendulum swings every day instead of big ones every few months.
Nonetheless, I like the ideas proposed in this article and think they also are quite effective.
I write mostly about how I build digital agency into millions of revenue, advice for early stage startups and scaling development to 100s of devs.
I mostly write about scaling early stage startups