Turns out there are lots of complicated ways, but in Ubuntu you can just reconfigure the package:
dpkg-reconfigure mysql-server-5.0
Hopefully that will save someone some hair pulling
HOWTO Reset MySQL 5.0 root password in Ubuntu 8.04 LTS
September 19, 2009 By Leave a Comment
Utils anti-pattern & AutoMapper
June 2, 2009 By Leave a Comment
These are more for my reference purposes – hopefully you’ll find them useful:
If you’re about to name a class **Util; think harder – there is a better name that discribes what that class is for:
Chriss Missal has some advice for you
Faced with the prospect of heaps of left hand side => right hand side code in your DTO of anti-corruption layer? Consider Jimmy Bogard’s Automapper
The Pomodoro Technique – Scrum in the small
May 31, 2009 By 5 Comments
Over the past month I’ve been experimenting with the pomodoro technique of time management to great success.
The technique is surprisingly simple; yet I’ve found it contains a wealth of physical and emotional benefits. To give some context; I’m using it as a programmer as part of a agile scrum team. I typically program using TDD techniques. That being said, I don’t see why it wouldn’t be applicable in most “desk” based jobs.
A pomodoro is a unit of focused, uninterrupted time; measured by an egg timer. For me, 25 minutes works well.
At the beginning of my work day, I write a collection of tasks that I think I achieve during the day onto a fresh piece of paper. (my todo list). I estimate how long I think each task will take in units of a pomodoros. Next to each task I put a number of boxes; one for each pomodoro unit. I make sure not to have more pomodoro units than I achieved yesterday; and I try to make sure that I’m estimating tasks based on how long similar tasks actually took me in the past.
Then I wind up my egg timer, place it visibly on my desk and begin the first task. The ritual of winding up the timer, placing it down and hearing it tick helps me to drop into the zone of full concentration – and let my team know that they shouldn’t interrupt me.
Brrrriiinng. Pomodoro up, finish the current test and stop. Cross out one of the boxes on my todo list. Get up and leave my desk; stretch, drink some water, focus on something far away to relax the eyes, go and speak to anyone who came past during my pomodoro time & was waived away.
Then back to the desk, reassess which is now the most important task to get one with, and start the next pomodoro.
At the end of the day I transcribe the results of my todo list back to a records sheet; update our project management software (VersionOne); and leave, satisfied that I achieved what I set out to do.
I’ve found that running my day like this greatly increases my job satisfaction & efficiency.
Firstly; I’m breaking my addition to hopium, and setting myself up to fail every day. I used to live in this lala land called – I have 8 hours of productive work time each day. The empirical reality shows that I usually do 5 – 8 pomodoro units / day – so much more like 3 – 4 hours. The rest gets gobbled up by meetings, emails, conversations. So its no wonder that I used to achieved half what I thought I would each day; and left work feeling disappointed.
Secondly, having a forced reset every 25 mins really helps me to stop falling down rabbit holes. I’ll often be trying to solve a problem with a specific technique that just isn’t working, and if I’m not careful I can spend a whole afternoon bashing my head against a wall. With the forced breaks, I’ll often find that when I sit back down to the problem, I’ll have a flash of inspiration for a much simpler way to solve it, or realise that I don’t even need to solve it in the first place!
Thirdly, being reminded to get away from my desk frequently really helps physically. I’ve experienced much less “mouse shoulder” and dry eyes.
The technique is also really helpful when pairing; keeping meetings from rambling; keeping focussed on one task (rather than having to check email or twitter every 10 seconds) and getting going on a large daunting task.
If you struggle with hopium like me; I’d really encourage you to give the Pomodori technique a try for 2 weeks, and let me know how you get on in the comments to this post.
Brrriiinng 
Resources
www.pomodorotechnique.com
- Pomodoro – Records sheet
- Pomodoro – Todo inventory sheet
- Pomodoro – Todo today sheet
Howto uninstall a broken MSI
May 27, 2009 By Leave a Comment
I’m busy creating an MSI installer package at work; and managed to get my system into a bit of a knot.
Basically, my custom action crashes on uninstall – so when I try to remove the broken MSI, it throws an error and rolls back the uninstall process.
AAARGH! How do I remove the broken MSI now that I’ve fixed the bug?
Fortunately MSKB supplies this helpful little tool:
Windows Installer CleanUp Utility
Simply run, select offending MSI, and it will forceably remove any MSI registration from your system.
Got me out of a pickle; and will hopefully do the same for you.
Symbolic links for WinXP
March 11, 2009 By Leave a Comment
Hurrah – symbolic links have arrived for WinXP; via Junction.
C:>junction.exe c:Test c:WINDOWS
Thanks for this great tip Nick
Try/Catch for SQL!?
March 5, 2009 By Leave a Comment
Thanks to Nick Sertis for this trick – who knew TSQL could do try/catch statements!
Very useful when you need to write data manipulation scripts for production databases.
BEGIN TRY
BEGIN TRAN
--Some SQL
COMMIT TRAN
END TRY
-- Catch the errors on the inserts
BEGIN CATCH
ROLLBACK TRAN
SELECT ERROR_MESSAGE()
END CATCH
For a software craftsman, reducing technical debt should be as much of a habit as typing
March 2, 2009 By Leave a Comment
I was involved in an interesting group discussion with fellow craftsmen yesterday on Technical Debt at the 2009 Software Craftsmanship conference.
The question put to the group was: “How should a team make time to reduce technical debt?”
I was interested that there was a totally unanamious response – “You shouldn’t”. “You should be doing tiny pieces of technical debt reduction all the time”.
Previously I have advocated creating technical debt reduction stories, and trying to schedule those into the iteration plan. People thought this was in principal the wrong strategy; and indeed in my experience this approach doesn’t work.
The group felt that in general tackling technical debt reduction though large scale refactorings was the wrong approach – rather a craftsman should be making incremental improvements every time they touch the code.
Bob Martin’s Boy Scout Rule: – check in your code a little cleaner than what you checked out – encapsulates this principal. Its the little refactorings that you make – removing a tiny piece of duplication, changing a variable name to better reveal intent; extracting an expression into a intention revealing method – that, over time, result in a clean, maintainable code base.
In a way, this is similar to implementing the “Fixing Broken Windows Theory” in software development. The theory is that having a zero tolerance attitude towards the little things makes a huge impact on the so called “bigger” things.
Its perhaps easier understood if you consider what happens if you don’t care about the little things. Its about the attitude – if I couldn’t care enough to clean up a messy bit of code; will my team mates care about a few broken tests? If its okay to have a few broken tests; then it’s probably okay to ignore some bugs. If its okay to ignore bugs; then who really needs to care about well defined acceptance tests? And if the team doesn’t care about precise acceptance tests; why should the business care about unambiguous requirements. You get the picture.
Its the little things, added up, that result in technical debt reduction.
Functions with side effects are just rude!
February 25, 2009 By Leave a Comment
Today I fell into a trap when using a function that had a side effect – it unexpectedly changed an input parameter; causing a later statement to fail. Debugging took an age!
For example, consider the following function:
string StringReplace(string haystack, string needle)
If this function is side-effect free, we can use it without fear like this:
string menagerie = "cat,dog,bee,llama";
string catFreeMenagerie = StringReplace(menagerie, "cat");
string beeFreeMengerie = StringReplace(menagerie, "eric");
Assert.AreEqual(",dog,fish,llama", catFreeMenagerie);
Assert.AreEqual("cat,dog,,llama", beeFreeMengerie);
However, if StringReplace() had the side effect of also changing the passed in haystack, then the second Assert would fail, because the first StringReplace has the unexpected side effect of changing one of its arguments.
Evans in the DDD book has quite a bit to say about this; arguing that having side effect free functions goes a long way towards making a supple design
Side effect free functions also make testing & refactoring easier (less state to worry about etc)
Remember, a function that changes its parameters is rude, and should not be trusted!