Husband, father of 👧 👧, and software developer living in the Metro Detroit area. Interested in continuous learning, tinkering, and exploring new technology.
LEARN.always
Serial podcast creator and .NET Core maniac.
Can often be found talking about everything and nothing on one of the many podcasts that he produces (only one of them is about .NET Core, honest)
Location
Leeds, UK
Education
Computer Science with Games Development - BSc
Work
.NET Development Contractor; Podcast host, producer and editor
If you'd have asked me how I prioritise tasks 2 years ago, I'd have said that I firefight. But these days, I take a look at what can allow me to check off the most at once.
One of the things which has helped me a lot recently, and it's super low tech, is pen and paper. Like, I'll write the heading:
What Do I Have?
And list everything that I have about a task. Do I have the spec for a job? Do I have access to documentations? Do I have the audio that I want to edit? Do I have the tools that I need?
Then I'll write the heading:
What Do I Want?
And list what I want the end result to be, in as much detail. For example, I might put something like:
To take this 80 minute audio, remove all of the dead air and multiple takes for certain questions, add indents, add an intro and outro, and mix it ready for release
That way, I can see the list of steps that I need to take to get to the final result, and precisely what that final result will be.
Then I'll make a check list of steps to perform, and check them off, one by one, until they're done.
The biggest thing to remember is that the individual tasks will take as long as they take. And if they go over, then it's not the end of the world.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Do you have any good tips on how you manage tasks? Tools and/or concepts? How you do prioritize?
If you'd have asked me how I prioritise tasks 2 years ago, I'd have said that I firefight. But these days, I take a look at what can allow me to check off the most at once.
One of the things which has helped me a lot recently, and it's super low tech, is pen and paper. Like, I'll write the heading:
What Do I Have?
And list everything that I have about a task. Do I have the spec for a job? Do I have access to documentations? Do I have the audio that I want to edit? Do I have the tools that I need?
Then I'll write the heading:
What Do I Want?
And list what I want the end result to be, in as much detail. For example, I might put something like:
That way, I can see the list of steps that I need to take to get to the final result, and precisely what that final result will be.
Then I'll make a check list of steps to perform, and check them off, one by one, until they're done.
The biggest thing to remember is that the individual tasks will take as long as they take. And if they go over, then it's not the end of the world.