Blog

Django Basic Tumblelog 0.6

Published by Myles Braithwaite 1 week, 5 days ago. 0 Comments

Tags , , and

Just published the new version of Django Basic Tumblelog to PyPi. With this release I decided to go with the "One Idea" methodology i.e. their is no Bookmarks, Videos, etc. Models anymore, just one Model called Post. I am working on some documentation that I hope to release by version 1.0.

A Django Intranet

Published by Myles Braithwaite 3 weeks, 3 days ago in Planet. 1 Comment

Tags , , , and

At work I started developing a intranet, nothing to complicated just an address book, microblog, timesheet, and forum. I knew from the beginning of development I wanted to release the final project open source. But it was developed in the monolithic approach (one project for multiple ideas) so instead I am releasing one sentence ideas:

  • django-blogs: A multi-person blog similar to MovableType.
  • django-bugle: A microblog. (This isn't my originally code I forked it off Simon Willson's Bugle Project and made it a more portable application.)
  • django-calendar: This is a fork of my Asgard Calendar.
  • django-contacts: An address book application we are using to keep track of employee contact information.
  • django-forums: A Django Forum application.
  • django-issues: An issue tracker.
  • django-projects: An internal project tracker.
  • django-timecard: A timesheet without projects or issues.
  • django-timesheet: A timesheet for projects, tasks, and issues.
  • django-voting: An Apache Style voting application.

I still have to release django-voting, django-projects, django-forums, django-calendar, django-bugle, and django-blogs which will probably be some time next week and I also want to do a Pinax style release at the end of the month.

Adam Savage's Colossal Failures

Published by Myles Braithwaite 3 weeks, 5 days ago in Planet. 0 Comments

Tags

Ryugyong Hotel Ryugyong Hotel in Sojang-dong.

I don't know, I'm making this up as I go.

Sorry for the second Adam Savage related post, but I thought this one was interesting. Early working as a consultant I found myself saying yes to a project just for a paycheck (or to show my parents why I didn't need to stay in college) even though I really couldn't do what the client is asking for; but I would get the project done.

One time I got a really simple project from a new client, the project was so simple and I had so much school work the project got pushed to two night before it was due (which was the same day as an exam). They were using a custom web framework with no documentation or even comments in the source code and I couldn't finish on time. Around 6:45 am i left for school with the project unfinished. I got to school around 7:00 am took my exam finished by 10:00 am and went to the library to write an email to the project manager and tell him I couldn't finish and I was sorry. While instead of doing the write thing I went home and fell asleep and didn't wake up till 9:00 pm. Where in my email inbox was an email from my project manager which wasn't really good, but I dissevered every word in that email.

Since then I stop taking project I didn't have the time to finish. But this situation taught me two really important thing about myself: one I will always fail horribly at some point and two I will always learn from the horrible failures.

Failure is always an option.

Adam Savage's Obsessions

Published by Myles Braithwaite 4 weeks, 1 day ago in Planet. 0 Comments

Tags

A TED talk by Adam Savage (of MythBusters) about obsessions, starting with his own obsession over owing a replica of a Dodo skeleton to modeling a the Maltese Falcon Falcon.

I find I am also like this with software, if I see something computer based that I find interesting I do crazy amounts of research to mimic. Recently made my site XML-RPC completely compatible with a WordPress weblog to use WordPress iPhone application.

Talking about Google App Engine @ PyGTA

Published by Myles Braithwaite 3 months ago in Planet. 0 Comments

Tags , , , and

On 21 April 2009 at 7:30 pm I am going to be giving a talk about Google App Engine at the linuxcaffe.

Google App Engine is a platform to building and hosting web applications on Google's infrastructure (which is sometimes called PaaS1). It has a pay-for-what-you-use payment level but anything below 5 million pageviews a month.

PaaS
Platform as a Service is the delivery of a computing platform and solution stack as a service.