4 ms·
I don't disagree but... If you're having a huge issue with this, I suggest trying to find ways to hold less context at one time. Write stuff down & get it out
by mattferderer 4y ago
I don't disagree but...
If you're having a huge issue with this, I suggest trying to find ways to hold less context at one time.
Write stuff down & get it out of your head more often. Write down all of your ideas & break down your tasks into smaller tasks. Don't try & solve a giant problem all at once without writing down what you're going to do. You may also discover issues earlier.
It doesn't get rid of the issue 100% but it helps a lot. I say this as a dev who has to do a lot of context switching.
- Casteil 4y ago>If you're having a huge issue with this, I suggest trying to find ways to hold less context at one time. For many who experience this regularly, that basically means leaving/finding a new job. With many employers, it's very difficult to escape being spread thin once you've proven your competence and they lean on you hard as a result.
- runlaszlorun 4y agoDo you write it down to read it? Or write it down just to write it down? I find myself doing the latter a lot lately- synthesizing rough ideas to a couple approaches or components and prob a little sketch. I feel a bit guilty that I toss them without reading but for me I think the value is it crystalizes my thinking by putting a pen to paper.
- mattferderer 4y agoBoth! Write it down to read it & not forget it. Write it down because the process often helps me better think about the problem & reasons my initial assumptions were wrong. Can't tell you how many times my clever initial idea becomes terrible rather quickly. Also if it's something that's going to exist over multiple days, writing it down & coming back to it at least a day later is a great way to re-approach the solution & idea.