Tag: productivity

  • How I Work: from apps to index cards

    How I Work: from apps to index cards

    I’ve always appreciated seeing what gear, software, and workflows other folks use day-to-day.  It’s part inspiration, part curiosity, and sometimes a great way to discover that niche tool you didn’t know you needed.

    For years, Wes Bos’ /uses page has set the bar and the uses.tech site has turned this idea into a community catalog of developers, designers, and makers sharing their setups.  I’ve browsed more of those pages than I can count… and now, I’ve finally built one of my own.

    ???? Check out my /uses page here

    It’s a living list of what I rely on daily across:

    • Hardware (from desk to monitor to Oura ring)
    • Software and developer tools
    • My analog task system (3×5 cards > to-do apps)
    • Fitness and photo tools
    • WordPress plugins, themes, and host setups
    • Social platforms, backup strategies, and more

    I’ve also added some personal quirks, like how I stack-rank index cards each morning, what tools I’m still testing, and where I hang out online (ranked by actual usage).  It’s not just a list, it’s a snapshot of how I work and what keeps the machine running.

    As I tweak my setup, experiment with new tools, or shift platforms, I’ll keep the page updated.  If you’re into /uses pages, workflows, or just curious how other folks work, then I hope it’s useful.  And if you’ve got your own /uses page, I’d love to see it.  Drop me a link!

  • Why I Wrote a Personal README (and Why You Should Too)

    Why I Wrote a Personal README (and Why You Should Too)

    I value transparency, collaboration, and clarity whether that’s working with colleagues, contributors in the WordPress community, or clients.  But one thing has become clear over time: everyone works differently, and understanding those differences upfront makes for smoother, more effective collaboration.  Enter the Personal README.

    Inspired by Luc Levesque, Roy Rapoport, and 18F’s guide on Personal READMEs, I put together my own as a way to share how I work, communicate, and approach leadership.  It’s a snapshot of my work style, values, and expectations, both for myself and for those working with me.

    ???? Check it out here: jeffpaul.com/readme/

    Why Write a Personal README?

    A Personal README isn’t a set of hard rules, it’s a tool to set expectations, remove ambiguity, and help others understand how to best work with you.  It can cover things like:

    • Your working hours and communication preferences
    • Your approach to meetings and collaboration
    • What makes you excited (and what chafes you or makes you grumpy)
    • How you give and receive feedback

    By being upfront about these things, you can reduce friction and make it easier for colleagues to engage effectively.  It also helps new team members ramp up faster, since they don’t have to guess what works best.

    My Challenge to You

    If you haven’t written a Personal README yet, I highly encourage you to give it a shot!  Start with something simple and iterate over time.  Ask yourself:

    • What’s important to me in how I collaborate?
    • What do I expect from my teammates?
    • How do I like to communicate and make decisions?

    And if you do create one, share it!  Put it in your profile on social networks and communication platforms as well as your personal website (you own your own content right?!), basically wherever people can easily find it.  The more we normalize transparent communication, the easier it becomes to work effectively together.

    If you already have a Personal README, I’d love to see it!  Drop a link in the comments or tag me on Bluesky / Mastodon / LinkedIn or wherever we connect.

    Let’s make working together easier. ????