garrybelka

Velcro, I guess.

https://elizarov.medium.com/structured-concurrency-722d765aa... https://elizarov.medium.com/coroutine-context-and-scope-c8b2... https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-corout...

Acceleration - d2t

Rate - dt

Labor - dt

Productivity - dt

Growth - dt

Altogether d6(Work)/dt

The quote in Russian is an example of a 6th derivative.

It was often mentioned next to a proof that the party line was straight (каждая точка - точка перегиба).

"Acceleration of a rate of labor productivity growth" - 6th derivative.

Not found in English, but in original Russian - "ускорение темпов роста производительности труда" - about 4,090 results in Google.

"The acceleration of labor productivity growth" in English - about 11,700 results. But that's only a 5th derivative.

A better analogy is a ship sailing against the wind: "To reach its target, sailors that intend to travel windward to a point in line with the exact wind direction will need to zig-zag in order to reach its destination. This technique is tacking." https://www.lifeofsailing.com/post/how-to-sail-against-the-w...

I do not use git flow. Only mentioned it here as a lesser evil than getting rid of git at all. Any reasonable predefined flow will do.

Besides, in my experience, a review system such as Gerrit or GitHub has a huge impact on whatever flow is convenient to use.

That works but:

- pushes code into a master before it is ready

- makes next to impossible to work on several tasks at a time: current state of incomplete tasks is spread all over in the master. Even working on a single multi-day task with multiple commits, it's harder to see the task changes and any slight feature refactoring during prototyping or development now involves master.

An easy modification to this flow is:

1. Make a branch from master called `yourName/featureName`

2. While feature is not ready:

2.1. Work on the feature for a day or two max

2.2. Pull master, rebase your branch from master

3. Merge it right to master when your branch is ready

Some options:

- Read a book or tutorials about reimplementing git. That will make clear its data model and how it works.

- Use libgit2 to extract some data from a git repository. As a side effect, you will become a git expert.

- Think what would you like as your source control flow. Use libgit2 or its binding in your favorite language to implement it.

- Adapt git flow or a similar predefined control flow.

- Try Fossil SCM (by the author of SQLite). Not recommended - you will need git in your career.

GrahpQL might be an answer.Though an incomplete answer at this point due to a mismatch between plain GraphQL and SQL;

And the real issue is how to define and where to place a single source of truth for the schema an operations. So far we saw approaches where:

- GraphQL schema is generated from SQL tables. Makes total sense for a project or a company that looks to capitalize on customers with existing databases (e.g., PostGraphile, Hasura);

- SQL schema is generated from a GraphQL schema;

- SQL schema and TypeScript CRUD resolvers are generated from GraphQL schema (graphback);

- a language is introduced and GraphQL and SQL are generated from that language (Prisma);

- a library and a set of decorators are used to define both GraphQL schema and a typed ORM schema within a standard language (e.g, TypeGraphQL + TypeScript + some ORM such as TypeORM).

How is it different from Slonik? https://github.com/gajus/slonik

Location: San Francisco

Remote: Yes

Willing to relocate: No

Technologies: Backend (Python, Flask, Django, etc), some frontend (mostly VueJS), clustering infrastructure (incl. Zookeeper), scalability, high availability, distributed systems, cloud (experience with GCP, AWS), etc. Python3, Java, C++, C, JavaScript, TypeScript.

Resume: on request.

Email: {this account name} at gmail

Done and released a complete SaaS implementation, complete clustering infrastructure software, big data infrastructure, etc.

Interesting. Who designs and makes non-OE parts for Steelcase chairs? It doesn't seem that the market is that big...

For a while I preferred Herman Millers. But after spending a year with Steelcase chairs I discovered that Leap is the most comfortable and least fatigue inducing chair for me. I even liked that its seat holds its angle - unlike swivelling seats of HM chairs. Fortunately, Madison Seating sells used Leaps for less than $300 in perfect condition so I got one for home too instead of a previous favourite from Herman Miller.

Ethnogenesis and the Biosphere by Lev Gumilev http://gumilevica.kulichki.net/English/ebe.htm

Surprisingly, not only ethnoses have an age, but their growth, development and aging follows a fairly common trajectory.

And Heimito von Doderer. His stories, novellas. The Last Adventure.

But, as introduction or a summary of a Fin de siecle Vienna that was a progenitor of XXth century and "proving ground for the destruction of the world", start with Allan Janik, Wittgenstein: Vienna Revisited. Wonderfully succint and comprehensive overview.

Mourinho analysis on RT is fantastic. His depth of perception and clarity are nothing like what I heard before and in 10 minutes or less create a new understanding of a game. Clearly, for him spaces and space creation are the tools of his trade.

People say everyone was doping. Lance, Floyd, Tyler, Levi, Big George, etc. A crime without victim - everyone did it.

I never saw anyone claiming Chris Horner was doping. He was not competitive internationally until his last years on the circuit when doping use somewhat subsided.

Chris Horner is the victim. In a better world it's Chris Horner who won Tour de France.

Look at Mizuno, Asics.

Maybe one or several guys a year - winners of international math olympiads or folks on a similar level. E.g., https://en.m.wikipedia.org/wiki/Maxim_Kontsevich

At least, until mid-eighties. Some years were worse than others.

Why, preparing for an interview.

L4 might be an option. http://l4hq.org/projects/os/

original with no pay wall: http://www.foxbusiness.com/features/2017/09/09/why-amazons-g...

It's actually described by We.

By context you mean a timeline of events while speech recognition is actually dependent on that timeline. Same applies to situational state recognition in driving. E.g., to derive speed, acceleration and direction of objects.

My shepherd is by no means special yet he asks 'Why?'.

He plans, hopes, and most definitely has and could express wishes. And while his intelligence is limited and very material in a pragmatic way he does possess a language (that I'm still learning) and he could reason.

He is not into abstractions, but, perhaps, could master one or two with a sufficiently tasty motivation. But he understands generalisations, conditionals and iterations.

And me, please!