The Boox is a little cheaper, I have one. It's mostly just an Eink Android tablet. I absolutely love it.

It will run most Android apps (modulo Eink screen support). The built-in note taking app is terrific.

You've probably heard of Org mode. Go look it up - md and a todo app is exactly poor man's Org mode.

I’m a big lover of the ecosystem and a heavy Emacs, but after several attempts I couldn’t get into Org mode: (1) it’s too complex and full featured, while my loose mind requires a strict and minimalistic system to be productive; (2) mobile support is quite lacking — yes, there’re beorg and Mobileorg, but they don’t do it for me for one reason or another.

So I’ve a custom GTD-like system build using iOS reminders, .md files, and a couple of scripts.

Yes, or Org mode can be quite complex if you let it be. I mostly only use the same features as markdown supports: headings and code fences.

For mobile (Android) I use Orgro.

does not have paper ergonomics

Right, I replied to the guy who holds the stance that "paper fails at organizing".

That's how the wife knows he's being serious during an argument. He goes and stows his trolleys.

Though Arabic has quite a few letters you won't find in the Latin alphabet, all the letters in the word shakshukah map perfectly to Latin letters. But put an H on the end, and quarter-pronounce it.

The spelling still had to be romanized. The Wikipedia page has three different spellings for it, though none match yours.

I stand by my point.

  > if you wanted chicken, they killed it in front of you. Needless to say, being directly confronted with the process…I didn’t eat meat the entire time.

The one time I had opportunity to kill a bird with my own hands and eat it, I ate it with far greater respect and less waste than any meat I'd ever even before or since. I wish there were an efficient way to bring the consumer closer to the animal in everyday Western society. I doubt that we would consume less meat, but we would certainly have more respect for it.

They would definitely waste less of it, and probably consume less as well.

In the spec.

Hmm... my code is the spec. It just happens to be executable. Is writing a precise spec in English easier than in a programming language?

The spec contains ambiguities and the code contains bugs. Clarifying ambiguities in the spec with stakeholders, allows one to reduce bugs in the code.

If you repeat this process until all ambiguities in the spec are eliminated, aren't you essentially left with code? Or at least something that looks more like code than plain English?

No

I just like to add that the database design is the real secret sauce, important even more than external APIs in my opinion.

This is something that I've stumbled into as well. DB models AND dataflow. Getting both of those well spec'd makes things a lot easier.

Well, not DB design really, you can achieve the same thing by defining your POCOs well. I switched entirely to code-first design years ago. If you haven't worked with a good ORM, you're really missing out, though I admit there was quite a bit of friction at first.

No, I really am talking about how the database is organised. Tables representing objects, normalisation, etc. Whether or not it is accessed through the application with an ORM.

All sufficiently advanced technology...

I'm most interested in the CRM. I'm a Linux and Android user, so there's currently nothing for me to try, but a page dedicated to the CRM features might get my email address on your mailing list.

Good luck!

Thanks for the feedback

Was that on the -57?