u/notomarsol

Looking for someone to help us edit faceless Instagram short-form videos every week.

What you will do:

• Edit Instagram Reels/short clips based on developer topics
• Add captions, cuts, zooms, hooks, and basic effects
• Make the videos feel engaging
• Deliver edited videos every week on time

Requirements:

• Know how to edit short-form Instagram content
• Understand hooks, pacing, captions, and retention
• Basic English writing
• Can do this every week without reminders
• Preferably comfortable making demos about latest AI news/tools

Details:

• Part-time, ongoing work
• Easy and simple if you know short-form editing

If you are not comfortable using After Effects or similar tools please do not apply.

DM me if you are interested! Please send one edited video clip as an example of your work.

curious where people are stuck because I feel like $1k is the hardest part and then it should snowball but for a lot of people it just doesn't. for me it's not the product, it's that I keep building instead of doing distribution. every time I sit down to do marketing I conveniently find a bug to fix or a feature to add.

is it pricing, is it positioning, is it that your niche is too small, is it that you hate selling, is it that you don't know where your customers actually hang out

genuinely curious what's the bottleneck for you

the original ticket was "add a filter to the user list." 1 point. estimated half a day. that was in early july

we are now in sprint 8 of this work and what we are actually building is a complete rebuild of the user management system with a new permissions model, audit logging for admin actions, and a redesigned admin interface that the design team is now calling "users 2.0." every retro someone says some version of "i cant believe this is still going" and we all laugh about it and then in the next sprint we add another adjacent thing because its "right there"

the creep happened in completely reasonable steps. the filter needed a search index. the search index revealed our permissions were checked inconsistently across 4 different places. fixing the permissions revealed we had no audit trail for admin changes which the security team had been asking for anyway. the audit trail meant we needed a real admin interface because the old one was readonly. and now we have a redesigned admin interface in figma that the PM is excited about because it solves three other tickets too. every step made sense in isolation

the codebase has gotten weird in the way that long projects get weird. half the methods have a v2 next to them. some of the old code is still there because we're not 100% sure nothing calls it. coderabbit comments on our PRs are getting funnier, last week one of them basically said "this file has 4 different patterns for the same thing, are you sure," and the answer was yes, we are sure, were aware, please dont remove the comment though, it helps the next dev understand what theyre walking into

the part that gets me is none of this was anyones fault. no individual decision was wrong. the PM didnt suddenly become evil. engineering didnt mismanage. the design team didnt overreach. but somehow we turned a 1-pointer into a quarter and im pretty sure if you put us all back in july with the information we have now we would have just made the same calls

next sprint we're "wrapping it up" which is what we said in sprint 5

since we leaned heavier into claude code and cursor over the last 6 months individual output has gone up a lot, but our review process hasn't scaled at all. PRs sit for 2-3 days waiting on the same 3 seniors who were already the bottleneck before AI showed up

we've tried smaller PR rules (helped a little), rotating primary reviewers (helped a little), explicit review SLAs (helped for about a month then slipped), and adding coderabbit on every PR for the first pass so humans only see the meaningful stuff (this one helped the most but still doesnt solve the architectural review part which is where the actual delay is)

honestly at this point i think the problem is organizational not technical. the volume of code shipped per engineer has gone up maybe 2x and the supply of senior reviewer hours is flat. and no amount of process is going to fix a math problem

curious what other teams are actually doing. specifically the 10-30 engineer range. is it more reviewers, fewer reviews, different review structure, accepting longer cycle times. genuinely asking, we havent figured it out

the original ticket was "add a filter to the user list." 1 point. estimated half a day. that was in early july

we are now in sprint 8 of this work and what we are actually building is a complete rebuild of the user management system with a new permissions model, audit logging for admin actions, and a redesigned admin interface that the design team is now calling "users 2.0." every retro someone says some version of "i cant believe this is still going" and we all laugh about it and then in the next sprint we add another adjacent thing because its "right there"

the creep happened in completely reasonable steps. the filter needed a search index. the search index revealed our permissions were checked inconsistently across 4 different places. fixing the permissions revealed we had no audit trail for admin changes which the security team had been asking for anyway. the audit trail meant we needed a real admin interface because the old one was readonly. and now we have a redesigned admin interface in figma that the PM is excited about because it solves three other tickets too. every step made sense in isolation

the codebase has gotten weird in the way that long projects get weird. half the methods have a v2 next to them. some of the old code is still there because we're not 100% sure nothing calls it. coderabbit comments on our PRs are getting funnier, last week one of them basically said "this file has 4 different patterns for the same thing, are you sure," and the answer was yes, we are sure, were aware, please dont remove the comment though, it helps the next dev understand what theyre walking into

the part that gets me is none of this was anyones fault. no individual decision was wrong. the PM didnt suddenly become evil. engineering didnt mismanage. the design team didnt overreach. but somehow we turned a 1-pointer into a quarter and im pretty sure if you put us all back in july with the information we have now we would have just made the same calls

next sprint we're "wrapping it up" which is what we said in sprint 5

i spent most of my career in java and typescript where abstraction is basically a competitive sport. every problem gets an interface, a factory, a strategy pattern, maybe a decorator if you're feeling fancy. half the codebase is plumbing for the other half. you read it and you can feel the cleverness in every file

started writing go for a side project last year and the language just kept saying no. no inheritance, no magic, no generics for most of its life, no clever metaprogramming tricks, no DI containers wired through annotations. just structs, interfaces, functions. at first it felt limiting in a frustrating way, like trying to write with one hand

then about a month in something flipped. i stopped trying to do the clever java thing and started doing the boring go thing, and the code got way easier to read. and not just my code, every other go codebase i've looked at since has been faster to navigate than equivalent java or typescript projects. theres usually one way to do something, you find it, you move on

the part i didnt expect is that this changed how i write typescript at work. im still doing typescript daily and i still use the language's features, but i reach for abstractions way less now. used to be id see a function thats called twice and start thinking about extraction, interfaces, generic constraints. now i let it stay duplicated for a while and most of the time it never actually needs to be abstracted, the duplication was fine

(also the readable-6-months-later thing isnt a small benefit, its enormous. i opened a go service i wrote in march and i was up to speed in like 20 minutes. that has not been my experience with my own typescript code)

i still think typescript is the right call for most of what i build. type system, ecosystem, frontend interop, all of that matters. but go changed how i think about complexity in a way that stuck. sometimes the best tool is the one that wont let you be clever, even if you only use it occasionally

Looking for someone to help us edit Instagram short-form videos every week.

What you will do:

• Edit Instagram Reels/short clips based on examples I provide
• Add captions, cuts, zooms, hooks, and basic effects
• Make the videos feel fast-paced and engaging
• Deliver edited videos every week on time

Requirements:

• Know how to edit short-form Instagram content
• Understand hooks, pacing, captions, and retention
• Basic English writing
• Can do this every week without reminders

Pay:

• $500/month
• Extra bonus if your work is good

Details:

• Part-time, ongoing work
• Easy and simple if you know short-form editing

DM me if you are interested! Please send one edited video clip as an example of your work.

something broke in prod yesterday. by the time i opened slack there were already messages about it, and 4 PRs from the last day that could be the cause, all of them passed CI, all of them got approved, all of them looked clean when i reviewed them.

it took me 3 hours to find it. race condition in a queue handler that only shows up when two events fire within about 40ms of each other.

the agent that wrote the code couldn't help me figure out why it broke. i tried, multiple times, different prompts. the bug wasn't in the code it generated, it was in how that code talked to another service from 8 months ago that someone who already left wrote. you cant prompt your way out of "this requires understanding the full system."

and this is where i'm losing it a little. the dashboards say we"re shipping 2-3x more PRs per week now. our leadership keeps sending around the metrics. but the time i actually spend AT MY DESK has barely changed, it just got rearranged. i write less code, i sit in more incident reviews

we have all the AI stuff btw. Claude Code, Cursor, CodeRabbit, Sentry, Datadog, the usual. coderabbit catches the obvious stuff at PR time which is great because it means the bugs that DO ship are the weird ones, the system-interaction stuff, the race conditions, the cross-service timing things. that part is still me at 2am with coffee, scrolling through traces

ok so the post-incident work has gotten HARDER not easier. when juniors wrote bad code i could usually figure out their reasoning by reading the code, even if the reasoning was wrong it was there. when an agent writes bad code there's no reasoning to recover. it just pattern-matched something that almost worked

different shape of problem entirely. yeah idk. our speed is up, defect rate at first review is down. but the average time it takes me to resolve incidents has gone up and nobody wants to talk about that one because its not on the dashboard