Not boring, and a bit of a condescending prick

2021-07-01 17:33:31 Embarrassingly, I knew it since forever that git upstreams can be local dirs, but it always felt a tricky feature to use.

So, even when we all knew a git proxy would help speed up cloning the repos, I was somehow reluctant to look into this.

Well, git upstreams can be /home/dima/.my_git_cache/${repo_name}. In other words:
• Create a .my_git_cache local dir.
• Clone everything you need there.
• (You may even "clone" from your local, already cloned, dirs, just make sure to change their upstream to the true ones.)
• Write a cron script to do git fetch in all those .my_git_cache/* repos every few minutes.
• For your new repo, add this .my_git_cache as one of the upstreams, e.g. cache.
• (You may also want to mark it read-only by preventing pushes to it, just to be safe).
• Now, establish a habit of saying git fetch cache every time you need to sync with the "true" upstream.

Voila. Time saved: hours and hours. A rewarding git experience: priceless. Open / Comment

2021-06-17 19:59:42 After drinking the C++ metaprogramming cool aid for several months, we are now seriously debating whether it's a good idea to have a universal wrapper that would make functions accept arguments in any order.

They are all of different types, after all, and we use enum classes and user-defined literals everywhere, for readability reasons. So, there are no bool`-s left, and any number or string would likely be suffixed by some `27960_container_port or "/tmp/foo/bar"_host_dir.

Spoiler alert: I am now the one advocating against this idea.

Although the chaotic part of me wants to go full Haskell mode and implement an even stronger wrapper. So that "partial specializations" would result in "Currying 2.0": returning functions of lower arity, with some argument values already preset.

(The chaotic evil part of me is even thinking about compile-time checks that we should be able to associate with these wrappers.) Open / Comment

2021-05-30 00:07:51 Today's System Design Meetup is about monitoring production services, at scale, about detecting possible issues early on, and about reacting to them promptly and correctly. Here's the video and the slides. Open / Comment

2021-05-16 18:21:04 Open / Comment

2021-05-08 23:54:31 Exactly Once: today's system design meetup video. And the slides.

We covered the narrow edge between the easy problems and the hard one, touched on message sequencing / "serialization", Kafka, Lamport clocks, the CAP theorem (once again), and how to deal with them in practice, not just in theory.

I truly enjoyed it today, and hope the recording captures the spirit well enough Open / Comment

2021-04-27 23:21:42 I'm experiencing a rare déjà vu.

As in the dev part of my career is, again, slowly expanding, from encompassing just the realm of C++ before, to now building JavaScript wrappers over it, enabling more and more people access the sacred performance of The Language.

It’s almost like my Java/JNI stint 2.5 years ago, but a lot better actually. Better because JavaScript is in fact a relatively good language to wrap C++ into, at least once the initial blockers are behind.

If all goes well, I’ll be generating (DSL, *.inl) C++ as part of the build step some time in the next few weeks, after which point shipping C++ code as npm modules, bundled with their TypeScript interfaces, may well become my second C++ nature, as long as the tasks I have to work on these days allow us to explore this direction.

Links: experiments, and my clean repo with example usage.

Fun times. Open / Comment

2021-04-13 20:03:06 This important design paradigm has reached me twelve days too late: https://github.com/zhuowei/nft_ptr

Also, copy-pasting and paraphrasing from a private group: The history of C++ repeats itself, the first time as tragedy, the second time as farce, the third as blockchain. Open / Comment

2021-04-11 09:06:27 A system design meetup episode on MapReduce: video, slides. Thanks folks!

And sorry my OBS Studio didn't record your questions this time — good thing I have a habit of repeating them from offline conferences :-) also, I should probably not forget to hide the taskbar next time.

#incrementalimprovements #practicemakesperfect #thanksforhangingalong Open / Comment

2021-03-17 10:23:53 Дима Королёв (@BoreMeNo) - архитектор программного обеспечения в Poker Stars, преподаватель, основатель Systems Design Meetup. Кроме этого он работал программистом в Google, Microsoft и многих других компаниях.

В этом интервью мы поговорим о собеседованиях по алгоритмам, systems design и о том, как можно развивать карьеру программисту.



Open / Comment

2021-03-17 10:23:53 Sorry in advance for Russian, promise to keep this rare — интервью, которые мы с Тилеком Мамутовым (Outtalent.com) записали в Ололо в Бишкеке. Спасибо, было офигенно, и ты отличный интервьюер! Open / Comment