Comments for /home/dkramer

Comment on Adobe Flex For Software Engineers by John

John — Fri, 15 Jul 2011 02:48:22 +0000

I concur with your assessment Dave. Spot on.

Comment on Religous “EXCUSE ME!?!?!” Of The Day by ROY

ROY — Fri, 08 Oct 2010 22:41:22 +0000

My x-wife was a nun. The Church seemed to never care about them. They were psychologically abused.
The only problem I could see in the article, if true, is thatsuggesting that Jesus Christ is, was, and forever be the only Son of God. I would suggest that every Christian pray often requesting God to allow everyone after they are dead to see what heaven (being with God) really is and giving them opportunity to choose their final destination.

Concerning the “catholic Church” might I suggest that the vatican place 100% of their efforts into ensuring that believers are physically and speritually nutered by the Priesthood. And, not abused by them.

Comment on Using And Making Open Source Software by Eric C

Eric C — Tue, 05 Oct 2010 13:52:12 +0000

Very well written. Many thanks.

Comment on Software Work In Process by David Kramer

David Kramer — Tue, 07 Sep 2010 14:28:51 +0000

Excellent point. Yes, there is a parallel in software. When you have work in process of any importance, you’ve committed to certain design decisions and implementations in that code. But since it’s not working and integrated yet, you don’t know whether it actually works yet. You still must abide by those design decisions in your other work. If integration and/or acceptance tests prove those designs unworkable, you need to reimplement them in your WIP, but you also need to change it in any other code you made based on those unproven designs.

As an example, let’s say you’re adding some new component to the system. It’s taking a while, and others need to use it, so you create a stub implementation and check that in so others can access the API. If, as you flesh out the real code, that design won’t work and the API needs to change, now the users of your class need to change their code to. This multiplies the uncertainty.

Thanks for commenting.

Comment on Software Work In Process by Jon Friedman

Jon Friedman — Tue, 07 Sep 2010 14:15:54 +0000

David:

Good post.

In manufacturing planning, obsolescence is discussed as an issue related to WIP. When a Bill of Materials changes, subcomponents in WIP need to be reworked or scrapped. The less WIP, the less rework. I wonder if there is an analogy here? For example, a partially completed task left for the next iteration could be obsoleted if the requirements change between iterations.

Jon

Comment on I am once again employed by Tim King

Tim King — Mon, 21 Jun 2010 18:57:19 +0000

Congrats, David! I hope you enjoy your time there and gain some memorable experiences out of this position. -TimK