|
Regarding mapping, note I said I don't rely on point-A-to-B directions for local trips. For long trips where I am not familiar with my destination, I typically plug it into Google Maps (that might change now, though I know of no appropriate substitute) and study the route, comparing alternatives. I write my route, both ways, on a single piece of paper. By studying my route, I am aware of confusing interchanges and such ahead of time. If I think a turn will sneak up on me, I write down the preceding streets intersected. Often the act of writing my route down means I never have to refer to the paper on the trip, a nice perk. I always could call the place if I get a little lost. On not using smartphones and being on this website ... I don't see the contradiction. I am a software developer, mainly working on sever-side software and some desktop development tools. The skills I claim to know (Erlang, JavaScript, Python, software design in the large ...) I know very well. No conveniences or lack thereof are going to change that. I don't really develop for mobile, except incidentally. My computing happens at a desktop or on a laptop, and I don't feel my experience or knowledge are limited, except in the mobile sphere. Even if all consumer computing were to move to mobile, there would still be lots of server-side software to be programmed. There's a whole lot of computing that happens outside of desktops, mobile devices, and networked services. I know little about firmware development and manufacturing software as well, for instance. I noticed you suggest you wouldn't care for my code ... it's true that best software I've written has not been open source, and I have a nasty habit of pulling down any project I am not very proud of. Peruse at your leisure: https://github.com/oinksoft |
"I'm not writing it down to remember later, I'm writing it down to remember now." – Unknown.