<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>Conferences @ clintshank.javadevelopersjournal.com</title><link>http://clintshank.javadevelopersjournal.com/</link><description>(Conferences) My thoughts on software development.</description><copyright>Copyright 2009 clintshank.javadevelopersjournal.com</copyright><generator></generator><lastBuildDate>Fri, 02 Jan 2009 17:28:00 GMT</lastBuildDate><image><title>Conferences @ clintshank.javadevelopersjournal.com</title><url>http://res.sys-con.com/portlet/163/featured-blog-graphic-145.gif</url><link>http://clintshank.javadevelopersjournal.com/</link></image><ttl>360</ttl><docs>http://backend.userland.com/rss</docs><item><title>Quotes from No Fluff Just Stuff</title><guid isPermaLink="true">http://clintshank.javadevelopersjournal.com/no_fluff_just_stuff_quotes.htm</guid><link>http://clintshank.javadevelopersjournal.com/no_fluff_just_stuff_quotes.htm</link><pubDate>Mon, 28 Apr 2008 17:57:00 GMT</pubDate><comments>http://clintshank.javadevelopersjournal.com/console/comments/popup/?f=no%5Ffluff%5Fjust%5Fstuff%5Fquotes</comments><dc:creator>Clint Shank</dc:creator><description><![CDATA[<p>I just returned from this past weekend&#39;s <a href="http://www.nofluffjuststuff.com/">No Fluff Just Stuff</a> conference in Reston, Virginia.&nbsp; As always (this was my fifth show), I had a great time conversing with my peers and the excellent speakers.<br /><br />The following are some memorable quotes/paraphrases in chronological order.&nbsp; Some disclaimers: 1) you should always take quotes in context and 2) I could have misinterpreted the intent of the speaker.&nbsp; I&#39;ll try to provide some comments for additional context.<br /><br /><a href="http://www.devjam.biz">David Hussman</a>: &quot;You need to respect the <span class="definition">pomodoro</span>,&quot; quoting an Italian manager of a team who used a tomato timer.&nbsp; They would work hard for 25 minutes, then take a 5 minute break.&nbsp; When one developer wanted to keep working...<br /><br /><a href="http://www.devjam.biz">David Hussman</a>: &quot;Sometimes stand-up meetings turn into stand-there meetings.&quot;&nbsp; This is when nobody is saying anything and we&#39;re just going through the motions.&nbsp; I&#39;ve definitely experienced this.<br /><br /><a href="http://www.agiledeveloper.com">Venkat Subramaniam</a>: In the context of <a href="http://code.google.com/p/google-guice/">Guice</a>, when comparing annotation and xml configuration, &quot;Both XML and annotations are evil.&nbsp; Annotations are the lesser evil.&quot;&nbsp; My opinion is that annotations are a good addition to the Java language, but can certainly be overused.&nbsp; This may be what Venkat was talking about.<br /><br /><a href="http://www.thediscoblog.com">Andrew Glover</a>: &quot;Some people say, &#39;<a href="http://en.wikipedia.org/wiki/Behavior_driven_development">Behavior-Driven Development</a>  (BDD) is <a href="http://en.wikipedia.org/wiki/Test-driven_development">Test-Driven Development</a>  (TDD) done right&#39;, but I say BDD is Customer focused TDD.&quot;&nbsp; BDD is closer to the customer&#39;s language.<br /><br /><a href="http://www.nealford.com/">Neal Ford</a>: &quot;If there were a book written today about real world software development, it would be called Accidental Complexity, Ceremony Over Essence, Ensuring Your Job Security written by the Enterprise Architecture Team.&quot;&nbsp; Neal had tons of good quotes from his excellent keynote.<br /><br /><a href="http://www.agiledeveloper.com">Venkat Subramaniam</a>: &quot;We constantly create whack-a-mole systems.&nbsp; Fix the code in one place and this other, seemingly unrelated part of the code breaks.&quot;&nbsp; Venkat was comparing software development with the children&#39;s game.<br /><br /><a href="http://www.integrallis.com"> Brian Sam-Bodden</a> : &quot;Remember when you had to go outside your IDE to access your version control system?&nbsp; And then, that functionality was integrated with Eclipse?&nbsp; That&#39;s what <a href="http://www.eclipse.org/mylyn/">Mylyn</a>  does for task management.&quot;&nbsp; Less context switching keeps you focused.<br /> <br /><a href="http://agileartisans.com/"> Jared Richardson</a>  or <a href="http://www.nealford.com/">Neal Ford</a>: &quot;Ted Neward is the Las Vegas of speakers.&nbsp; You have to go see him at least once.&quot;&nbsp; I always enjoy Ted&#39;s sessions.<br /> <br /><a href="http://www.tedneward.com"> Ted Neward</a>: Sarcastically, &quot;The code is perfect when it leaves my desk.&nbsp; Something mystical happens afterwards that introduces bugs.&quot;<br /> <br /><a href="http://www.tedneward.com"> Ted Neward</a>: &quot;The Teddy Bear Technique has the added advantage of keeping people away, particularly when you&#39;re caught talking to it by a manager.&quot;&nbsp; The Teddy Bear Technique is the act of explaining your problem to a stuffed animal, and then suddenly solving it as you start to question your assumptions.<br /> <br /><a href="/console/admin/v5/edit/www.tedneward.com"> </a><a href="http://www.tedneward.com"> Ted Neward</a>: &quot;Oh Great Debugger, tell me where the bug is.&quot;<br /> <br /><a href="http://agileartisans.com/"> Jared Richardson</a>: &quot;Take a shortcut here, another shortcut there - you get to a point where you&#39;re so busy paying interest, you don&#39;t have time to pay the principal.&quot;&nbsp; This was in his talk about credit card software development (<a href="http://www.martinfowler.com/bliki/TechnicalDebt.html">Technical Debt</a> ).<br /> <br /><a href="http://agileartisans.com/"> Jared Richardson</a>: Quoting <a href="http://en.wikipedia.org/wiki/Watts_Humphrey">Watts Humphrey</a>, &quot;Developers are caught in a victim&#39;s mentality.&quot;&nbsp; We never think it&#39;s our fault, it&#39;s always somebody else&#39;s.<br /> <br /> Expert Panel: When asked for two words about <a href="http://en.wikipedia.org/wiki/Service-oriented_architecture">SOA</a>, some of the phrases were, &quot;<a href="http://www.w3.org/TR/wsdl">WSDL</a>  sucks&quot;, &quot;Consider <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer">REST</a> &quot;, &quot;Overly complex&quot;<br /> <br /> Expert Panel: When asked for two words about closures, one of the experts said, &quot;Use Groovy&quot;<br /> <br /><a href="http://wmrichards.com/"> Mark Richards</a>: &quot;Java has become over-bloated and way past its usefulness as a general purpose language.&quot;&nbsp; I think he was the one who said, &quot;Use Groovy.&quot;<br /> <br /><a href="http://www.g2one.com"> Jeff Brown</a>: &quot;If we could start [Java] from scratch today, Java would look like Groovy.&nbsp; Groovy is the preferred general purpose language.&quot;<br /> <br /> Jay Zimmerman, Symposium Director: &quot;If you want management approval to use Groovy, don&#39;t call it Groovy, call it Next Generation Java.&quot;&nbsp; Managers freak out when they hear you want to use something called &#39;Groovy.&#39;<br /> </p><p><a href="http://www.tedneward.com"> Ted Neward</a>: &quot;Your peer group is more important than any tool or book we can recommend.&quot;&nbsp; Great advice.<br /> <br /><a href="http://www.davebock.com"> David Bock</a>: &quot;The existence of the system changes the requirements of the system.&quot;&nbsp; Dave was talking about how seeing the system run changes the customer&#39;s mind of what he really wants.<br /> <br /><a href="http://www.davebock.com"> David Bock</a>: &quot;Never believe someone who tells you he&#39;s 90% done.&quot;&nbsp; Ever notice how that last 10% takes a long time?</p><p>I look forward to next time.</p><p>&nbsp;</p>]]></description><category>conference</category><category>show</category></item></channel></rss>