For people who didn’t know - I am working on my pet project for logging/tracking/analysing symptoms. App is designed only for my own needs.

Yesterday I got understanding that we are far from being replaced still. The app is fully vibe coded, I was only doing manual deployment to vm, I dont fully know how it works.

I am using claude in a very beginner mode, I gave him Claude.md, put sonnet4.6 and just explain what to do in single session, nothing advanced.


I added 2 features to react FE and nest BE (the easiest for ai to work with), and it broke ui in 2 places, one feature is just removed from ui silently. But the critical thing was that nest stopped starting up, so no backend.

It was trying to fix it for 20-30 mins, until I myself analysed what happened and gave him hint what can be wrong and then he found it.
Yes it is probably skill issue, but this is exactly the point. Random noname vibecoder would have skill issue as well. So even if we fully can trust ai, there is still skill needed to be able to properly set and maintain it so it does right thing and does not break your backend.

This leads me to the idea, that maybe QA aren’t done as I thought.

Right now with the vibe coding shit, code is cheaper than effort to validate what AI has produced. Since we cannot trust AI in testing (and in general) we need human being to ensure nothing is broken, all is working, etc.

And ofc security will be a thing. I mean mostly it can be automated as well, but there should be a human being ensuring it covered everything.

Daily (234/373 streak until LC cap)

BS problem, don't do it and don't waste your brain energy on it.

https://leetcode.com/problems/lexicographically-smallest-generated-string/description/?envType=daily-question&envId=2026-03-31

#daily #hard #nopattern

Do you know about ARP protocol in tcp/ip stack?
Address resolution protocol - is the way Ethernet resolves physical MAC address given Ip address.

Then the resolved MAC address is used to deliver the datagram to the physical device withing the LAN.

It is located on Link layer in Tcp/Ip layering, below Internet layer

This thing sucks. It completely misses the whole set of realtime communication components: socket servers/socket connections, propagating update to socket connections, etc.

Let me think about it, maybe I can vibe code it as well.

Moving this one from the comments so that more people see. I mean it generally makes sense, but I never approached vibe coding so serious, as I'm too lazy to put effort on the thing that I won't own mentally, I don't feel like it is mine and I don't have this desire to do it high quality:

Defining of MD spec files can be done through generating by Chat GPT / Claude Code / Copilot, etc.
1) Define CLAUDE.MD as PRS (Product Requirement Specification)
- PRS: Context, High Level Core Features, Project structure, Project Architecture, Tech Stack, Backend, Frontend, Infrastructure, etc.
- Out of scope: user-stories and tasks.
2) Define a user-story (WHO + WHY + WHAT, change not often) like Plan stage
- Business section like FRs: Context, Expected capabilities/outcome, Acceptance criteria, etc.
- Constraints section like NFRs (Technical, but without low-level details e.g. NO classes/functions/methods): Architecture, API, Data model, Performance, Security, etc.
3) Define tasks (HOW, may change) based on the user-story like Execute stage
- Low-level steps
- Must have testing tasks (Unit - required; Integration, E2E - optional) for verifying itself
4) Ask to implement the tasks of the user-story

https://tools.andreyka26.com/system-design
one evening, zero lines of code written or reviewed even, it is first shot, so not even beta, it is shita rather, but incrementally I will make it work properly.
Paperdraw - suck my balls😆😆😆

It is not only me, Ihor, who is my AI guru(https://t.me/ihor_codes) came up with idea, that there is no purpose to pay for bunch of SaaS if you can vibecode one for your needs in 1 week.

Daily (235/373 streak until LC cap)

Didn't solve as was busy during the day, but it feels like amazing hard problem, so for now I recommend it, but let me solve it as well

https://leetcode.com/problems/robot-collisions/?envType=daily-question&envId=2026-04-01https://leetcode.com/problems/robot-collisions/?envType=daily-question&envId=2026-04-01

#daily #hard

To think about. Love the analysis from Vlad

Daily (236/373 streak until LC cap)

Today is typical solid DP problem that you might be asked during real interview: definitely advise to solve.

https://leetcode.com/problems/maximum-amount-of-money-robot-can-earn/description/?envType=daily-question&envId=2026-04-02

#daily #medium #pattern

Daily (237/373 streak until LC cap)

Pretty hard and cumbersome problem, tbh it feels pretty large to reason about and effort consuming to reason about, but definitely not bullshit problem either. Up to you whether to solve it or not

https://leetcode.com/problems/maximum-walls-destroyed-by-robots/description/?envType=daily-question&envId=2026-04-03

#daily #hard

IMPRESSIVE. Claude pushed me back instead of hallucinating / bullshiting. Eventually they did it, I'm surprised in a good way.

Wondering how they did it, typically some months ago even explicit instructions to push back instead of bullshiting with temperature = 0 would still result in hallucinating rather than getting pushed back

Now legit I'm getting really annoyed and tired by this daily nonsense shit.

I started interviewing in Snowflake lately, and I see what people are getting asked. OMG for couple of times I was shadowing the interviewer for some senior positions. I cannot even explain how easy the questions they ask seem to me now after seeing this nonsense crazy bullshit daily leetcode problems.

I really don't know why other people are solving it consistently, and are there a lot of such people who don't miss single streak like me?

Leetcode really DOES have good problems, but they are all in lists, so usually they are top 500 first problems. 90% of daily - is ugly nonsense that no one would ask ever, and if so - fuck such company

===

Once I'm getting cap (4 months left) - I will be solving only exciting, interesting, applicable problems with measurable complexity (that you are able to solve in 1 hour, NOT FUCKING 1 HOUR TO ONLY UNDERSTAND THE SOLUTION)

BUT NOT PRESENCE INDICATOR IN TEAMS 😎🚦🚦🚦🚦🚦

Daily (238/373 streak until LC cap)

Today is not bad problem. First of all it is some real concept from computer science (I didn't know before). Second of all it is not that hard to be honest.

https://leetcode.com/problems/decode-the-slanted-ciphertext/description/?envType=daily-question&envId=2026-04-04

#daily #medium

So, it is the time. Do you want to try yourself for System Design? You remember I said I don't know the good real prod solution for Messenger System Design?

It is time to shine and give your ideas, while I'm prepping the article, so that I can consider all the possible ideas and challenge them whether they are scalable or no.