When in "busy" mode I always kept a to-do list on the screen, the electronic version of multiple post-it notes. No fancy software, just a basic word processor. Type task in with start date and move from to-do section to done section with done date when completed. Helped a lot to staying organized and making sure all activities got done.
I keep a combination Log and To Do list in OneNote.
At the end of the day I organize the list so that when I arrive in the morning I can just start executing, not organizing.
At the end of a week / month / year it's nice to be able to see where your time went. It's invaluable for tracking tasks handed off to colleagues or outside vendors.
I use other pages and 'notebooks' in the OneNote app to save more detailed technical and project info so that's it's all in one place.
I do the same as you - "nothing breeds success like success".
But I'm often unwilling to look at the to do list so I tend to re-discover it the next day (or later), and if I'm lucky I can put a line through some more items on the list.
I admit it; I do keep a list for work that helps me keep on track and reminds me of small tasks that otherwise would be ignored.
However, for personal time, a list only shows up in my routine when is a day full of interaction and obligatory items with third parties. I have a more restful day without a to-do list.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.