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.

Comments

Sid Yadav 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? :-)
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.

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 operate on. The only re…

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…