The slogan of the Russian Revolution of 1917 was: "Factories to the workers, land to the peasants."
If the factory is yours, then everything inside is yours ;)
But it's funny how low wages under the broken Soviet economic system turned such things into a semi-official, informal work perks, allowing people to make ends meet.
It was less the low wages and more the general unavailability of things (shortages). Lots of things you couldn't just buy but you had to know somebody who knew somebody.
I wouldn't call it "funny" though. It ws quite sad and I'm glad it's over.
As I mentioned in another commebt, I don't even consider anything related to that to be a viable government system.
That said, the general unavailability of everything was caused by an incompetent government rather the the system itself but the system itself caused the government.
My point is that it was a succession of demagogueries hiding personal interests that caused the recurring and unrecoverable tragedies of that state. Being controlled and misguided is not exclusive to any particular government or political system.
This is not false but totally an oversimplification.
I don't think communism is a good form of government and I don't think the soviet union was marching the right way.
But the biggest blunts came from other much more serious mistakes caused by politicians ignoring science, like the big famine and many others, including the Chernobyl connerie
1. The problem is with using HTTP for APIs, not with GraphQL. HTTP was designed for rich (hypertext) documents, not for APIs. So layering GraphQL or any other APIs over HTTP is a hack.
2. GraphQL is useful for small remote teams b/c of mandatory staticly-typed schema and built-in schema documentation. Otherwise it's lots of back-and-forth between backen, frontend, QA, etc. You forced to use external tools like Postman collections, and still having communication problems.
> After years of debate and confusion, the GraphQL Working Group has reached a historic decision: starting with the October 2027 spec release, all GraphQL responses will return random HTTP status codes between 100 and 599.
> Additionally in order to make GraphQL AI Agents friendly, the GraphQL response body will be switching from JSON to Markdown.
imagined tasks == Jira
discovered tasks == Dark Jira
IMO, tickets for planned work are an anti-pattern. Tickets are good for reactive work: bug reports, support, etc. Use Kanban board for tracking them.
Planned work should be organically discovered from the plan by the developers (or agents) who will be implementing it, not assigned via Jira tickets by the project manager. Shape Up recommedns using Hill Charts for per-scope (vertical slice) progress updates.
The number of alternative public and semi-public companies went up exponentially (Reg CF/Reg A, crypto ICOs).
After reaching some thresholds a Reg A company can become public and even trade on OTC markets.
reply