June 19th - Heat Advisory and a Warning about 'Reasoning'
TL;DR
It was a very hot day after 11am field work. Fortunately, this crew and itās farmer know how to balance what needs to get done with what can get done within reason.
Nerd Note
Also, this is in part a retrospective about the past week of blogging augmented with a āreasoningā large language model (āAIā for the uninitiated) despite prompt tweaks that didnāt produce the expected results. I think I need to step back to reconsider the effectiveness of employing reasoning in all LLM use cases and instead specialize the LLM used in specific scenarios.
Balancing Worker and Weather Conditions
On a hot day, itās nice to work with a farmer that knows the value of factoring in whatās going on in the hourly (not daily) weather report with what the given crew on hand can handle.
Weather reports and conditions, notwithstanding the imposed level of inaccuracy being incurred by the current politically-fueled mass layoffs at NOAA, are almost always NOT what you experience in a particular location. This is because weather stations, aggregated across a wide area, are not able to capture the hour-to-hour microclimate fluctuations in temperature, UV index, and humidity that can occur in a specific location.
So today, between watering the greenhouse twice and early morning harvesting, Jamie (the farmer) kept our necessary work pretty well-balanced. Hot weather encourages many early-season crops to bolt (go to seed) and this is exactly what happens with lettuces and broccoli rabe in these fields when spikes in temperature occur. Just like too much rain all at once rotting rooty veg like radishes and salad turnips, extremes in anything are generally a source of stress on the crops and a need to āhurry upā about specific activities on the farm.
Sequencing and Variance
Today I spent most of the morning washing and packing crops coming in from harvesting in field. Because weāre always running tight on tote bins during the weekly harvest-to-sell cycle, every day thereās plenty of things to wash (rinse, wash, rinse, sanitize spray). Totes, harvest bins, surfaces, knives, buckets, floors, basinsā¦basically anything that comes in contact with produce at any stage is as clean as it can be made.
In every system, there is always a sequence of events and degrees of variance, as Dr. Eliyahu Goldratt would say. In this case, the sequence of events is clearly based on constrains while the system variance is driven in large part by the weather. Balancing these fluctuations is the job of a āmanagerā and how well they do this significantly impacts the success of the system.
Then in the afternoon I spent most of my time bunching scallions, radishes, and salad turnips. The barn has a mobile industrial fan which is *so necessary* and even on a hot day, opening both garage door sides gives a cross breeze that makes everything bearable.
But the biggest factor on a tough day is what and how the farmer calls the shots. What to rush on, what can be deferred to tomorrow/later, who to group with whom, who is wilting like the veg and needs a ācool downā activity when. Who can go the extra mile on something, who does or doesnāt have the training for a particular critical set of activities.
Manual vs. Automated Processes
When you automate something, you trade off the speed and repeatability of a process with the opportunity to perform quality control and the flexibility to adapt to changing conditions. In the case of farming activities, especially the mundane and manual ones are always an opportunity to check for quality and make adjustments.
Similarly, my work with LLMs is always an opportunity to check for the quality of the AI-driven summaries and make adjustments. Do I always do thatā¦particularly when Iām in a rush to get to the farm on the weekday mornings? Not always, as Commit d7408f2 to this blog yesterday including blatantly erroneous Deepseek summary activities includes. About two weeks ago, I switched from using Ollama 3.2 to Deepseek-R1:8b in my LLM backend because I thought adding āreasoningā would make the summaries better than without.
By switching to a āreasoningā LLM, all I did was add work to deeper validate what the output is saying. I didnāt trade speed or flexibilityā¦I traded verified quality for speculated quality but didnāt anticipate the actual time-cost of checking the change in process.
In my rushed prototyping work, I made the simple engineering mistake of changing multiple dynamics at once without verifying them separately: adjusting the process as well as foundational tech stack componentsā¦not unlike so many corporate management actors Iāve encountered over the years.
The short version is:
Approaching the Limits of a Lack of Context for LLM Work
For the past few months, Iāve been driving an LLM to produce summaries of transcripts so that my human writing is augmented with something āobjectiveā. Iāve learned that thereās a limit to how far a generic, mainstream pre-trained large language model can be expected to produce context-specific results for organic farming. I know that there are at least two things I can do to improve the situation:
- Implement a RAG/TAG model to verify that more context does/doesnāt improve the results
- Look at options for fine-tuning existing LLMs, particularly those that perform āreasoningā
Tweaking the prompt to include more context and/or fine-tuning existing LLMs, particularly those that perform āreasoningā, only go so far with these āmaths crystal ballsā (as I describe them to casual observers).
Until I can do the above, Iām relegated to micro-managing the LLMās output to ensure itās on-topic and on-brand. Case in point, retroactive updates bundled with new content wouldnāt fly in any legit dev team. So for the sake of principle today, Iāll use separate commits now but moving forward Iāll make sure that cross-outs are included in the LLMās output where I personally verify it to be wrong.
Every AI Model Has Defective Biases
Case in point, ābolting prevention strategiesā is not a thing in organic farmingā¦sort of. I mean, you can pluck seeding heads but thatās not really addressing the fundamental issue in the organism. The time trade-offs of micromanaging natural tendencies in plant species when coupled with organic practices just isnāt worth the over-inflated sense of economic virtue that high tech (agro or digital) is optimized to value.
The genomic makeup of the plants is what determines whether they bolt or not given specific conditions. Despite lofty modern AgTech claims over what it can control about crop productivity, the accompanying chemical-heavy WW2 litany of *-icides and productized synthetic fertilizers expose the faulty scientific longitudinal effectiveness that ābig ag(riculture)ā says it can deliver.
Dogs are a recent phenomenon. Plants are not. Did your bizarre conjunction of a Labradoodle exist 65 million years ago or was that over the past 100 years? Unfortunately, even modern organic crops service a similar human goal: convenience to humans and climate.
Similarly, all AI models have their own biases. Whether itās as overly simplistic as just āa problem with specific training dataā (though most useful LLMs are trained on a very wide sample of available data), the wideness of that public data, or the underlying process and people responsible for training the model, itās turtles all the way down. Case in point, todayās summary now includes crossed-out fallacies now that Iām pain-stakingly reviewing the output.
Todayās LLM (Deepseek-R1:8b) Generated Summary
Final Summary:
The intern focused on three main themes: Harvesting & Processing, Facility Maintenance, and Greenhouse Management. Activities included harvesting lettuce, salad turnips, and scallions; cleaning and organizing the barn; watering the greenhouse to manage plant stress; and preparing for CSA drop-offs.
No entirely new farming techniques or tools were encountered, though standard methods like using blue bins for washing were utilized.
Key questions and research areas include how to mitigate crop stress caused by high heat, effective cooling solutions for greenhouses, strategies to prevent lettuce bolting, and efficient cleaning practices. Suggestions involve exploring alternative planting schedules, innovative watering techniques, and measures to protect crops from excessive heat. Additionally, thereās interest in optimizing the use of leftover plants to reduce waste and enhance sustainability.
Part 1
Analysis of Farm Internās Field Notes
Main Themes:
- Daily Chores: The intern started their day with basic chores like watering the greenhouse and assisting with farm activities.
- Harvesting and Preparing Produce: They participated in harvesting vegetables such as radishes, kale, and Swiss chard, moving them to the barn for washing.
- Cleaning and Organization: The focus was on cleaning and organizing produce using blue bins, indicating a structured approach to handling crops.
Activities Performed:
- Watering the greenhouse.
- Assisting with harvesting and bunching radishes, kale, and Swiss chard.
- Moving produce to the barn for washing.
- Washing harvested vegetables in blue bins.
New Things Encountered:
- ~
Use of blue bins for washing produce.~ - ~
Specific crops like Swiss chard and their role in farm operations.~ - ~
Elastic used for bunching vegetables, suggesting a method or tool that could be explored further.~
Questions and Future Research Areas:
- The need to check irrigation systems due to dry spots in the greenhouse.
- Planting schedule optimization to minimize leftovers and excess produce.
- Exploring methods for more efficient washing processes in the barn.
Suggestions for Improvement:
- ~
Organize tasks more efficiently, possibly through role assignments or prioritization.~ - Ensure availability of necessary tools and their maintenance.
- Develop sustainable practices to reduce waste and optimize planting schedules.
Sustainability Considerations:
- Explore ways to integrate sustainability into farming processes to minimize waste and enhance resource efficiency.
This analysis highlights the internās contributions to farm operations while identifying areas for improvement and potential research opportunities.
Part 2
Main Themes:
- Harvesting Produce: The intern focuses on harvesting lettuce, salad turnips, and scallions, which are processed and packed for CSA drop-offs.
- Facility Maintenance: Cleaning and organizing the barn, including washing and sanitizing equipment and facilities, is a key part of their tasks.
- Greenhouse Management: Watering the greenhouse to manage plant stress due to high temperatures.
- Environmental Impact Awareness: Recognizing the effects of heat on lettuce growth and considering solutions like cooling systems.
Activities:
- Harvesting and processing vegetables (lettuce, salad turnips, scallions).
- Cleaning and maintaining farm facilities.
- Watering greenhouse plants.
- Ensuring readiness for CSA pickups.
New Elements: None new farming techniques or tools are mentioned. Standard methods are used.
Questions and Research Areas:
- How to mitigate crop stress caused by high heat.
- Effective cooling methods for the greenhouse.
- Lettuce bolting prevention strategies.
- Efficient cleaning and maintenance practices.
Suggestions/Actions:
- Consider alternative planting schedules to extend lettuce season.
- Explore efficient watering techniques or cooling solutions.
- Implement measures to protect crops from excessive heat.
Enjoy Reading This Article?
Here are some more articles you might like to read next: