Linkedin, what are you doing? Stop it!
Recently I’ve checked this website and styling became really aweful. After my digging it turned out one little busty thing was doing the crap.
Official Linkedin badge! Overrides default link styling!
<script type='text/javascript' src='https://platform.linkedin.com/badges/js/profile.js' async defer ></script>
The easiest way to turn it off is to change type=‘text/javascript’ to just ’text’.
You have also been decreasing my lighthouse score. Bye-bye little nasty thing.
On Datomic dark sides
I love datomic. Datalog is a definitely something noteworthy and even if you never going to use it in your projects, still it is worth getting your hands dirty. Despite all Datomic bright sides, there are some thoughts bothering me since I started using it more extensively in my pet project.
Smalltalk and its descedants
The Smalltalk is an extraordinary language. Firstly, this is a mother of all OOP family languages. Secondly, Java was invented as alternative for payed (sic!) programming language Smalltalk, and if IBM won the race with Microsoft a that time, things might end up very differently and Smalltalk could still be a hype.
Initially I’ve been exposed to Ruby, but only with Smalltalk I finally grasp lot’s of ideas in Ruby, so as the roots of the syntax.
org-roam ideas
I love talking about ideas. org-roam has quite simple idea for organizing your knowledge. I didn’t believe it works when I gave it a try.
The essense of the Zettelkasten method is following:
- Keep your notes split apart in one single folder.
- Insert tags and backlinks to group notes together.
That’s it!
What is so special about this? Let’s say I started moving all things from my backlog pile into separate small notes and I started to breath again! You know you probably have this cemetry of links you will never open and articles you will never read. I have such pile as well, links in browser in “favorites”, pile of links in org backlog file.
Disable Chrome browser confirmation to open external protocol with org-protocol
I recently added org-capture chrome extension to my toolbelt. Unfortunalely chrome annoys me by asking if I want to open this protocol link every time.
Here is the simple way to fix this.
Execute this in the shell
defaults write com.google.Chrome URLAllowlist -array-add -string 'org-protocol://*'
check chrome://policy url that it contains proper settings for org-protocol

Emacs literate programming and SQL
I’m really crying of how finally emacs can be used for the literate programming and for some testing.
For restclient, this creates POST request with json data structure in request body.
#+begin_src restclient
POST http://muster.test/index.php?cl=ping
Content-Type: application/json
{
"essentialtech": true,
"googleadwords": false,
"googleanalytics": false,
"googlemaps": true,
"gtmbasedtech": false,
"terminland": true,
"userlike": true
}
#+end_src
#+RESULTS:
#+BEGIN_SRC js
{
"message": "success"
}
// POST http://muster.test/index.php?cl=ping
// HTTP/1.1 200 OK
// Date: Tue, 09 Feb 2021 13:45:07 GMT
// Server: Apache/2.4.46 (Unix) OpenSSL/1.1.1i
// X-Powered-By: PHP/7.1.33
// Expires: Thu, 19 Nov 1981 08:52:00 GMT
// Cache-Control: no-store, no-cache, must-revalidate
// Pragma: no-cache
// Set-Cookie: language=0; path=/; HttpOnly
// Set-Cookie: sid=0fvjai2h5h2pso52p4vq9e5309; path=/; HttpOnly
// Keep-Alive: timeout=5, max=100
// Connection: Keep-Alive
// Transfer-Encoding: chunked
// Content-Type: application/json;
// Request duration: 0.269261s
#+END_SRC
useful git wip
Useful Git WIP alias command
add this to the .gitconfig
[alias]
wip = for-each-ref --sort='authordate:iso8601' --format=' %(color:green)%(authordate:relative)%09%(color:white)%(refname:short)' refs/heads
and enjoy git wip sorting branches by most recent
Книги о здоровье
Вот небольшой список книг и ресурсов, которые настоятельно рекомендую для погружения в обширную тему здоровья.
- Очаровательный кишечник. Джулия Эндерс
- Нейрофитнес Рахул Джандиал
- Сахар, соль и жир. Майкл Мосс
- Блог Бесчастнова Павла aka Stelazin
Gitlab limit parallel pipeline execution
In brief - use the resource_group directive.
Example:
stages:
- build
jobA:
resource_group: jobA
stage: build
script:
- echo HelloA
jobB:
stage: build
script:
- echo HelloB
There are some useful patterns for Resource Group.
resource_group: $CI_ENVIRONMENT_NAME … Limit per environment
resource_group: $CI_JOB_NAME … Limit per job
resource_group: $CI_COMMIT_REF_NAME:$CI_JOB_NAME … Limit per job per branch
resource_group: $CI_COMMIT_REF_NAME:$CI_ENVIRONMENT_NAME … Limit per environment per branch (e.g. review apps)