Maksim Ivanov | building usemont.com

Building a video editor for educators

[Maksim Ivanov | building usemont.com @ivanov_dev]

This is the “UNFOLLOW” tweet

If you see this and you don’t remember why did you even follow me in the first place - press three dots then “Unfollow @ivanov_dev”

[Maksim Ivanov | building usemont.com @ivanov_dev]

thanks for saying it directly, no worries at all

Not looking for personal brand help right now, but I appreciate the offer

when you say stale help videos are “silent conversion killers,” where have you seen that show up - onboarding, sales objections, or something else?

Happy to stay connected as well

[Maksim Ivanov | building usemont.com @ivanov_dev]

I’m testing a narrow wedge for Mont:

SaaS teams have onboarding/support walkthrough videos that become stale every time the UI changes.

Instead of re-recording the whole video, I’m trying to make each step editable.

Today I sent the first cold email to a SaaS team whose public help video already has an outdated-pricing note.

[Maksim Ivanov | building usemont.com @ivanov_dev]

@joshuapalassis Awesome! Joshua, would you be up for a 20-30 min discovery call, I’d like to hear more about your current workflow and pinpoints

[Maksim Ivanov | building usemont.com @ivanov_dev]

@SahilBloom How many single ingredient foods do you typically consume in one sitting?

[Maksim Ivanov | building usemont.com @ivanov_dev]

@fido_node Елду как то можно в Гулаге применить?

[Maksim Ivanov | building usemont.com @ivanov_dev]

@fido_node @punished_pie как их проверить? Если бахнуло значит были неисправны?

[Maksim Ivanov | building usemont.com @ivanov_dev]

@supabase Postgres direct (db.<ref>.supabase.co:5432) reachable. Dashboard says services Healthy. Status page silent

[Maksim Ivanov | building usemont.com @ivanov_dev]

@supabase prod down for us TCP/443 to the Cloudflare anycast IPs your DNS hands out for *.supabase.co (172.64.149.246, 104.18.38.10) silently times out from our path.
The CF IPs serving https://t.co/7J4hFDk4IT (172.66.x, 104.20.x) work fine same machine

[Maksim Ivanov | building usemont.com @ivanov_dev]

@TheGoldenDays kidney stones or smth?

[Maksim Ivanov | building usemont.com @ivanov_dev]

@Samaytwt Both are true

[Maksim Ivanov | building usemont.com @ivanov_dev]

Being a vibecoder is way harder that a regular programmer. Not only you still struggle with all the same problems, but on top of that all your effort is not recognised, because “the agent did all the work”. Well, it’s not true, who was pressing the “Yes button”? Who’s paying for the tokens? Who’s debugging all this slop while making sure to not be too rude (so that AI overlords spare you in 8 months from now)

If you are a vibecoder at heart and you get what i’m talking about - press that like button and follow my account. We’re in this together

[Maksim Ivanov | building usemont.com @ivanov_dev]

@Principal_Jon Come on man, that would be too good

[Maksim Ivanov | building usemont.com @ivanov_dev]

If you are vibecoding an app — you are this close to having to rewrite it from scratch. Watch this till the end and do exactly what I say.

Here is exactly what you do. And I need you to actually follow through, if you are doing it the first time your brain will tell you that it’s unnecessary, or too hard to do. Just ignore it

Open Claude. Ask it to launch subagents, explore your codebase, and return a diagram of how it works.

Now for every part in that diagram ask Claude two things: what is this part’s area of responsibility, and what are its inputs and outputs. Do that for every part until you can explain the whole thing in plain language.

Now you have a map. It highlights the problem areas. We tackle them one by one.

Follow me and comment architecture — next I’ll show you what to actually do with this map.

[Maksim Ivanov | building usemont.com @ivanov_dev]

@inkdrop_app Exciting, but at the same time quite dangerous

[Maksim Ivanov | building usemont.com @ivanov_dev]

@Cryptinflux Imo there is no other way that keeping everything explocit on architectural level

[Maksim Ivanov | building usemont.com @ivanov_dev]

Claude Code slows you down.
Not at first.
At first it’s the fastest thing you’ve ever touched. Prototype in a day. Feature before lunch. It feels like cheating.
But then you try to change something.
And the code resists you.
Because LLMs don’t architect — they patch. Every problem gets a new condition bolted on top of the last condition. Special case on top of special case.
So now you’re not slow because you’re writing too little code.
You’re slow because you’re drowning in code that nobody — including the AI that wrote it — actually understands.
Speed without architecture isn’t speed.
It’s debt with a good first impression.
The fix isn’t complicated — but it’s not obvious.
Comment architecture and I’ll break it down. 👇

[Maksim Ivanov | building usemont.com @ivanov_dev]

It's a bit weird that the best way to coordinate pepl at scale is some sort of "Monopoly" game

[Maksim Ivanov | building usemont.com @ivanov_dev]

5 things I learned from posting a video daily for 30 days

1.Daily > weekly. Taking a break guarantees more resistance next time you pick up the camera.
2.Allow yourself a low bar. It keeps the streak alive and the resistance manageable.
3.Make videos in the first half of the day. Leaving it till evening creates anxiety that lingers - and forces you into low-bar mode anyway.
4.Make it fun, not a chore. The moment it feels like an obligation, consistency starts to crack.
5.30 days isn’t enough for real traction. Some things work, some don’t - and figuring out a viable strategy just takes time.
I’m building a video editor and started this challenge to test it and find potential users. Still learning. Still posting.
Follow along if you’re on a similar journey