 And I think it's best framed in terms other than "ownership". One can state one of the major challenges facing libraries in these terms. You could call these various attempts - in particular at guitar and Go - "learning Katas". Not all code is equally defect-prone; a small number of source file often accounts for a disproportionate fraction of all defects. Are the generated code files checked into version control ? What I'll do is write a blog entry sometime this afternoon - if I can explain it to someone else I'll feel confident I won't get bitten again. I will watch what happens with interest. I would have been interested to learn what they see as priorities: what are the three or four things that JISC could fund to effectively advance some of the topics they describe. It will be based on a database of people and organisations with records contributed from a variety of sources including the Australian Name Authority File. To respond is less effective than to anticipate. " That's when you're lucky. It will be based on a database of people and organisations with records contributed from a variety of sources including the Australian Name Authority File. " I'll check for a large number of defects associated with that class. We run the unit tests in our local sandbox, they all pass. I know that there's some interesting research concerning, for instance, power law distributions in source code. We run the unit tests in our local sandbox, they all pass. The payoff is early intervention - think of smoke detectors. "Invalid login," it said, cold as a judge. " I'll check for a large number of defects associated with that class. If you value learning for its own sake, you will move on to new skills any time you feel insufficiently challenged, etc. Overall, one could imagine how it could be more specialized to the needs of those interested in this topic and how the various services presented could be more integrated. I agree that accountability is important. There are two main things I try to help with, when a team wants my help: clarity of purpose, and fresh ideas. "Last Copies: What's at Risk? It has a strong family resemblance to YouTube, including the emphasis on ease of linking from and embedding in blogs and other sites. interesting ideas about the inner workings of hash tables. These are wide-ranging and it is instructive to see what they think is important or advisable. O'Neill, and Chandra Prabha. This is a very helpful piece of work which reviews a variety of approaches. I knew some of the basic tactical instincts of the game, but I was quite deficient in strategy. It feels like ascending a steep slope - sometimes it feels like making no progress at all, in fact. I knew some of the basic tactical instincts of the game, but I was quite deficient in strategy. This does away with the need to struggle with multiple players, and supports the easy linking and embedding which is promoted by YouTube. There's a number of anti-patterns related to code generation; I'll make a note to look into that later. |
_______________________________________________ Patches mailing list [email protected] http://mail.python.org/mailman/listinfo/patches
