Want Attention? Show You've Put in the Effort

Developer Tom Bedor dropped a simple yet painfully true insight: if you want someone to give you their time and attention, you need to show that you've put in equivalent effort first. Sounds obvious, but how many times have we seen a GitHub issue with a single line "fix the bug" and no logs? Or emails from startups with a brilliant idea but zero prototype?

Bedor's rule is straightforward: before asking for help, do your homework. Gather context, describe the problem, provide examples. In other words, don't be that user who writes "it doesn't work" and vanishes, leaving you to guess whether the server crashed or they spilled coffee on the keyboard.

This is especially relevant in open source. Maintaining a project is like running a 24/7 diner: hungry users come with all sorts of requests, while the cooks (maintainers) have been at the stove for 12 hours. If a customer just yells "I want a burger," they're unlikely to get love. But if they bring their own ingredients and ask for help cooking — chances of success skyrocket.

So next time you're about to ask a question on Stack Overflow or request a code review, remember: investing human effort is like writing a meaningful commit message. Without it, your request is just an empty PR.

Studio METABYTE comment: At METABYTE, we also appreciate when clients come not with an abstract "make it cool" but at least with a rough spec. It saves nerves and coffee. And if you're still not sure where to start, we'll help — but please, jot down a few lines first.