Viewing profile — arogozhnikov

> But these computation graphs are similar every time. For now I'm testing one-after-another because failure of previous (overflow, too-small-transfer, etc) gives a hint about whic…

Robotic planning of liquid handling. There are many potential alternative ways to achieve the same result, each resulting in its own computation graph. I imagine any kind of trajec…

same for me

sums it up pretty well

> API != User Interface. API = Programming Interface. That's where we should start, but the other way around. Why do you keep trying to replace programming interfaces with bash cal…

> then it should be pretty easy to test. If it is that simple, you can just devote this to package like typer. That's what I point to - don't write it. I see people somehow read GU…

ok, I understand now my question got misinterpreted, I'll rewrite that. CLI parsing (mapping to real calls) may have bugs. How do you test this? Both options suggested eliminate th…

+1 for reading post

> Agree the CLI "shell" around the system should not have separate logic that was the main point. > should report back logic faults from within the library And I suggest validating…

It looks new - but is it any more complicated if after all that's what your call maps to?

It is easy only if you write CLI utility (or somewhat very light-weight). Imagine you write ASR system (from CLI input to output - week(s) of training, requires several servers). M…

+1ed the issue. I was sure that's a problem on Safari side.