<commit_before># Programmatic Diary

```javascript
function (foo, fields, baz) {
    foo.forEach(function (item) {
        if ($.test(item.type == 'integer')) {
            _$field = (_$field & $sign) ? ($mask - _$field + 1) * -1 : _$field
        } else {
        }
    })

    $(fields = fields.forEach(function () {
    }))

    $.switch(index, function () {
        return $.forEach(function (racket) {
            return
        })
    })

    while (bite != $stop) {
        if (start == end) return start
        _$field += Math.pow(256, bite) * buffer[start++]
        $($direction < 0, bite--, bite++)
    }

}

function other ($) {
    var $, bits = (mask >>> (field.bits - pack.bits)).toString(16)
    unsigned = $reference
    unsigned = unsigned < 0 ? bits + unsigned + 1 : unsigned
}
```

Now that I think about it, why am I trying to survive minification? The route
I'm taking now would require the user to install a parser. That's more
complicated than minification isn't it?

## Concerns and Decisions

 * Decided that I do not care about minification. Realized, too, that a
 generated generator that contains an AST would be minification safe.

## Generator Output

Generators can be output, written to file, then distributed as source. They can
also be unit tested.<commit_msg>Notes on crufty decisions to make progress.<commit_after># Programmatic Diary

```javascript
function (foo, fields, baz) {
    foo.forEach(function (item) {
        if ($.test(item.type == 'integer')) {
            _$field = (_$field & $sign) ? ($mask - _$field + 1) * -1 : _$field
        } else {
        }
    })

    $(fields = fields.forEach(function () {
    }))

    $.switch(index, function () {
        return $.forEach(function (racket) {
            return
        })
    })

    while (bite != $stop) {
        if (start == end) return start
        _$field += Math.pow(256, bite) * buffer[start++]
        $($direction < 0, bite--, bite++)
    }

}

function other ($) {
    var $, bits = (mask >>> (field.bits - pack.bits)).toString(16)
    unsigned = $reference
    unsigned = unsigned < 0 ? bits + unsigned + 1 : unsigned
}
```

Now that I think about it, why am I trying to survive minification? The route
I'm taking now would require the user to install a parser. That's more
complicated than minification isn't it?

## Concerns and Decisions

 * Decided that I do not care about minification. Realized, too, that a
 generated generator that contains an AST would be minification safe.

## Generator Output

Generators can be output, written to file, then distributed as source. They can
also be unit tested.

## Literals Versus Identifiers

To get going with Programmatic we're going to need build a project, and that
project is Packet. When I created this library as a string manipulation library,
I distinquished between replacing literals and identifiers. Whatever reasoning I
used then, I'm going to use now. After having a code base, I'll be able to see
if the distinction can be removed.

Also, I'm not going to beat too hard on the syntax. I'll probably use some sort
of dot notation on the initial variable, the `$` variable, for now. After Packet
is complete, I can look and see if there are patterns that would make more
sense.

```javascript
$('_' + value) // means evaluate
($ + value) // could mean literal, or quote.
$ + value // could also mean.
$(function () {
    return calculated.values
}) // evaluated at runtime.
```
{'fraction_non_alphanumeric': 0.11529548088064889, 'fraction_numerical': 0.005793742757821553, 'mean_word_length': 2.9016949152542373, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6896923', 'n_tokens_mistral': 1017, 'n_tokens_neox': 963, 'n_words': 411}