How to not get bored with huge tasks? Break those to smaller ones. #GTD #buildinpublic
I am implementing undo and redo functionality. I need to define an undo command for every possible action in the app. Making that in one bunch is pretty monotone and can lead to errors. More⬇️
I created a list of all possible actions and now treat undoing every action as a separate small task. Now I can mix them with other tasks, still keeping track of what should be done for a big “undo” story. ⬇️
Keeping tasks tiny diminishes another problem: context switching. Because there is not much context to switch with small tasks :) ⬇️
So:
- Break your tasks to smaller ones
- Break your smaller ones to tiny ones
- Mix those with tasks from another area
- Keep a list of everything

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Pavlo Yevsehnieiev

Pavlo Yevsehnieiev Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @PavloDev

6 Jan
1/11 In this and some upcoming threads, I want to share with you some insights I am getting as a solo developer who builds a big product.

First insight: Write unit tests early, but not extensively

#BuildInPublic #webdevelopment #SoloDeveloperInsights Image
2/11 Since now I am fully responsible for product decisions as well, I am seeing a bigger picture. For example, where and when I need to compromise on code quality to bring an #MVP faster.
3/11 Compromising on the code quality infuriates my inner developer :) So I need a way to calm the beast and make sure that everything will be stable enough to make it to the launch. One way to do that is by writing tests.
Read 11 tweets
4 Jan
Creating a #SaaS #NoCode tool with real-time collaboration possibilities is quite the challenge, and there are a few resources that are helping me.
First of all — an awesome @figmadesign blog. I was thrilled when I read figma.com/blog/how-figma… — it has inspired me to work on a collaborative tool in the first place, and it has been my main source of insight about multiplayer.
Figma though is freer in its data structures since it does not use an existing technology of working with layouts. In my case, I need to comply with HTML and CSS. Some CSS properties, for example, backgroundImage, are not atomic — they could hold multiple values at the same time.
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(