scpotter
Open source screen reader: NVDA (www.nvaccess.org) Industry standard screen reader: JAWS (www.freedomscientific.com/Products/Blindness/JAWS)
Read GTD. It will inspire you and provide a path to success, walking you through creating meaningful todo lists. Many become devout followers, but for me just the basics and patterns were great to build on. There are concepts similar to the 'backlog' from scrum/XP, where you add a placeholder for every idea or task even very large ones, but only flesh out and break down into actionable items the near term / high value items.
Don't focus on tools, pen and paper are adequate, anything else is gravy. I use a location aware reminder app for short term/scheduled to-dos (iOS reminders, but before that Remember the Milk for years). The rest of the backlog and all details are in Evernote. Both are synced to all my devices (phone, ipad, laptop, etc) and available offline.
If I were trying to achieve your goal I would set a recurring weekday reminder when I arrived at the train station in the morning called "GTD". Just enough to remind me what I need to do. In evernote I'd have a folder with a todo list, plus all the notes/articles. Every day I would get on the train, review my todo app, see GTD at the top, open evernote to that todo, review/prioritize it and make as many happen as possible. The todo list I'd start with would be: Buy GTD Read GTD Create todo for reading/implementing GTD Read / delete pointless articles Find todo apps Create more todo lists
Love this. The question then becomes do you change the too, the way you use it, or some of each.
>A tool should not be designed only to "allow" people to do certain things.
You lost me here, because that's the definition of design. There are many hammer designs, some more general purpose like the claw hammer and many others (tack, 2lb) with a more limited intended purpose. Git is designed for very large scale teams, and staging seems to be integral to that. The paper asserts the complexity of staging is unneeded, but in my view doesn't adequately demonstrate that to be true for large teams. The paper goes on to describe an alternate, simpler product which better meets the needs of simpler users using and alternate, incompatible conceptual design. This is fine, but I'd be more impressed if it started by fully demonstrating a concept is not needed for the intended users before removing that concept and then described a pathway from a simpler concept to the fully complex conceptual model.
Truly best practice: don't collect SSN unless you truly must have it, and never use it as a foreign key. The government is probably worst offender here, because there are really no consequences to individuals or organizations and tons of legacy systems.
Still, I have zero issues with iOS 7 on my iPad 2 and my parents are happy on their 4S.
I'm not familiar with the UK, but in the US there is one important distinction between a pension and individual retirement accounts like a 401k, 403b, IRA, etc. Most pensions are defined benefits, meaning they are not controlled or accessible to the individual, they are, which are a promise for the future with zero individual control. The other instruments are ultimately owned and controlled by the individual.
You are typically limited to using the 401k your current employer offers if you want an employer contribution (which has a vesting schedule) and pre-tax investing, but when you change employers you can roll the money into another retirement instrument. The flip side is all responsibility for investment management, or even having retirement savings, is on the individual. Of course there are many people willing to help you manage it (for a fee).