Living with the Consequences
by Malcolm Murray - Durham
Something smells funny in the air – probably because the group we are sharing the convention space with is IPCPA – The International Premium Cigar and Pipe Association. Unfortunately, smoking is allowed inside, though technically it is supposed to only be in the casino areas. However, there is a lot of pipe and cigar smoke floating around. It's hurting my throat a bit even.
I was a bit reluctant to go to a presentation by Malcolm, not because it wouldn't be good, but because I've heard him before in the UK and will probably get many chances to hear him again. However, there wasn't anything else which interested me, so I went to his session for the last of the day.
Basic gist of it: Building blocks are good but can cause real problems and bring down your system. (Like a moth to the pretty flame of building blocks)
What cost?
-can't upgrade quickly – need to fix any bugs and change language packs
-dependency on others to fix some building blocks or upgrade them
-potentially dependent on small number of staff members who may disappear, get his by a car (anyone?)
-half of Malcolm's time spent customising using building blocks and language packs
Changed error messages to cause people to review what they are doing – did it help?
Should talk to Malcolm about language pack editing and updating each release – has some method, maybe worth discussing?
It's possible to have multiple language support in your building blocks too
Can't customise icons for building block items, though you can for regular Bb items
Either:
Introduce a new feature
Extend an existing feature
Completely replace an existing feature
-how to switch it off, what dependencies are there, any new documentation needed?
Example, he has created a new portal task module
No JavaDocs, so he used the class file to auto-load what functions there are he can call
Then looked at database to try to understand what was where
New version of tasks,
-color coded by date priority
-students can show their progress on tasks, choose when they want to get the color coded warning (14 days before due date, etc.)
-hide things when they are done – as people mostly worried about stuff left to do
-can export tasks to exchange, Blackboard calendar
-group tasks are now possible, that can show people what is done
Bit like workflows?
Wants to have an option to tell people who have not finished a group task yet
Changing documentation is a big issue, as it is impossible in many cases.
Are there any tools you don't use – then you can't change the docs
by Malcolm Murray - Durham
Something smells funny in the air – probably because the group we are sharing the convention space with is IPCPA – The International Premium Cigar and Pipe Association. Unfortunately, smoking is allowed inside, though technically it is supposed to only be in the casino areas. However, there is a lot of pipe and cigar smoke floating around. It's hurting my throat a bit even.
I was a bit reluctant to go to a presentation by Malcolm, not because it wouldn't be good, but because I've heard him before in the UK and will probably get many chances to hear him again. However, there wasn't anything else which interested me, so I went to his session for the last of the day.
Basic gist of it: Building blocks are good but can cause real problems and bring down your system. (Like a moth to the pretty flame of building blocks)
What cost?
-can't upgrade quickly – need to fix any bugs and change language packs
-dependency on others to fix some building blocks or upgrade them
-potentially dependent on small number of staff members who may disappear, get his by a car (anyone?)
-half of Malcolm's time spent customising using building blocks and language packs
Changed error messages to cause people to review what they are doing – did it help?
Should talk to Malcolm about language pack editing and updating each release – has some method, maybe worth discussing?
It's possible to have multiple language support in your building blocks too
Can't customise icons for building block items, though you can for regular Bb items
Either:
Introduce a new feature
Extend an existing feature
Completely replace an existing feature
-how to switch it off, what dependencies are there, any new documentation needed?
Example, he has created a new portal task module
No JavaDocs, so he used the class file to auto-load what functions there are he can call
Then looked at database to try to understand what was where
New version of tasks,
-color coded by date priority
-students can show their progress on tasks, choose when they want to get the color coded warning (14 days before due date, etc.)
-hide things when they are done – as people mostly worried about stuff left to do
-can export tasks to exchange, Blackboard calendar
-group tasks are now possible, that can show people what is done
Bit like workflows?
Wants to have an option to tell people who have not finished a group task yet
Changing documentation is a big issue, as it is impossible in many cases.
Are there any tools you don't use – then you can't change the docs
In general the session was not about the tasks building block he wrote, though it was a good example of the difficulties with making your own replacement tools. I think the general message was be careful what you do customise as it may require lots of updating in the future (ditto for language packs).
No comments:
Post a Comment