Skip to main content

Some books for agile programmers

I'm giving docs.google.com another try. I tried it over two years ago (wow, time flies) when Google Docs was still Writely. Oh, my prediction did come through (they got bought by Google), wuhu! So if this post gets doubly published it's because it got screwed up.

Update: docs.google.com didn't manage to publish the title properly. I also have to apply some tags manually. All the pictures and headings came through allright, though.

New books

I just got these books:

They're all from The Pragmatic Bookshelf, although I got them from Amazon (who sent them from New-Zealand, which gave me sort of a bad eco-concience for a while..) cause they were alot cheaper there.
The first title, The Pragmatic Programmer. Well, I'm sort of ashamed that I haven't read it before, being as famous as it is. However, I'm looking through the TOC, and I sort of get the feeling I've touched most of the points, either by hard realization and experience, or by advice from friends and colleagues. The book still provides me with a sturdy, well sorted and well formulated set of practices, which will help me communicate the QWAN to my consulted clients.
Practices of an Agile Developer looks like a follow-up to TPP. It's published in 2007, 7 years after. It seems to have more of a focus on collaboration and project management than on effective tool use (although the subjects do overlap). 
The last book is written by two guys working for SAS, neither are part of the original PP pair. I got it because it's been a long while since I read any modern works on agile development, and agile stuff is quickly turning into my pressure point for some reasons yet to be announced publically :)  The book also has a very nice looking section on Common problems and how to fix them. My team at work just shrunk down to 1,5 people, and we recently suffered almost a two month long sprint stumble (long story, and I'm still having trouble figuring out how I could've gotten it right). Hopefully the book has some advice I can apply to my own project.
All three books make up for three areas I care, and I think every IT-professional should care deeply about: Tools, languages and practices
just asked on twitter which book I should read first. I think I'll do Ship it! first, but might follow the advice of Olve and do TPP first. To be honest, after I finished studying I've been horrible at reading books. I have several books now that I started but never finished. 
Oh, here's a wordle of my blog:
Very flash. I can't for the life of me remember who's blog I just read who pointed me at it. Sorry. There are a bit too many normal English words in the cloud, but some of the words are nice: pretty, people, good, stuff :)
Ok, let's push this thing to Blogger and see how it goes..

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --