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
- How To Do Lessalexturek.com
- How I ship projects at big tech companiesseangoedecke.com
- Stop just using “Frontend” or “Backend” to describe the Engineering you like - Michelle Limmichellelim.dev
- Push and pullbitsofwonder.substack.com
- Some reasons to work on productivity and velocitydanluu.com
- Good Engineer/Bad Engineerterriblesoftware.org
- Git Guides - git pushgithub.com
- How I Find Problems to Solve as a Staff Engineerlalitm.com
- What can strong engineers do that weak engineers can't?seangoedecke.com
- Planning for unplanned worklinear.app
- Breaking the "senior engineer" ceiling - DEV Communitydev.to
- Design Engineeringmarcelochaman.com