Skip to main content

Announcement: JournalApp 2.0 is Live

My Month-Project for June 2011 was the 2.0 release of the JournalApp tool I built during PyCon. I'm going to give a quick overview here, but I really hope anyone with the least bit of interest in what I do will go and look for themselves. I also think you should give it a try, but I don't think its for everyone. I think there are ways to sort your thoughts that work for us and we have different methods that will work best for us. This works best for me. If it works for you, great. If not, I hope you find something for you.

You can try it out now at GoJournalApp.com.

The easiest way for me to summarize it is to just copy-paste the help page right here.
Write. 
Write #awesome things and tag use hashtags to find them later. 
Find things by hashtag by typing only the tags you want to search. 
#likethis 
Have something to do? 
TODO: write todo's in your entries. 
DONE: and click them to check them off. 
ALSO: notice you can use "todo" or any word you want. 
Like searching for tags, you can also search for todo items, or whatever word you used. You can even mix them with hashtags! Here's how I find a list of books i want to read. 
#reading book: 
 Finally, while you are searching, anything you write gets the current hashtags automagically 
 You can use this to create separate notebooks, topics, or any other way you want to organize.
Labels:

Comments

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 operate on
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

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro
4 comments
Read more