Category: Uncategorized

The Scribe’s Day Off: From 1880 Archives to 2026 Vines

We’ve spent the last few weeks teaching an AI to read 19th-century cursive and build a social graph. It works. The Digital Scribe is now a fully realized Knowledge Graph. But a Sovereign system shouldn’t be a one-trick pony.

The Mid-Summer Anxiety:

It’s June in Oregon. The Pinot Noir, Riesling, or one of my personal favorites, Maréchal Foch, and other varietals are hitting their stride, but the “mid-season jitters” are setting in for vineyard owners. You have 100 acres of prime fruit, but contracts for only 30. In the traditional model, that’s 70% risk. In a Sovereign Model, that’s 70% opportunity.

The Tech as a Tool, Not a Toy:

The same architecture we used to link a “Boarder” to a “Head of Household” in 1880 is what allows us to link “High-Acid Green Grapes” to “Premium Verjus Markets” in 2026.

Not familiar with Verjus? It’s a highly acidic juice made from unripened grapes thinned during the summer. In a standard year, these “green” grapes are dropped to the ground and left to mulch. In an Agile Harvest, they are identified by the Scribe as a high-value culinary asset, providing cash flow months before the primary wine harvest even begins.

By moving the “Scribe” from the archive to the tractor, we’re demonstrating that local-first, governed AI isn’t just for historians, it’s for the farmer who needs to decide, today, whether to thin their crop for a secondary market or risk a “hang-time” that may never pay off.

What’s Next:

Next week, we kick off The Agile Harvest. We’re putting down the ledgers and picking up the refractometer. We’re going to talk about varietals, market pivots—from mid-summer Verjus to late-winter Ice Wine—and why a ‘Knowledge Graph’ is the best friend a grower can have during a lopsided season.

Digital Scribe Series

Facebooktwitterredditlinkedinmail

Assignment Operators in R – Which One to Use and Where

Whenever you start learning a new programming language, you must get accustomed to the language’s syntax. One of the first operators you’d expect to come across is the assignment operator for the language. Assignment operators are used to, well, assign values to variables. The R language has a few different ways to assign values. Let’s take a quick look and them and some of their differences and use cases.

Assignment Operators

R has five common assignment operators:

  • <-
  • ->
  • <<-
  • ->>
  • =

Many style guides and traditionalists prefer the left arrow operator, <-. Why use that when it’s an extra keystroke? <- always means assignment. The equal sign is overloaded a bit taking on the roles of an assignment operator, function argument binding, or depending on the context, case statement.

Equal or “arrow” as an Assignment Operator?

In R, both the equal and arrow symbols work to assign values. Therefore, the following statements have the same effect of assigning a value on the right to the variable on the left:

x = 42

x <- 42

There is also a right arrow, -> which assigns the value on the left, to a variable on the right:

42 -> x

All three assign the value of forty-two to the variable x.

So what’s the difference? Are these assignment operators interchangeable? Mostly, yes. The difference comes into play, however, when working with functions.

The equal sign can also work as an operator for function parameters.

x <- 42
y <- 18
function(value = x-y)

History of the <- Operator

Where did the arrow as an assignment operator originate? As you may know, the R language has its origins in the S language. S was originally influenced, in part, by APL. APL had its own keyboards which included arrow symbols.

APL Keyboard Layout - Assignment Operators next to the "P" key

The S language also didn’t have == for equality testing, so that was left to the single equal sign. Therefore, variable assignment needed to be accomplished with a different symbol, and the arrow was chosen.

Conclusion

There are some differences of opinion as to which assignment operator to use when it comes to = vs <-. Some believe that = is more clear. The <- operator maintains backward compatibility with S. Google’s R Style Guide recommends using the <- assignment operator, which seems to be a pretty decent reason as well. When all is said and done, though, it is like many things in programming, it depends on what your team does.

R is a great language for data analysis. If you’re interested in learning how to use R to explore data in a MongoDB database, please check out this blog post I wrote. There are many uses for it, and knowing a bit about the assignment operators and which one to use should help tremendously.

Facebooktwitterredditlinkedinmail