[ectoplasmaboiii]

Not a large K program, but a company I used to work for maintains a large, open source q framework https://github.com/AquaQAnalytics/TorQ which is used in many large investment banks and hedgefunds.

Funnily enough, the framework is actually a more expansive version of a tick system developed by Kx (the company that makes kdb) https://github.com/KxSystems/kdb-tick

The Kx one is incredibly concise. When I first started working with it, it took me a while to figure out what was going on.

The larger K/q programs get, the more they tend to look like "normal" code, but you still see a lot of these clever one liners hidden away in there.

[clarry]

> The larger K/q programs get, the more they tend to look like "normal" code, but you still see a lot of these clever one liners hidden away in there.

Yep, that's what I suspected. TorQ confirms it.. giving everything a single-letter name will no longer do :-)

I'm a bit surprised at the number of comments that explain what the next line does. I'm not sure what to think of that, but it reminds me of beginner tutorials explaining code for people who can't yet read it confidently; for obvious reasons, not a popular style among more conventional languages.

[scythe]

Thanks! This is the kind of thing I was looking for:

https://github.com/AquaQAnalytics/TorQ/blob/master/code/proc...

I could imagine working on a codebase like that.