agileroundtable.org

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: 24 hours of code

http://leansoftwarecincinnati.blogspot.com/2005/04/24-hours-of-code.html

Unites Lean Business Models and Agile Technology. Friday, April 15, 2005. 24 hours of code. Lean Software Development produces code on an ongoing basis, rather than in long waits and big chucks of deployment. Using xp www.lifeware.ch. Delivers code into production every working day. This is made possible by Agile processes like Extreme Programming (XP). And by smart technology choices. LifeWare uses Smalltalk. Another continuous code delivery technology will be demonstrated. 24 hours of code.

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: Throughput Accounting

http://leansoftwarecincinnati.blogspot.com/2005/06/throughput-accounting.html

Unites Lean Business Models and Agile Technology. Tuesday, June 21, 2005. Accounting has different problem solving schools of thought just like software development does. If you want to measure the effectiveness of a management decision you want to count the costs and benefits of that decision. The traditional way to do this is with Cost Accounting. In the Lean-Thinking approach, Cost accounting blamed for guiding companies toward inefficiencies. It reminds me of the struggle between the Data Processing ...

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: Field of Dreams

http://leansoftwarecincinnati.blogspot.com/2005/09/field-of-dreams.html

Unites Lean Business Models and Agile Technology. Thursday, September 08, 2005. In the last week, I've talked with two very smart, highly motivated programmers. Both are making plans to leave the Cincinnati area. Both say that there are no interesting programming projects going on here. All they see is old-style java and .NET projects that are missing the wave of new approaches. And they feel that they would put their career at risk by staying here. 1) Why are programmers leaving Cincinnati? If you see I...

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: Language and Culture

http://leansoftwarecincinnati.blogspot.com/2005/04/language-and-culture.html

Unites Lean Business Models and Agile Technology. Friday, April 08, 2005. Most J2EE development is in DP style That does not mean that you cannot do Object Oriented J2EE. But what people do with a language creates the language culture. Perhaps some people could build OO programs in a culture of DP, but it will always be fighting against the norm. DP is encouraged when requirements:. Specify the DB schema. Specify the data fields, flags, switches, and codes. Specify the data transformations. The first ste...

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: RailsDay Milestones

http://leansoftwarecincinnati.blogspot.com/2005/06/railsday-milestones.html

Unites Lean Business Models and Agile Technology. Saturday, June 04, 2005. The two programming teams in Cincinnati are Team8 and Team32. Team8 is doing a food tracking system. Team32 is doing a photoDepo. The contest rules require at least 12 check-ins. At this point Team34 has 16 check-ins and Team8 has 32. Today is Rails Day. Pdf: COBOL oriented J2EE. View my complete profile.

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: The Rails Day-After

http://leansoftwarecincinnati.blogspot.com/2005/06/rails-day-after.html

Unites Lean Business Models and Agile Technology. Sunday, June 05, 2005. Well, I didn't give as many "updates from the front" as I intended. But here is my rapid-review of the day of coding. Ok, now more detail. About 120 teams were signed up. 100 competed. This contest was world-wide. More details at railsday.com. We do wish we had another few hours to add some of the cool AJAX features and polish it up a bit more. Lines Of Code Produced. 445 (not counting the rhtml). Today is Rails Day.

leansoftwarecincinnati.blogspot.com

Lean Cincinnati: Recap: Lean Software Development

http://leansoftwarecincinnati.blogspot.com/2005/04/recap-lean-software-development.html

Unites Lean Business Models and Agile Technology. Sunday, April 10, 2005. Recap: Lean Software Development. The links in this recap all point to previous entries. It is a recap after all.]. Is that software projects still deliver an unacceptable level of quality and responsiveness. Part of the reason for this is the industrial-era Scientific Management. Approach. Part of the reason for this is the progamming culture. That grows up around a language. And start expecting zero defects. How hard can that be?

def-end.blogspot.com

def-end: Prototype and Witch's Brew

http://def-end.blogspot.com/2010/02/prototype-and-witchs-brew.html

Meteor, JavaScript, Ruby, Rails, and a smattering of other cruft from the back of Dave's mind. Sunday, February 14, 2010. Prototype and Witch's Brew. When things work differently in one part of a package than they do in another - for no apparently good reason - programming indigestion may occur. When you beat your head against the code for too long trying to figure out why things are screwing up, big headaches are sure to come. The cause of my current indigestion and headache? You may be asking, "Why doe...

def-end.blogspot.com

def-end: A little Hash goodness

http://def-end.blogspot.com/2009/09/little-hash-goodness.html

Meteor, JavaScript, Ruby, Rails, and a smattering of other cruft from the back of Dave's mind. Tuesday, September 08, 2009. A little Hash goodness. Some quick refactoring this weekend had me throwing together some tidbits. Return Hash of enumeration to yielded values. Def collect hash hash={}. Inject(hash) { h,e h[e] = block given? Yield(e) : nil; h }. Return Hash of enumeration to non-nil yielded values. Def select hash hash={}, &block. Collect hash(hash,&block).compact. Delete if { k,v! The Lust Lizard...