<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10titles.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemtitles.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" gd:etag="W/&quot;Ck4DSX85eSp7ImA9WxNXFEk.&quot;"><id>tag:blogger.com,1999:blog-30950679</id><updated>2009-10-01T16:49:38.121-07:00</updated><title>Regular Expressions</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>33</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/idcmp" type="application/atom+xml" /><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://feeds.feedburner.com/idcmp" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.addtoany.com/?linkname=Regular%20Expressions&amp;linkurl=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp&amp;type=feed" src="http://www.addtoany.com/addfr-b.gif">Add to Any Feed Reader</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.fwicki.com/users/default.aspx?addfeed=http%3A%2F%2Ffeeds.feedburner.com%2Fidcmp" src="http://www.fwicki.com/images/ui/fwicki_clicklet.png">Subscribe with fwicki</feedburner:feedFlare><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;DUQCRH4_eCp7ImA9WxVbF04.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-4187149614066667587</id><published>2009-04-02T22:35:00.002-07:00</published><updated>2009-04-02T22:42:45.040-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-02T22:42:45.040-07:00</app:edited><title>Xen vs KVM</title><summary>I wanted to chime in on the Xen vs. KVM discussions, and give you some food for thought.I've been using Xen now for years, having replaced UserModeLinux on my personal server, and it's seen a lot of production use at my current job.  That said, KVM is ultimately the right way to go. Constant maintenance of Xen's hypervisor kernel is what causes Linux distributions grief with Xen.  Those that keep</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/4187149614066667587/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=4187149614066667587" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4187149614066667587?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4187149614066667587?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2009/04/xen-vs-kvm.html" title="Xen vs KVM" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total></entry><entry gd:etag="W/&quot;CkIFR3s6fip7ImA9WxVSEU8.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-4456828730153334798</id><published>2009-01-04T16:46:00.007-08:00</published><updated>2009-01-04T17:55:16.516-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-01-04T17:55:16.516-08:00</app:edited><title>Provisioning Servers: An Afternoon with Cobbler</title><summary>I spent some time evaluating Fedora's Cobbler installation service. If you play with many machines - real or virtual - you should definitely take a look. Some handy features:* Kickstart Setup: For Red Hat breed systems, existing Kickstart configurations (found on installation media) are exposed as profiles in Cobbler.  You can add your own Kickstart configurations too (imagine a "rhel5-webserver"</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/4456828730153334798/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=4456828730153334798" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4456828730153334798?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4456828730153334798?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2009/01/provisioning-servers-afternoon-with.html" title="Provisioning Servers: An Afternoon with Cobbler" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;C0cMR3s9eCp7ImA9WxVTFUQ.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-4439859257237931845</id><published>2008-12-29T09:03:00.002-08:00</published><updated>2008-12-29T14:51:26.560-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-29T14:51:26.560-08:00</app:edited><title>Ye Olde Job: Technology That Wasn't</title><summary>Our system could accept transactions over the phone (via a clerk) or through our website.  The clerk on the phone used a semi-web based application to interact with the system.The headache with this was that the code base for the "semi-web" and "actual web" only became a common code path much, much deeper in the code. So the plan was simple, redo the website code such that it could eventually be </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/4439859257237931845/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=4439859257237931845" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4439859257237931845?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4439859257237931845?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/12/ye-olde-job-technology-that-wasnt.html" title="Ye Olde Job: Technology That Wasn't" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;C0EEQn0_fCp7ImA9WxVTFUQ.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-2533826725614276009</id><published>2008-12-26T09:58:00.009-08:00</published><updated>2008-12-29T15:00:03.344-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-29T15:00:03.344-08:00</app:edited><title>Ye Olde Job: First Post - So You're the Boss</title><summary>It's been seven months since I left my old job, and I feel it's alright to talk about some things.If you're in a situation where you're finding yourself leading a team of developers without any mentoring from anyone on how the heck to do that, I offer you some food for thought.As a developer, you measure your own progress by the code you write, the bugs you fix, stored procedures you debug, </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/2533826725614276009/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=2533826725614276009" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/2533826725614276009?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/2533826725614276009?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/12/ye-olde-job-first-post-so-youre-boss.html" title="Ye Olde Job: First Post - So You're the Boss" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total></entry><entry gd:etag="W/&quot;CUYNQ3Y_cSp7ImA9WxRVEko.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-7841236467567219617</id><published>2008-11-09T10:36:00.001-08:00</published><updated>2008-11-09T15:26:32.849-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-09T15:26:32.849-08:00</app:edited><title>Seven Reasons I Didn't Pick Your Open Source Project</title><summary>After a really relaxing summer, I've picked up a job as a Systems Architect at local company suffering from growing pains. After almost a decade, I've put down my debugger and picked up a budget..for now. I've found myself looking at many different options of products some open source some not. I want to apologize to those open source projects I've rejected and wanted to let you know why:1. </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/7841236467567219617/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=7841236467567219617" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/7841236467567219617?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/7841236467567219617?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/11/seven-reasons-i-didnt-pick-your-open.html" title="Seven Reasons I Didn't Pick Your Open Source Project" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DkcBQ3k7fip7ImA9WxRQF0g.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-2377623438054508630</id><published>2008-10-11T12:35:00.002-07:00</published><updated>2008-10-11T12:40:52.706-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-11T12:40:52.706-07:00</app:edited><title>Wave Tracing: Ray Tracing for Sound</title><summary>Here's the pitch: With regular ray tracing, rays of light are traced backward from a pixel of the camera, to an object and eventually to a light source (or lack thereof).  If you can do that with light, why can't it be done with sound?Over ten years ago I was having breakfast with a friend and I sketched out the idea on a napkin. This kind of math is definitely not my strong point. But instead of</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/2377623438054508630/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=2377623438054508630" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/2377623438054508630?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/2377623438054508630?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/10/wave-tracing-ray-tracing-for-sound.html" title="Wave Tracing: Ray Tracing for Sound" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;CUUNRHk5eCp7ImA9WxRRFEs.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-2704391621386087854</id><published>2008-09-26T14:08:00.000-07:00</published><updated>2008-09-26T14:08:15.720-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-26T14:08:15.720-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="gwt" /><title>GWT: Generators HowTo (BuildStamp)</title><summary>If you're curious what generators are, or have never used them with GWT, this simple generator will give you a quick introduction to get your hamster wheels turning.I do a lot of prototyping in GWT before I build the backend and I've recently had the need to generate a "build version" for my GWT interface.  While there are about fiftybazillionmillion different ways to do this, I've chosen a GWT </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/2704391621386087854/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=2704391621386087854" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/2704391621386087854?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/2704391621386087854?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/09/gwt-generators-howto-buildstamp.html" title="GWT: Generators HowTo (BuildStamp)" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DkMFSHk8eip7ImA9WxRSFEs.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-4251323027291805850</id><published>2008-09-15T00:16:00.003-07:00</published><updated>2008-09-15T00:40:19.772-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-15T00:40:19.772-07:00</app:edited><title>Spore on Linux</title><summary>If you're a Linux user wondering if Spore works, the answer is: Sorta.I bought the download version from the EA Store.  Nothing mentioned until after my purchase was complete that I needed a Windows-only downloader.  I didn't test this under Wine.Aside: The EA Store website allows + in email addresses, but the Spore online login does not.I'm using Ubuntu 8.04 with a custom build of Wine 1.1.4 (</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/4251323027291805850/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=4251323027291805850" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4251323027291805850?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4251323027291805850?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/09/spore-on-linux.html" title="Spore on Linux" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CEMFQnk-eSp7ImA9WxRTFEo.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-403798459687629689</id><published>2008-09-03T12:28:00.005-07:00</published><updated>2008-09-03T13:06:53.751-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-03T13:06:53.751-07:00</app:edited><title>Chromium and Bees</title><summary>Watching what Google does feels like watching X-Files. I want to believe there's some grand master plan, but I'm pretty sure they're just making things up as they go.Hank Williams over at Why Does Everything Suck pretty much covers my thoughts on Google's new web browser in his Huh? and Huh! posts.</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/403798459687629689/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=403798459687629689" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/403798459687629689?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/403798459687629689?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/09/chromium-and-bees.html" title="Chromium and Bees" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;A08CQXw4fip7ImA9WxdVEUk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-5672734053272664779</id><published>2008-07-15T11:10:00.003-07:00</published><updated>2008-07-15T12:24:20.236-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-07-15T12:24:20.236-07:00</app:edited><title>Nine Handy Tips for Taking the Summer Off</title><summary>Six weeks ago I quit my job; six weeks later I've never been happier. I had grown jaded about technology and worn down about my work.  This post isn't about how to quit your job, how to budget for the summer or how to get your next job; it's what I've learned in the  brief oasis between those points in my life.The Beginning1. Do Not Look For Your Next Job: You know internally if you're at the </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/5672734053272664779/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=5672734053272664779" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5672734053272664779?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5672734053272664779?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/07/nine-handy-tips-for-taking-summer-off.html" title="Nine Handy Tips for Taking the Summer Off" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total></entry><entry gd:etag="W/&quot;C0AGRHs6cSp7ImA9WxdQFko.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-514900216617857856</id><published>2008-06-16T20:02:00.000-07:00</published><updated>2008-06-16T20:02:05.519-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-06-16T20:02:05.519-07:00</app:edited><title>Google's Conference on Scalability</title><summary>This is the second year I've attended Google's conference on scalability, the talks were more academic this time around. One organizer indicated that this was indeed the goal of this year's conference.  I enjoyed last year how much of the information was really hands on, but there's some value in seeing what's coming down the research pipe.The conference is an example of what googlers do with </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/514900216617857856/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=514900216617857856" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/514900216617857856?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/514900216617857856?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/06/googles-conference-on-scalability.html" title="Google's Conference on Scalability" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DkYBRXc5eSp7ImA9WxdTEEk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-7197974776417864950</id><published>2008-05-03T14:02:00.005-07:00</published><updated>2008-05-05T20:22:34.921-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-05-05T20:22:34.921-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="spring" /><title>Four Days of Spring: Spring Core Training</title><summary>The other week I was fortunate enough to grab an extra freebie spot on Spring Source's "Spring Core" course.  It's a marathon. Four days jam-packed with just about everything you could imagine Spring-related. I thought I'd post a bit about my impressions...First the good side; the course material is exhaustive and the instructor knew his stuff cold.  While I was the only one in the course with no</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/7197974776417864950/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=7197974776417864950" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/7197974776417864950?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/7197974776417864950?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/05/four-days-of-spring-spring-core.html" title="Four Days of Spring: Spring Core Training" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DEIBR3w4eCp7ImA9WxZbFEs.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-6426463016011726043</id><published>2008-04-03T18:35:00.008-07:00</published><updated>2008-04-17T14:09:16.230-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-04-17T14:09:16.230-07:00</app:edited><title>Six PDFs You May Find Interesting</title><summary>1. Failure Trends in a Large Disk Drive Population [ PDF ] A popular Google paper from 14 months ago, but a good read if it's something you may have to deal with.  Fairly readable language too.  Summary: Really burn your drives in for the first few months.  Few metrics are good indicators of failure.2. Pinpoint: Problem Determination in Large, Dynamic Internet Services [ PDF ] Tracing requests </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/6426463016011726043/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=6426463016011726043" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/6426463016011726043?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/6426463016011726043?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/04/six-pdfs-you-may-find-interesting.html" title="Six PDFs You May Find Interesting" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DU8DRXo-eCp7ImA9WxZWFk8.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-3929228047994656940</id><published>2008-03-15T17:22:00.004-07:00</published><updated>2008-03-15T17:37:54.450-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-15T17:37:54.450-07:00</app:edited><title>Logging Performance Exceptions (Part 1)</title><summary>You've probably wished you could find out why a certain block of code was occasionally slow in production.  Wouldn't it be nice to turn on extra logging only when things were acting up? You can!With a bit of logging in your code, you can get an output like this: [135ms] request share purchase   [5ms] validate purchase request   [40ms] check account balances    [39ms] synchronous balance request</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/3929228047994656940/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=3929228047994656940" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/3929228047994656940?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/3929228047994656940?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/03/logging-performance-exceptions-part-1.html" title="Logging Performance Exceptions (Part 1)" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">5</thr:total></entry><entry gd:etag="W/&quot;DkEMQHk_fip7ImA9WxZXF0U.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-3094723278343126148</id><published>2008-03-05T19:29:00.003-08:00</published><updated>2008-03-05T22:24:41.746-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-05T22:24:41.746-08:00</app:edited><title>Java Developer Performance Reviews</title><summary>Despite years of promises to the contrary, I've found myself in the unfortunate situation of having to write performance reviews for my developers.  For those other poor souls in this situation, I've collected my thoughts and present them here. This post is split into two parts.  The first part I vent a bit, the second part has the useful content.Before You Get HereWarning: If you find yourself </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/3094723278343126148/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=3094723278343126148" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/3094723278343126148?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/3094723278343126148?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/03/java-developer-performance-reviews.html" title="Java Developer Performance Reviews" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CE4GR384eyp7ImA9WxZQEk0.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-5373069929548173506</id><published>2008-02-16T13:59:00.004-08:00</published><updated>2008-02-16T15:02:06.133-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-02-16T15:02:06.133-08:00</app:edited><title>Testing Network Effects on Your Code</title><summary>Testing is a big deal.  Very often though, we spend days writing unit tests only to forget that our code must play well with others.  In the real world, how responsive will a new AJAX interface or RMI Swing application be?In our load testing environment, we've introduced a network nightmare bridge.  This handy little box sits between us and our server (or between any two networked devices).  We </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/5373069929548173506/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=5373069929548173506" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5373069929548173506?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5373069929548173506?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2008/02/testing-network-effects-on-your-code.html" title="Testing Network Effects on Your Code" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;Ck8GRXs4fyp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-5061698859565597043</id><published>2007-12-08T21:11:00.000-08:00</published><updated>2007-12-09T14:53:44.537-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:53:44.537-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="sql" /><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><category scheme="http://www.blogger.com/atom/ns#" term="oql" /><title>Using SQL on Java Collections</title><summary>On the project I work on, we have an in memory model of some particularly useful data (a POJO model as it were).  A situation that regularly occurs with this useful data is that various groups want the data sliced and diced in various manners.Each time a request comes in we have to write a new method that iterates through our collection, sometimes making a new comparator and then return a subset </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/5061698859565597043/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=5061698859565597043" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5061698859565597043?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5061698859565597043?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/12/using-sql-on-java-collections.html" title="Using SQL on Java Collections" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">6</thr:total></entry><entry gd:etag="W/&quot;Ck8CRnk9cCp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-5043612656599756477</id><published>2007-11-21T20:45:00.001-08:00</published><updated>2007-12-09T14:54:27.768-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:54:27.768-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="passwords" /><category scheme="http://www.blogger.com/atom/ns#" term="security" /><category scheme="http://www.blogger.com/atom/ns#" term="rants" /><title>Security Anti-Pattern #1: The Very Secure Password</title><summary>Our security department decided to change passwords of some "common accounts" (anti-pattern #2) we have at work on our load testing network.  They started this process without letting anyone know and set the new password to "G2xi]$7jB;".   This leads to security anti-pattern #1: The Very Secure Password.A good password has to meet four criteria:     1) It must be easy for you to remember.     2) </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/5043612656599756477/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=5043612656599756477" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5043612656599756477?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5043612656599756477?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/11/security-anti-pattern-1-very-secure.html" title="Security Anti-Pattern #1: The Very Secure Password" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;Ck4FQnw5eCp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-5186655457538314818</id><published>2007-11-18T19:02:00.000-08:00</published><updated>2007-12-09T14:55:13.220-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:55:13.220-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="bamboo" /><category scheme="http://www.blogger.com/atom/ns#" term="ideas" /><category scheme="http://www.blogger.com/atom/ns#" term="continuous integration" /><title>Breaking Continuous Integration Servers (Part 2)</title><summary>I wrote a few posts ago about how easily continuous integration servers break.  This post got quite a bit of response!Jon from Atlassian felt bad for the ordeal and sent over a couple of "I'M WELL BUILT" t-shirts.  Thanks Jon!  Owen over at Unreasonable Entertainment ran an initial version of the "hell build" maven plugin idea from my post against Hudson with less than stellar results.  Damn!Owen</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/5186655457538314818/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=5186655457538314818" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5186655457538314818?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5186655457538314818?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/11/breaking-continuous-integration-servers.html" title="Breaking Continuous Integration Servers (Part 2)" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;Ck4HQns_eSp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-1983778304762766448</id><published>2007-10-29T23:47:00.000-07:00</published><updated>2007-12-09T14:55:33.541-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:55:33.541-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="rants" /><title>Cutting Through "Technological Mythology"</title><summary>"Java is slow."  "Windows always crashes."  "We have to do it this way; it's the way we've always done it!"As we grow at work, I find the rules of thumb that I usually follow and ask others to do the same have become carved in stone.  Those who don't fully understand "why" they're doing it have taken it as immutable doctrine.  When I ask for minor deviations in these rules of thumb, I'm met with </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/1983778304762766448/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=1983778304762766448" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/1983778304762766448?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/1983778304762766448?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/10/cutting-through-technological-mythology.html" title="Cutting Through &quot;Technological Mythology&quot;" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;Ck4BR3w_eCp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-4013787420814662557</id><published>2007-10-17T23:07:00.000-07:00</published><updated>2007-12-09T14:55:56.240-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:55:56.240-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interviews" /><category scheme="http://www.blogger.com/atom/ns#" term="resumes" /><category scheme="http://www.blogger.com/atom/ns#" term="tips" /><title>Tips on Getting Your Development Co-Op Job</title><summary>As a co-op student, you likely get a lot of advice from academics on things - that in 10 years - you will do intuitively as tying your shoe and checking for unprotected wifi networks.  Here are some tips from The Real World that you should double-check before applying to your co-op position.Nobody is expecting you to be a master of the things you list.  They'll expect you to be proficient in them</summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/4013787420814662557/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=4013787420814662557" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4013787420814662557?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4013787420814662557?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/10/tips-on-getting-your-development-co-op.html" title="Tips on Getting Your Development Co-Op Job" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;Ck4NQnY9cSp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-5438246852022476935</id><published>2007-10-11T18:41:00.000-07:00</published><updated>2007-12-09T14:56:33.869-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:56:33.869-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="bamboo" /><category scheme="http://www.blogger.com/atom/ns#" term="ideas" /><category scheme="http://www.blogger.com/atom/ns#" term="continuous integration" /><title>Dog Food Not Enough for CI Servers</title><summary>Our Continuum CI server constantly had problems hanging during builds, so we switched to Bamboo, which while not perfect, is better.This week our Bamboo server ate its own config file when it ran out of disk space and this got me thinking that most CI servers I've seen these days do a horrible job at handling the plethora of near-failure conditions that plague a build.What's really needed is a </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/5438246852022476935/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=5438246852022476935" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5438246852022476935?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/5438246852022476935?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/10/dog-food-not-enough-for-ci-servers.html" title="Dog Food Not Enough for CI Servers" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total></entry><entry gd:etag="W/&quot;C0cESHo7fSp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-3999640358098305625</id><published>2007-09-04T22:08:00.000-07:00</published><updated>2007-12-09T14:56:49.405-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:56:49.405-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="cvs" /><category scheme="http://www.blogger.com/atom/ns#" term="svn" /><category scheme="http://www.blogger.com/atom/ns#" term="source control" /><title>SVN: Insufficent Kool-Aid?</title><summary>We've switched from CVS to SVN at work, and I was surprised to find out that Subversion doesn't actually have a command line tool worth salt.  Sure, there's svn, but it's not designed with a developer in mind at all.  The more I use Subversion, the more I feel like it was actually designed for something else, and I just happen to be using it for source code.As one developer on my team describes </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/3999640358098305625/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=3999640358098305625" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/3999640358098305625?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/3999640358098305625?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/09/svn-insufficent-kool-aid.html" title="SVN: Insufficent Kool-Aid?" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;C0cNRXk6fCp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-1872851074594410223</id><published>2007-06-02T19:46:00.000-07:00</published><updated>2007-12-09T14:58:14.714-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:58:14.714-08:00</app:edited><title>Our Software Marketplace (and it's not what you think)</title><summary>Every other Monday morning, members from different departments, groups or teams come to our marketplace and talk to us about whatever work they need done.Sometimes the DBA group want us to try a new JDBC driver, sometimes Security wants us to add more auditing to our code, sometimes our business group want business features added .. you get the idea.Our own internal work is expressed during the </summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/1872851074594410223?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/1872851074594410223?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/06/our-software-marketplace-and-its-not.html" title="Our Software Marketplace (and it's not what you think)" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author></entry><entry gd:etag="W/&quot;C0cHRHw7cSp7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-30950679.post-4244868892952353872</id><published>2007-05-11T19:54:00.000-07:00</published><updated>2007-12-09T14:57:15.209-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T14:57:15.209-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="interviews" /><category scheme="http://www.blogger.com/atom/ns#" term="resumes" /><title>Shortages of Decent Java Developers (part III)</title><summary>I've been interviewing Java developers now for two years.  My interviewing skills are strong enough now that I can pinpoint where in the grey "maybe" area a candidate lies.   Here's a few tips on helping you move from maybe-grey to "yes".1. Your Head Hunter ResumeAdmit it.  You polish your resume up for head hunters, adjusting the content so they can find you jobs without having the technical </summary><link rel="replies" type="application/atom+xml" href="http://idcmp.linuxstuff.org/feeds/4244868892952353872/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=30950679&amp;postID=4244868892952353872" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4244868892952353872?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/30950679/posts/default/4244868892952353872?v=2" /><link rel="alternate" type="text/html" href="http://idcmp.linuxstuff.org/2007/05/shortages-of-decent-java-developers.html" title="Shortages of Decent Java Developers (part III)" /><author><name>Idcmp</name><uri>http://www.blogger.com/profile/10737882461734024589</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="17601816689650581356" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry></feed>
