I started out studying Finance & Econ, but building ventures like @LEARN__X made me realize the future isn’t built in silos.
Now I’m pursuing Computer Engineering at Iowa State, while minoring in business + econ, stacking tech depth on top of markets & strategy…
I saw a clip recently — “vibecoding during big tech interviews.”
Fun in 2024 when Roy Lee went viral, sure.
But honestly? You’re better off going deep on AI research.
The roles are shifting fast: Software Engineer → AI Engineer → AI Research/Data Science.
Everyone’s an “AI engineer” now.
Meanwhile 24–26 y/o interns are landing spots at top labs just by binge-watching LLM training talks and building something interesting.
Back in 2023–24 there weren’t even internship slots at these places.
Moral of the story:
Work your way toward becoming the next Karpathy. Sounds hard, but the competition is way thinner than you think.
Technically don’t need a phd in Math for sure. Most of the math you would have to understand is linear algebra and probability and a few statistics concepts but most of them you can learn while on the route of getting deep into AI.
Also most AI research has really moved from papers to implementation.
Pretty sure uni already model this, but issue is that international students already pay a lot so increasing the tuition will reduce enrollment to such an extent that the price increase won’t offset that decline.
On another note, pre-AI, it was also of national interest to have more international students for talent acquisitions (so did it really benefit schools as well — research etc)
Video projects should have proper history.
Most editing workflows still depend on one project file, an undo stack that disappears after you close the app, and filenames like final_v7_REAL_final.drp.
vedit adds a version-control layer for video editing:
- snapshot a timeline
- branch to try a different cut
- compare two versions in plain English
- merge changes back when the edit works
Instead of a wall of code, the diff reads like:
- Moved b_roll_03 before interview_take_2
- Trimmed drone_shot_04 by 1.80 seconds
- Added crossfade between title_card and drone_shot_04
The first release supports workflows around DaVinci Resolve, Premiere, Final Cut, but mostly AI-video editors.
It is early, but the goal is clear: video editing should be collaborative, traceable, and easy to undo across days, exports, and teammates.
PyPI: https://t.co/3nKBtgbUxu
GitHub: https://t.co/6i1aZW1twZ
just shipped vedit — version control for video edits.
snapshot timeline, branch, diff changes, merge. like git, but for cuts.
the diffs read like English:
Moved "b_roll_03" before "interview_take_2"
Trimmed "drone_shot_04" by 1.80s (in)
Added crossfade between "title_card" and "drone_shot_04" (12 frames)
works on anything that exports OTIO — Resolve, Premiere, FCP, or AI tools that generate timelines. there's a vedit watch mode that auto-commits every time you export from Resolve.
Rust core, Python bindings. very early (v0.0.1). would love eyes on it.
PyPI: https://t.co/3nKBtgbUxu
GitHub: https://t.co/6i1aZW1twZ