bulldozer

I will bring a bulldozer to Googler Mission Wonderland the day you bring a bulldozer to low-density Palo Alto whitey-ville.

That is, if you have an old bulldozer sitting out in a field, it's costing you nothing.

To stabilize the grid you have a bulldozer (the throttle) and a little scalpel (capacitor banks).

Their downfall was their insistence on pushing out Bulldozer despite the fundamental flaws in its concept.

This is like saying that you can drive a bulldozer into a house but the bulldozer and house don't have to destroy each other, that they have the option of happily occupying the same space.

It would have gotten heavily compacted as the bulldozer drove across it.

Imagine a robot about the size of a small refrigerator that creeps along the field on bulldozer treads, digging holes and dispensing seeds as it goes.

In 1999, prototype self-steering ag equipment could get the angle of the working implement (bulldozer blade) by having GPS antennae on the perimeter of the vehicle.

Why would that help AMD, when Bulldozer already does hyperthreading?

To expand on this - the Bulldozer FPU is supposed to be SMT, but the integer cores are single threaded; two integer cores share an FPU, making a 'module'.

Technology wasn’t an intrinsic leveler or a bulldozer to archaic structures: It just gave people new, improved tools to be lovely or horrible to each other in all the old ways.

For example, is a smallish piece of equipment which can take many different parts on the end of the arm, work very slowly as a bulldozer, and fit inside our payload budget.

Likewise, 1.5 "Bulldozer" aka breaking up a function into subfunctions that aren't "useable everywhere".

> "Bulldozer code" that gives the appearance of refactoring by breaking out chunks into subroutines, but that are impossible to reuse in another context (very high cohesion) > 3.

The only one whose legitimacy as an antipattern I would question however would be this one: >"Bulldozer code" that gives the appearance of refactoring by breaking out chunks into subroutines, but that are impossible to reuse in another context (very high cohesion) I think it is useful to break up complex logic into discrete methods that represent some logical step in the overall algorithm.

He said, "just have to get out of the way," and when I gave a quizzical look, continued, "That guy is a bulldozer." Basically, you might sweat for a year and end up being a special case of a more general result that Talagrand just proved.

Bulldozer sadly had been for quite some time even slower that K10.

Guess it's their time for another Pentium4/Bulldozer mistake?

I still hope AMD will make another sudden leap like that, to keep the x86 market more competitive, but they seem more intent on keeping to the path started by Bulldozer...