chrismcdermott.blogspot.com
53 Events Blog: April 2007
http://chrismcdermott.blogspot.com/2007_04_01_archive.html
Thursday, 5 April 2007. So thats the end of week 2 in the new job and I'm shattered. I've already learned loads and I've still got a mountain to climb. I've arrived just in time to do my objectives and they are looking pretty full up already. I plan to sit the SCJP (I think I've put it off long enough) learn Ruby strengthen the old SQL skills whilst trying to soak up as much domain knowledge as possible. Subscribe to: Posts (Atom). View my complete profile.
jiggypete.blogspot.com
Jiggy Pete: March 2011
http://jiggypete.blogspot.com/2011_03_01_archive.html
Thursday, 3 March 2011. As most of you will know myself and five friends are raising funds for Maggie's Centres as well as training for their Bike'n'Hike. From the Maggies webite. What is a Maggie's Centre? A Maggie’s Centre is a place to turn to for help with any of the problems, small or large, associated with cancer. So what do I intend to do to help raise funds I hear you ask? What do you get for your donation over and above a warm fuzzy feeling for helping out a much in need charity? In summary, I a...
jiggypete.blogspot.com
Jiggy Pete: October 2010
http://jiggypete.blogspot.com/2010_10_01_archive.html
Monday, 18 October 2010. For the last few weeks I've had a bit of extra time on my hands which I've been trying to put to good use by going out to play on my bike. Fun as it sounds there is a more serious reason for getting out on the bike more, six of us have signed up to participate in Maggies Monster Bike'n'Hike. At the end of April 2011. What does that involved? A 30 mile bike ride plus one of an 8, 22 or 43 mile hike. See why I need to get some training underway? The first section of the red route i...
jiggypete.blogspot.com
Jiggy Pete: Now I know
http://jiggypete.blogspot.com/2014/09/now-i-know.html
Wednesday, 17 September 2014. Hey, it's been a while. How are you doing? Where do I start? Must be important for Peter to bash the keyboard more than 140 times after a few years. As someone who is heavily involved in the dev community with ScotRUG, ScotlandJS and IslayConf I am very aware of the safety concerns women have about attending events. How can we prevent people being left with nightmares for the rest of their days? How does all this start? It only takes a look and/or a noise to unnerve someone.
jiggypete.blogspot.com
Jiggy Pete: Call to arms: Ban Case / Switch statements
http://jiggypete.blogspot.com/2009/12/call-to-arms-ban-case-switch-statements.html
Tuesday, 8 December 2009. Call to arms: Ban Case / Switch statements. Of late I've been keeping up with the Hashrocket bookclub. Which is streamed on Tuesday evenings at 5.12pm GMT. Each week the folks discuss a chapter or two of the current book Refactoring: Ruby Edition. I noticed there was a running theme through a number of the 'Organising Data' refactorings which was removing case statements. Any language designers out there reading? Subscribe to: Post Comments (Atom). View my complete profile.
jiggypete.blogspot.com
Jiggy Pete: September 2007
http://jiggypete.blogspot.com/2007_09_01_archive.html
Wednesday, 5 September 2007. Jiggy jumps into action after NFSJ. Hello and welcome to my first blog post,. During my trip to London for the. No Fluff Just Stuff eXchange. I was introduced to a host of new tech toys to play with. The friendly nature of the presenters and attendees was great and I really want to share some of that experience with the wider world. The overarching message I took from. Whatever your bag is Java, Ruby, Groovy or something more functional like. To create a .groovy file you ...
jiggypete.blogspot.com
Jiggy Pete: Mac Gem Jip
http://jiggypete.blogspot.com/2009/04/mac-gem-jip.html
Wednesday, 15 April 2009. I'm a bit of a newbie to Macs and finally took the plunge a few months back. The day job is still on a windows box to keep inline with the rest of the team so there hasn't been much Mac playtime. The last few days I started to put together a presentation for Agile Scotland with coded examples and that is where I hit the wall - running the code. . Background to the problem:. Which helps explains where I went astray. Subscribe to: Post Comments (Atom). View my complete profile.
jiggypete.blogspot.com
Jiggy Pete: How easy is it to validate the format of an email address
http://jiggypete.blogspot.com/2008/12/other-day-i-had-to-create-admin-console.html
Friday, 5 December 2008. How easy is it to validate the format of an email address. The other day I had to create an admin console for creating a user object which contained the usual fields,. When it came to setting up the active record object to ensure that the username, forename and surname are supplied I started spec'ing the behaviour. All was moving along well. Include only one '@'. There must be a lot more to it than that. Validates presence of :username, :forename, :surname. And there it is! Valid...
jiggypete.blogspot.com
Jiggy Pete: May 2008
http://jiggypete.blogspot.com/2008_05_01_archive.html
Saturday, 17 May 2008. When we started our latest project about 6 months ago I was banging on about using Groovy. Nobody was convinced or should I say interested. On Thursday the Mighty Gus and myself went along to a presentation on Groovy. We came back thoroughly enthused and were desperate to use it day to day. The main aim for Thursday afternoon was to. Get Groovy up and running within our development environment,. Write a test case for new functionality. Getting Groovy up and running locally. When ru...
jiggypete.blogspot.com
Jiggy Pete: October 2007
http://jiggypete.blogspot.com/2007_10_01_archive.html
Monday, 1 October 2007. For around the past 6 months I have been trying to nail down what the difference in attitude is between developers. Paul Duvall has summed up what I have been trying to get across to colleagues in his. About troubleshooters and troublepreventors. I describe myself as a lazy developer to anyone who cares to listen, however this needs some context. Everytime these upfront payments get dodged it comes back to punish the dev team with obscene amounts of non-value add work.