Why don't we write code that just works?
Or absent a "just works" set of patches, why don't we revert to code
that has years of testing?
This kind of "I broke things, so now I will jiggle things randomly
until they unbreak" is not acceptable.
Either explain why that fixes a real BUG (and why the magic constants
need to be what they are), or just revert the patch that caused the
problem, and go back to the allocation patters that have years of
Guys, we've had this discussion before, in PCI allocation. We don't do
this. We tried switching the PCI region allocations to top-down, and
IT WAS A FAILURE. We reverted it to what we had years of testing with.
Don't just make random changes. There really are only two acceptable
models of development: "think and analyze" or "years and years of
testing on thousands of machines". Those two really do work.
[videoplayer file=”/wp-content/uploads/2011/04/04-17-11.mp4″ width=”640″ height=”379″ autostart=”false” /]
Nature-Inspired Programming Recipes
via Clever Algorithms: Nature-Inspired Programming Recipes.
This time i’m going to talk about the basic components that make up a physics engine and how to put them together; this tutorial is aimed at programmers who have a basic grasp of maths and geometry but would like to step into the world of simulation.
via Physics engines for dummies | Pauls blog@Wildbunny.
The Cicada Principle and Why It Matters to Web Designers » HTML & CSS, Layout » Design Festival.
on using primes to create nicely repeating backgrounds. I’ve used similar techniques to this on 3D networks…