DEV Community

Cover image for How I Use AI, Sticky Notes, and Pomodoro to Stay Productive as a Software Engineer
Piyush Chauhan
Piyush Chauhan

Posted on

How I Use AI, Sticky Notes, and Pomodoro to Stay Productive as a Software Engineer

As a software engineer juggling frontend and backend tasks, I’ve found that staying organized and focused is key to delivering quality work without burning out. Over time, I’ve developed a workflow that combines AI assistance, sticky notes, and the Pomodoro Technique to break down tasks, track progress, and maintain my sanity. In this article, I’ll share my process and how you can adapt it to your own workflow.


The Problem: Overwhelming Tasks and Context Switching

When working on a new feature or story, I often start with a vague set of requirements. Breaking these down into actionable steps can be overwhelming, especially when I’m still figuring out the details. Add in the constant context switching between frontend and backend work, and it’s easy to lose track of what’s done and what’s left.

To tackle this, I needed a system that:

  1. Helps me break down tasks into manageable chunks.
  2. Keeps me aware of my progress.
  3. Allows me to adapt as I learn more about the problem.
  4. Ensures I stay focused and hydrated (because, let’s be honest, we all forget to drink water sometimes).

My Workflow: AI, Sticky Notes, and Pomodoro

Here’s how I’ve structured my workflow to address these challenges:


1. Generate an Initial To-Do List with AI

When I start a new subtask, I use AI tools (like Perplexity.ai or Continue.dev with Codellama) to generate an initial to-do list based on the requirements. For example, if I’m working on a user login feature, I might ask:

"Generate a to-do list for implementing a user login feature with email and password authentication. Include frontend and backend tasks."

The AI might suggest:

  • Set up login API endpoint.
  • Create frontend login form.
  • Add input validation for email and password.
  • Implement error handling for invalid credentials.

This gives me a solid starting point with 2–5 high-level tasks.


2. Create a Feature Branch

Once I have my initial to-do list, I create a feature branch for the subtask. For example:

git checkout -b feature/user-login
Enter fullscreen mode Exit fullscreen mode

This keeps my work isolated and makes it easier to manage changes.


3. Work Incrementally and Extend the To-Do List

I start by tackling the first task on my list. As I work, I often uncover additional subtasks or edge cases. This is where AI comes in again. I’ll share my current progress and ask for suggestions:

"I’m working on implementing the login API. Here’s what I’ve done so far: [details]. What additional tasks should I consider?"

The AI might suggest:

  • Add rate limiting to prevent brute force attacks.
  • Log failed login attempts for security monitoring.
  • Write unit tests for the login functionality.

I add these tasks to my to-do list and continue working incrementally.


4. Track Progress with Sticky Notes

I’m a big fan of sticky notes for tracking progress. Whether physical or digital, they give me a visual representation of what’s done and what’s left.

  • Physical Sticky Notes: I place them on my desk or monitor, moving completed tasks to a "Done" section.
  • Digital Tools: If I’m working remotely, I use tools like Trello, Notion, or Todoist to manage my to-do list.

Crossing off tasks gives me a sense of accomplishment and keeps me motivated.


5. Stay Focused with the Pomodoro Technique

To maintain focus, I use the Pomodoro Technique:

  • Work for 25 minutes, then take a 5-minute break.
  • After four Pomodoros, take a longer break (15–30 minutes).

I assign specific to-do items to each Pomodoro session. For example:

  • Pomodoro 1: Set up login API endpoint.
  • Pomodoro 2: Add input validation for email and password.

During breaks, I make sure to hydrate, stretch, or take a short walk.


6. Create a Pull Request and Request Review

Once all tasks are completed, I create a pull request (PR) for my feature branch. I write a detailed PR description summarizing:

  • What was implemented.
  • Any challenges faced.
  • Testing performed.

I then request a review from my team and iterate based on feedback.


Tools I Use

Here are some tools and methods that have been invaluable in my workflow:

AI Tools

  • Perplexity.ai: For generating initial to-do lists and brainstorming solutions.
  • Continue.dev: For seamless integration with my IDE and local development environment.
  • Local AI Models: I use Qwen2.5-Coder 7B and CodeLlama 7B for code completion, debugging, and extending my to-do lists as I work. Running these models locally ensures privacy and customization.

Task Management

  • Trello: For visual task tracking with boards, lists, and cards.
  • Notion: For documenting requirements, progress, and reference materials.
  • JIRA: For aligning my tasks with team-wide project management and sprint planning.

Pomodoro Timers

  • Manual iPhone Timer: I use the built-in timer on my iPhone for Pomodoro sessions. It’s simple and effective.
  • Paper Checklist: I keep a handwritten checklist on paper to track tasks for each Pomodoro session. There’s something satisfying about physically crossing off completed tasks.

Hydration Tracking

  • Manual iPhone Timer: I set recurring reminders to drink water throughout the day.
  • Paper Drawing: I draw circles on paper and color them in to track my hydration progress. Each circle represents a glass of water, and filling them in gives me a visual sense of accomplishment.

Why This Works for Me

This workflow works because it:

  • Breaks down complex tasks into manageable chunks.
  • Adapts to new information as I learn more about the problem.
  • Keeps me focused with the Pomodoro Technique.
  • Provides a visual representation of progress with sticky notes.
  • Ensures I stay hydrated and energized throughout the day.

Example Workflow in Action

Scenario: Implementing a User Login Feature

  1. Initial To-Do List (AI-Generated):

    • Set up login API endpoint.
    • Create frontend login form.
    • Add input validation for email and password.
    • Implement error handling for invalid credentials.
  2. Feature Branch: feature/user-login

  3. Incremental Work:

    • Start with "Set up login API endpoint."
    • Commit: git commit -m "Add login API endpoint with email/password validation"
    • Ask AI: "What else should I consider for the login API?"
    • AI suggests: Add rate limiting, log failed attempts, and write unit tests.
    • Add these tasks to your to-do list.
  4. Sticky Notes:

    • Move "Set up login API endpoint" to "Done."
    • Add new tasks: "Add rate limiting," "Log failed attempts," "Write unit tests."
  5. Pomodoro Sessions:

    • Session 1: Work on "Add rate limiting."
    • Session 2: Work on "Log failed attempts."
  6. PR and Review:

    • Create PR with title "feat: implement user login" and description: "Implemented user login feature with email/password authentication. Added rate limiting and logging for security. Unit tests included."
    • Request review and iterate based on feedback.

Key Benefits of This Workflow

  • Clarity: Breaking tasks into smaller chunks makes complex work manageable.
  • Focus: Pomodoro sessions and sticky notes help maintain focus and track progress.
  • Adaptability: AI assistance allows you to dynamically adjust your plan as you learn more.
  • Wellness: Regular breaks and hydration keep you energized and productive.

By formalizing and refining this workflow, you can enhance your productivity, reduce stress, and deliver high-quality work consistently.


Try It Out!

If you’re feeling overwhelmed by your tasks or struggling to stay focused, give this workflow a try. Start small—use AI to generate a to-do list, create a feature branch, and work incrementally. Experiment with sticky notes and the Pomodoro Technique to see what works best for you.

I’d love to hear how you stay productive in your day-to-day work. Share your tips and tools in the comments below!


Happy coding! 🚀

Do your career a big favor. Join DEV. (The website you're on right now)

It takes one minute, it's free, and is worth it for your career.

Get started

Community matters

Top comments (0)

👋 Kindness is contagious

Immerse yourself in a wealth of knowledge with this piece, supported by the inclusive DEV Community—every developer, no matter where they are in their journey, is invited to contribute to our collective wisdom.

A simple “thank you” goes a long way—express your gratitude below in the comments!

Gathering insights enriches our journey on DEV and fortifies our community ties. Did you find this article valuable? Taking a moment to thank the author can have a significant impact.

Okay