Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Basic Coding Tips: Parsimonious Parameterization

by TimToady (Parson)
on Jan 29, 2005 at 20:54 UTC ( #426285=note: print w/ replies, xml ) Need Help??

in reply to Basic Coding Tips: Parsimonious Parameterization

A higher-level view of this is that the programmer must be aware of when a transaction is happening, and avoid installing any "holes" that allow the transaction to end up partially committed. The analytical/reductionist mindset of "break it down into steps" must be balanced by the synthetic/holistic flipside that says "this whole thing is just one step". Transactions are not just something that database programmers have to worry about. I think training in transactional thinking tends to fall through the paradigmatic cracks because transactions can't be classified as functions or events or objects. If anything, a transaction is most closely related to the logic programming paradigm, which is undertaught. A transaction can be viewed as a sort of hypothesis that can either be proven or disproven. A partially proven hypothesis is of little use.

Comment on Re: Basic Coding Tips: Parsimonious Parameterization

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://426285]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (3)
As of 2015-10-10 11:10 GMT
Find Nodes?
    Voting Booth?

    Does Humor Belong in Programming?

    Results (255 votes), past polls