22 | Engineer | code | music
Joined February 2025
- Tweets498
- Following240
- Followers111
- Likes1.9K
just noticed i havent used vs code in months , spent a lot of time in making it look cool but time to say good bye now
Does anyone know a good way to review pull requests? The average PR is now 4 k LOC and its not possible to read all that code. We have automated QA, but how should I, as a human reviewer, review it? Is there a tool for this? rn i just test it out and try to read imp files.
will be trying this
The CheatCode
read, learn, work, post, rinse and repeat
What to read: papers, eng blogs, GitHub commits, verified technical sources
What to learn: fundamentals, build, optimize, adapt fast, do the work even when you don’t feel like it
What to work on: different architectures/languages/stacks, projects that push past comfort
What to post: what you read, learned, and built
i thought x would improve after recent creator revenue changes but i still see people posting slop everyday for impressions not sure why
lesson learnt never give context of a bug/issue using a screenshot to codex i have seen this happening multiple time now. it just ignore whatever you say and focus on the image itself.
just got wispr flow pro free for one year with my student id :) it's been just one day since I started using it and i am already addicted to it.
