Pull vs Push jobs | Manas J. Saloi
manassaloi.com · 331 words · saved by 1 readers
There are pull jobs and then there are push jobs.
There are pull jobs and then there are push jobs. In a pull job your work starts when someone asks. Someone needs data, analysis, approval, context, a deck, a bug fix, a report. And they pull it from you. You respond. You check the box. In a push job you create forward motion without waiting to be asked. You ship the code. You make the decision. You write the update before someone chases you for it. You spot the problem, frame it, and make progress on it without anyone following up with you. Pull jobs can still be valuable. Plenty of important functions are structurally pull-oriented.…
saved by
related reading
- Impact, agency, and taste | benkuhn.netbenkuhn.net
- What to care about in a job | benkuhn.netbenkuhn.net
- Don't End The Week With Nothingtraining.kalzumeus.com
- claude code is not making your product betterethanding.substack.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Stuff you should have been taught in college but weren’t – Casey Handmer's blogcaseyhandmer.wordpress.com
- Code was our medium for thoughtwattenberger.com
- How I ship projects at big tech companiesseangoedecke.com
- After Automation | Everyevery.to
- Nghệ thuật giao việc: tech lead edition (phần 1)substack.com
- Hey, N00b, We Didn't Hire You to Complete Tasksnewsletter.kentbeck.com
- How teams build – Linearlinear.app