The other replies make fair points, but tillage does still have it's uses.

Quick examples:

  - Inversion tillage (ploughing) to bury green manure crops or bulky organic manure
  - Subsoiling (deep tillage) can help break underground compaction, to allow better root penetration
  - Working with soils prone to surface capping

There's also a spectrum:

  - Full inversion tillage
  - Low/min-till
  - No-till

With a wide range of operations you can perform from one end to the other. You might end up taking a mix-and-match approach as years/fields demand it.

EDIT: This is a response to the question "why do it?" rather than anything in the context of the article itself.

This is actual reality. No-till is great until you have to till because of circumstances. Sometimes what happens needs to be dealt with; we've had years of heavy, heavy rain, and despite decades of no-till farming, it still can't absorb limitless water. That's when compaction happens, especially if you need to get crops off wet ground. So you deal with it, and start again building the soil back from tillage. You don't have to always haul out the 3-bottom plow, but even discing has a recovery period. But it's better than trying to seed into concrete.

And tillage can work well by bringing up nutrients. Some crops will do this themselves to an extent, or you can plant forage crops for a time that will bring up nutrients. But subsoiling to break deep compaction or simply bring up phosphorus or potassium from lower levels can breathe new life into a field.

Whenever I read about poisoning LLM inputs, I'm reminded of a bit in Neal Stephenson's Anathem, where businesses poisoned the the internet by publishing bad data, which only their tools could filter out:

> So crap filtering became important. Businesses were built around it. Some of those businesses came up with a clever plan to make more money: they poisoned the well. They began to put crap on the Reticulum [internet] deliberately, forcing people to use their products to filter that crap back out.

When I'm in a tinfoil hat sort of mood, it feels like this is not too far away.

EDIT: There's more in the book talking about "bad crap", which might be random gibberish, and "good crap" which is an almost perfect document with one important error in it.

AI companies have already poisoned the internet.

Sounds in effect like what SEO / "trash article soup" companies did for Google et al the last decades.

There’s an archive of older versions here: https://files.menial.co.uk/base/

This app is great for writing code comments when you hit one of those “1000 words or 1 picture” cases for an explanation of something.

Just checked and my most recent document is a diagram of data flows between two services.

Highly recommended.

That’s not me. I was quite surprised - in a good way - to find it there.

And I welcome the feedback, even if I probably won’t follow it. If everyone thought like you do, then it’d be far nicer to publish the code and maybe charge for support. I’m fairly confident that not enough people feel the same way to make it work.

As to pricing, I need to be able to financially justify the time spent working on the app, and the price is one that I hope will let me do that.

I would love for you to make the code source available if you pay.

Or are you worried about people stealing and making pirated copies?

If the code were available I would 100% expect that someone else would distribute a binary with the paywalled features unlocked and that my original version would be relegated to secondary.

I know you could make the argument “the right license wouldn’t allow that”, but that would only be enforced if you follow up through the courts, perhaps internationally. I just can’t be doing with the hassle unfortunately.

In this case, no. It would be nice if it did though.

There’s two main reasons. One is that this is the first paid update in 14 years. The second is that it’s just such a pain to do that on the App Store and I don’t want to have a two-tier system. I’ve tried to strike a balance on the price bearing this in mind.

Understood, thank you!

To add to what xmprt and msephton have said, people have told me they use it for:

  - Storing results for scientific research
  - Local analysis of data exported from server-based databases
  - Experimenting with database designs before exporting SQL to codebases
  - Maintaining relational data where a website or app are not needed (eg. tutors keeping client records)
  - Recovering data from databases used by other products (eg. phone backups, discontinued apps)

Thank you. I don't have any other public apps at the moment.