Skip to content

Instantly share code, notes, and snippets.

@brendo
Created February 1, 2011 12:45
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save brendo/805802 to your computer and use it in GitHub Desktop.
Save brendo/805802 to your computer and use it in GitHub Desktop.
A never ending list of things I can do on my Personal Development time.

UC - Use Cases. CW - Collaborate with.

Watch & Learn

  • Watch the Think Vitamin videos
  • Watch Paul Irish's "Things I've learnt from the jQuery source code"
  • Learn to use SimpleTest, or any other Unit Testing library, that may help speed up Symphony development (CW: Rowan would probably have some ideas, or may have some experience in this already)
  • Read about UX in general
  • Read some Graffle tutorials to get more productive
  • Read any tutorials about Photoshop, and cutting up designs to see if I can do this quicker (CW: Mark might have some Photoshop tips that'd be handy)
  • Setup Webgrind & MySQL on my laptop so I can do more development work at home (CW: Rowan will definitely need to give me a hand here)

Symphony

  • Symphony Core duties
  • Upgrade The SoundLounge to Symphony 2.2 (or 2.1.2). A nice experiment in migrating data from the Bilink field to Reference Link fields.
  • Analyse where the times goes in our Symphony quotes so that we can better estimate. If there are extensions, or functionality that we commonly require, look at making Extensions/Utilities that we can use. Possibly Wufoo form for all Digital to fill out?
  • Work out a generic Sitemap XSLT utility we can use

Extensions

  • Package and release our Create + Send extension for the Symphony community (based on Rowan's, but I've since updated it for the new API)
  • Look at a Campaign Monitor field, that will allow an Entry to pull in Subscribers information from Create and Send
  • Improve the Reference Link extension so that the dropdown values are actually jQuery autocomplete (UC: Improve usabilty and page responsiveness in the backend for any site that uses Reference Link with the 'autocomplete' setting.
  • Look at ways to extend Nick Dunn's Entity Diagram extension to support Graffle a bit better (UC: Would be very helpful for Technical Documentation for sites)
  • Work on a Shop extension, so we don't have to spend hours investigating other solutions

Javascript

  • Look at a generic way to implement AJAX history in our sites (UC: AskHuey Radar changing, Battlefront 2 pagination)
  • Look at a generic way to implement Lightbox forms in our sites (UC: pretty much every brochure site ever)

Documentation

  • Finish my Symphony Field tutorial article for Symphony site (UC: May be helpful for our dev's too?)
  • Write an article about jQuery, context and selector engines (UC: All our junior dev's would benefit)
  • Write an article about Javascript scope (or find a list of good ones)
  • Write an article about how to approach a project with XSLT, talking about modular code etc.
  • Write a R&B code style document that will save my sanity. This will save a shitload of time when swapping between projects (CW: Rowan has some ideas to make a Wiki like interface to display this)
  • Write an XSLT primer, or get a copy of Craig's XSLT chapter to hand around, this will save an amount of head slapping and redundant code

R&B

  • Look at building a Builder page, that will streamline the creation of a new client site (checks out Symphony, common extensions, sets up Database, Codebase repo)
  • Look at making a build script that will concat all stylesheet, javascript files and minify them for production (UC: Make all our sites fly!)
  • Create an R&B repository of common scripts and utilities that we use, this will save time when swapping between projects if we always use the same plugins. Should look at donating to these projects.
  • Ask Phill, Nick or Chay what some things that still catch them up are, so we can make them better dev's and increase productivity
  • Talk with Mark about some design techniques he'd like to use, but currently doesn't because of technical limitations (CW: Mark)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment