Developer-Centered Development Teams of developers and their direct managers prioritize work making sure the highest priority work is tackled first, that it is matched with the right engineers, and things overall are moving forward. The other disciplines such as Test and Program Management consume and are affected by decisions Dev makes. One usually sees program [...]
Archive for the ‘Technical’ Category
Development Processes
Posted in Technical on March 7, 2010 | Leave a Comment »
First Impressions of Google Wave
Posted in Review, Technical on November 30, 2009 | Leave a Comment »
Google Wave is currently in invitation-only, preview mode, so any judgment of its value in finished form is potentially premature. Two initial impressions stand out and seem often repeated. Firstly, the small set of initial invitees has the effect of limiting the kinds of conversations and the types of uses to which Google Wave can [...]
Home Network (Part 3 of 3)
Posted in Technical on August 1, 2009 | Leave a Comment »
In the last post, my home network was a single sub-net and supported wired and ABG wireless devices including a Wii, XBox 360, one wirelessly-connected Color/FAX printer, wired LaserJet printer, two wired desktops, two wireless desktops, and three laptops. In the last week, I’ve replaced this network piece-by-piece as follows: First, I added a LinkSys [...]
Home Network (Part 2 of 3)
Posted in Technical on August 1, 2009 | Leave a Comment »
In the last installment, I described the basic single sub-net home LAN with two runs of CAT5 (one going upstairs, and one going downstairs). In this installment, I describe our foray into the wireless world. As our kids became older, it became more and more important for us to have a centrally-located computer downstairs. So, [...]
Home Network (Part 1 of 3)
Posted in Technical on August 1, 2009 | Leave a Comment »
The first part will cover the basic one-subnet, home network. The second covers the ABG wireless period including problems with the XBox. And, the last covers the current two-subnet ABGN+ wireless period. DSL from Verizon is straight-forward for most people. The fastest available to us was the 3Mb-up-1.5Mb-down DSL (which establishes a line speed that [...]
Hatori, Spike One, Code Gen (Part 1)
Posted in Technical on November 7, 2008 | Leave a Comment »
The two ‘Dragon’ compiler books are wonderful, and the labeling described here is but one of the several methods the Dragon books describe, but they leave Ershov numbers and labeling open to confusion. In the First Edition, the fictional target is a two-address machine whereas in the Second Edition, they change to a more RISC-like, [...]
Hatori, Spike One, Parser (Part 2)
Posted in Technical on November 6, 2008 | Leave a Comment »
Continuing from Part 1, we start describing hatori.y. Notice the tokens (NUMBER and ID) used by the updated scanner are defined here. Bison will produce hatori.tab.h from this. Also, sometimes we manipulate pointers to Node structures and sometimes we manipulate an index to either an ID or NUMBER, so the parser needs to know which [...]
Hatori, Spike One, Parser (Part 1)
Posted in Technical on November 6, 2008 | Leave a Comment »
The next stage (or two depending on how closely you look) is the parser. I say two because this parser will also have some minimal semantic actions that act as an interpreter for our language. But, first, we need to change the scanner to pass its results to the parser instead of printing them out. [...]
Project Hatori, Spike One, Scanner
Posted in Technical on November 5, 2008 | Leave a Comment »
Lexical Analysis or Scanning looks at the stream of incoming characters and breaks them up into tokens. It can taken into account local context, but our initial language doesn’t need this ability. For the example input in the previous post below: b = 200; a = 1 + (-b/2)*30; a; b; Our scanner produces the [...]
Project Hatori, Spike One, Definition.
Posted in Technical on November 5, 2008 | Leave a Comment »
The project name, Hatori, comes from the name of a Fruit Basket character. A spike is a term from the Agile Development methodology for a narrow, deep coding experiment used to improve estimates and remove design risk. Perhaps the distinction between a spike and a prototype is only cover for developers to say that they [...]