Skip to main content

How To Review Memiary in 5 Easy Steps

This is how to review Memiary in 5 easy steps:
  1. Forget what you did yesterday. Check!
  2. Decide that all problems can be solved not just with software, but by adding new software just for that purpose. Check!
  3. Get written about on the popular ReadWriteWeb so people find you. Check!
  4. Be nifty enough to grab someone's attention when they try out the new service. Check!
  5. Surpass a plain text file in convienience, flexability, privacy, and install base. Damn! Maybe next time.
The best way to solve a problem is to avoid needing to solve it in the first place.

Labels:

Comments

Anonymous said…
So, you're saying, text files are so ahead in 'convienience' ('spell check' might help, btw, if you've heard of such a thing), 'flexability' (again), privacy, and install base, that Google Calendar, Remember the Milk, Microsoft Outlook, IWantSandy, and the hundreds of tools which have resulted in millions of hours of productivity saved should cease to exist?

I'm sorry, but I'm one of those who believes that innovation should exist at any cost. If I feel that I can come up with a solution to my problem, or better one already there, it is my job to make it happen, for me. If you don't want to use it, that's fine, but there is no reason something should 'not exist' in the world if you don't.

I think text files are great, I have used them all my life, and I can tell you now that for this purpose, they suck. Where is my 'oranize by month' option? Can I skip to a date? Do I have one big file with 10,000 lines of 'memories', or one for each day? Where do I put them? What can I do with this data? Do I really have to put the 'date' at the top each day? And does that really require me to click on my system clock and copy it out?

Read: whether you like it or not, the world will continue to innovate and come up with better solutions. That is what makes it all tick. If it were for you, I would be surprised if even the typewriter would have its day. After all, we can all use a pen and paper, can't we? :-)
4:29 AM
Calvin Spealman said…
Sid Yaday,

First of all, It doesn't bother me that I misspell anything. Spell checkers have trained us to think if there is no red squiggly line, everything is golden. Don't think you point out some flaw in my intelligence because I didn't memorize the same sequences of letters you did.

You might be right about text files and searching, if I didn't know grep so well. The thing is, how often am I going to look back? I'm going to write new things every single day. What is most convenient for what you do most of the time is more important.

Of course, a text file doesn't solve everything. This little "5 things a day" problem is teeny-tiny and Google Calendar, Remember the Milk, and Microsoft Outlook provide you with facilities you can use often and get more value from. Don't pretend they're in the same basket.
10:41 AM
Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...
Post a Comment
Read more