More from Vadim Kravcenko
Question: Answer: The post What I learned building a $1K MRR SaaS in 6 weeks appeared first on Vadim Kravcenko.
Question: Answer: The post Iām sorry appeared first on Vadim Kravcenko.
Question: Hey Vadim, So, I've been coding for money for about 5 years now. I've jumped around a lot ā Java, Javascript, Python, NodeJS ā you name it. The job market's been great, making it super easy for me to switch between gigs. I've done both full-time and contract work across many different companies. I think I've reached the level of being senior as I take on more and more responsibility. At every place I've been at, they seemed to love me. I always got the comments that I'm the best dev they'd ever had. But, personally, I've always felt a bit off. I'm good at bringing the team together and breaking down problems. Yet, there's always someone who can code better than me. They can whip up solutions way faster than I can. I get things quickly, but my code always seemed a bit messier. Now here is where it starts being interesting. I decided to switch jobs again, as Rust is the new fun kid of the block, I decided to switch things up by teaching myself Rust. Landed a job at a big-name brand recently, many thousands of engineers, and I'm feeling way out of my league. The devs here are on another level, I feel like everyone here is smarter than me, even the juniors are soo good, coming up with stuff I wouldn't even dream of. It's gotten to the point where I'm doubting if I'm cut out for this, especially having the title senior but not really being senior amongst my teammates. Makes me think of calling it quits. So, here's what my question is: How can I tell if I'm a good developer? Were my previous companies just bad? Now, I feel like I'm just not measuring up. Looking for some guidance or any advice you've got. Answer: The post How can you tell if youāre a good developer? appeared first on Vadim Kravcenko.
Question: Answer: The post Why software projects fail appeared first on Vadim Kravcenko.
Back when I was coding in 2007, my stack was straightforward. I had a shared hosting provider that cost me [ā¦] The post Infrastructure: From Zero to Enterprise appeared first on Vadim Kravcenko.
More in programming
Being focused is about doing less things, and giving more space to the stuff that matters. I am spread out on too many projects and I canāt give enough attention to all of them. Itās time to clearly sort out which one I will keep maintaining and which I should drop entirely. Chuttersnap Mikochi Mikochi is a self-hostable remote file manager Iāve started in 2023. Itās my most successful open source project. I personally use it every day, and thousands of people have adopted it and started using it on their own servers. This year the project has been receiving more and more attention. Maybe it just reached a critical mass of users. In practice, that means a bit more maintenance work, since people have been pointing out bugs and suggesting new features. At the same time, working on Mikochi is fairly enjoyable. Itās a small, self-contained project made with technologies I enjoy working with. Iāve got no complaints about spending some time working on it. Verdict: Keep maintaining Mikochi and actively continue improving it. Itako Itako is an investment portfolio tracking SaaS. I built it for the most part between 2023 and 2025. In terms of scope, itās the largest project Iāve done entirely by myself. Is it a success? Not really. There are definitely a lot of people who tried Itako, and some whoāve kept using it a bit. But itās not engaging enough for anyone to consider getting the premium plan. And honestly I donāt find myself using it that much. My view of investing and portfolio management has significantly shifted since I started this project. While I used to think that more sophisticated analysis would lead to better returns, I now realize that the only strategies that consistently make money are honestly stupidly simple. Or maybe itās a U curve: on one end youāve got a monkey throwing darts, on the other end youāve got Jane Street, and everyone in-between fails to beat the market. Anyway, the biggest issue with Itako is how dull working on it is. The interesting parts of the projects are working on statistics and data visualization. But in practice, 90% of the time is spent tediously fixing data, understanding why some German stocks have an exchange labelled XETRA instead of XETR, why some Belgian stocks still have quotes while Euronext shows them as delisted⦠Verdict: Shut down Itako today. Milou Milou is static site generator for press kits. It started as a fork of presskit.html which was completely abandoned at the time. Itās a very useful tool. At Tsukumogami, itās part of our Cloudflare pipeline which builds our website in a few minutes whenever we need to change something. It seems like a few other game studios have picked it up, although I rarely get any feedback about it. Iāve not spent too much time working on it in 2026. I think it could be interesting to come back to it and add a feature or two. Better support for multiple languages could be an idea. At least, I need to make sure we donāt fall into the good old Node.js dependency rot. Verdict: Spend some time on Milou. Luluka Earlier this year, I created Luluka. Itās a CLI that allows previewing the output of Ebitengine shaders. I do still think Ebitengine is a great engine and Go is better suited for game development than most people realize. However, after quite a long period of experimentation around it, weāve decided to remain a Godot studio. On top of having quite a large sunk cost in infrastructure surrounding Godot, the tooling and possibility of doing 3D games still makes it a more attractive engine for our use cases. And Iāve been doing a lot of 3D work lately, so better put those hours to use. Verdict: Archive the project. The rest Iāve had a lot of good ideas that stayed as almost empty repositories in my GitHub. For example, Hakumei was a terminal companion to Mikochi. I made a few commits on this project and never found the time to work on it again. I have to admit Iām probably never going to have the time to work on all those repositories. Time to archive them all!
Internalize this graph, we post it on this blog a lot. If trends continue, China will have 10x the electricity of the US in 10 years. Whenever you think about geopolitical strategy, always keep it in mind, because whatever your plans are must consider this. Hereās a strategy that would make sense for America long term. Sell as many AI chips into China as possible, use the money to purchase solar panel and battery factories, and build out electricity capacity as quickly as possible. Fundamentally, compute is a function of electricity. Thatās the sort of long term thinking that gives America a chance. With robotic labor, immigrants like Jensen and Elon, a business friendly culture, and an incredible chunk of land, itās not so clear who is ahead in 50 years. Regardless, I do know this strategy would lead to massive prosperity for the citizens of both countries. However, thatās not close to what we see happening. We see a lot of short term zero sum thinking in action. Itās very scary what the US āAI raceā mentality leads to. When exactly does the race end? Whatever capabilities you have today will eventually be matched, unless⦠ā¦you believe that you can use ASI in a decapitating first strike. Iām worried that this is what these people see as the only way out. It probably doesnāt work, can you outthink steel and drone production? I donāt see how, see my critiques here. But Iām not totally sure, Iām not a superintelligence. And if it does work, that may be the end. My likelihood of imminent WWIII went up a lot with the nationalization of NVIDIA.
This post was previously published through my newsletter on November 9, 2026. From time to time, I will republish newsletter issues on my blog here if I think people (and search engines) might benefit from it. If you want to read everything Iāve written once it is posted, I recommend signing up for the newsletter. If youāre doing anything to stay on top of what is happening in the world of software testing and test automation, like browsing or even posting on LinkedIn, which I stopped doing for the foreseeable future, or reading blog posts - my preferred way of keeping up these days, and I highly recommend Dawid Dylowiczās excellent Software Testing Weekly aggregator mailing list if you prefer longer-form reading, too youād be thinking that AI has consumed our entire field, and that everybody (or at least those who post or write in public) is an AI expert these days. The reality, though, is far from that. Yes, some people use a lot of AI, even when I would only call a small fraction of them āexpertsā. I definitely do not classify myself as an āAI expertā, by the way. A much larger group uses AI on a less frequent basis, and theyāre getting some value out of it. Sometimes more, sometimes less. Thatās the group Iām probably in. And then thereās a group of people who havenāt really been using a lot of AI at all so far, beyond maybe the odd prompt to ChatGPT or Claude. I donāt have the actual numbers, but I suspect that this group is a lot larger than you would think from browsing your feed or surfing the blogosphere. You just donāt see them, because theyāre typically not the people who do a lot of work in public. A few weeks ago, I started working with a small group of testers to teach them how to use AI in their daily work. This work covers both test automation as well as broader software testing tasks, as some of them contribute to automation on a daily basis, but not all of them do. Iām working with them one day per week, on average, for three months, and weāre making small steps towards making AI a more prominent tool in their tool belt. So, what are we working on right now? Iām pulling ideas from my āValuable Feedback, Fast with AIā course, and so far, weāve spent some time setting up Claude, going over some important concepts such as context windows, models, tokens, and (of course!) the probabilistic nature of LLMs, and what that means for the results they provide. We have gone through several initial conversations, using Claude to learn more about and review specific user stories, which was an excellent segue into using talking about MCPs and setting up a connection to both Jira and Confluence using the Atlassian MCP. Last week, we also started experimenting with writing straightforward skills to make it easier for Claude to repeat certain actions in a structured way. These actions ranged from reviewing stories and acceptance criteria to refactoring small chunks of code in their (Robot Framework-based) test automation suite. What I loved about this is the avalanche of ideas that popped up in their heads when they saw how easy it was to use Claude. We made a short to-do list of ideas to try out for the next couple of weeks, and Iām looking forward to seeing them getting more confident around using Claude. One thing I have noticed is that their level of comfort around using AI varies quite a bit. Some of them are naturally quite cautious, which means theyāll ask ācan we really do this?ā and āshould we really do this?ā frequently before even submitting a single prompt. This is a good habit, I think, but weāll have to do some work to get them more comfortable with using LLMs, without losing too much of that caution. Others in the group are the opposite: I need to hold them back a little, because otherwise theyāll create a beautiful mess within days, simply because they see so many opportunities to use Claude in their work. That, too, isnāt inherently bad, but I do want to teach them not just how to get the most out of an LLM, but also (more so) how to use AI prudently. Over the next couple of months, weāll dive deeper into writing better prompts, creating and structuring skills, better context management, and creating and using agents, and probably a few more things, too. Iām looking forward to seeing these people grow more comfortable around using AI in their daily work, and figuring out where AI genuinely adds value and where it doesnāt in their own context. Is there a deeper message in this newsletter? Maybe not, and Iām just happy to tell you about this project, and how it is a great example of a what I call ācorporate mentoringā, a very efficient way of teaching a small group of engineers new skills, within their own context. But maybe itās also to show you that, despite what you might see on the Internet, especially those places featuring a lot of self-congratulation (Iām looking at you, LinkedIn), not everybody out there is an AI expert. At least not yet. So, if you feel like youāre ābehindā simply because youāre not running at least 17 agents continuously, creating 5400 merge requests per day, know that youāre not alone. Quite far from it, I would say.