Back to Blog

    The "Non-Nagging" Developer: How I Respect Your Time

    Filippo Tinnirello

    The biggest fear agencies have with freelancers isn't bad code—it's high management overhead. You want to hand over a task and know it will get done, without your phone buzzing every 10 minutes with trivial questions.

    Autonomy is a Feature

    I understand that when you outsource, you're buying time, not just code. If I spend 4 hours of your day asking clarifying questions that I could have figured out myself, I haven't saved you any money.

    My default mode is autonomy. If a font size isn't specified in mobile, I use my judgment. If an icon is missing, I find a matching placeholder. I solve the problem first, so you don't have to.

    The Difference Between "Nagging" and "Value"

    That doesn't mean I stay silent. I simply filter my communication. I only "nag" (interrupt you) when it brings value or prevents disaster.

    I Don't Ask:

    • "Can you resize these images?" (I handle all asset optimization)
    • "I need this in WebP format." (I convert files myself)
    • "What font is this?" (I check the design file)

    I Do Ask:

    • "This user flow has a dead end. Should we add a redirect?"
    • "The design uses 5 different H1 sizes. Can we standardize this for SEO?"
    • "This logical condition conflicts with the checkout process."

    The "Batching" Method

    When a project has genuine ambiguities, I don't drip-feed them one by one. I collect them into a single, clear list—usually sent once a day or once per milestone.

    This respects your "flow state" as an agency owner. You can answer 5 questions in 5 minutes at your convenience, rather than being interrupted 5 times throughout the day.

    Need a Developer Who Just "Gets It"?

    If you're tired of hand-holding freelancers, let's talk. I take ownership of the tech stack so you can focus on running your agency.