Skip to main content

Someone Do This So I Don't Keep Wanting To

I'd like to say it is for lack of time, but the blame is equally (at least) on the shoulders of a lack of motivation. This is the blame for why all these little ideas never get made. Here are a few things I would love to do/make, but would even more so love for someone else to have already done. There are things I really want to build, because I am excited about building them. There are other things I really want to build, because I am excited about using them. For the second group, I'd just as soon find that someone else will, is, or already has built it.

Del.icio.us Bookmark Post Generator

I'd like to collect and blog the links I find throughout the day, but I can't find a good non-manual way to do it. The method I blogged previously didn't really pan out, unfortunately. I want a web app that I can give my del.icou.us account and have link posts generated for me, with options.
  • Minimum and maximum links to include in a post
  • Minimum and maximum time to pass between posts
  • Email, auto-post to Blogger/Wordpress APIs, or manually generate

Todo Sync

We have lots of places where we track things to do, between our bug trackers and websites like Remember the Milk and Evernote. I'd love a tool that can collect and synchronize these in controlled ways. I want bugs assigned to me added to RTM and I want checkboxes from Evernote notes added, as well.

User-Script Online Editor

It makes sense, as low impact as userscripts are, they should be editable and forkable on the sites that host them. This sounds simple, right? I started to write this, but just haven't found the time to finish it. Do you?
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 operat...
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

Using a React Context as a Dispatch Replacement

React Contexts are the pretty little bows of the React world. Here's a really quick example of the kind of messy code you can cleanup by using contexts, without dragging in a larger dependency like Redux or even Flux. Starting backwards with a diff showing lines of code I was able to remove: All the properties I was able to remove were just pass-through. The Carousel component didn't care about any of them, but it had to pass through these callbacks so the multiple TaskList components inside the carousel could invoke actions. They were removed from the Component class itself, too, since it no longer needed to pass them through. Where did they all go? My ActionContext removed all the need for these passthroughs by providing a single simple helper method, action(), that components rendered under it can access.   I really enjoy the pattern of passing a single callback through a context and removing what used to be lots of callback properties. Of course, I cou...
Post a Comment
Read more