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

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 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

Source: https://carolynvanslyck.com/blog/2020/12/git-wip/

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

1. Очаровательный кишечник. Джулия Эндерс
2. Нейрофитнес Рахул Джандиал
3. Сахар, соль и жир. Майкл Мосс
4. Блог Бесчастнова Павла aka Stelazin

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)

• Advent of Code 2020
• EmacsConf 2020 videos
• reClojure 2020 day 1 video
• reClojure 2020 day 2 video

Just read this article from magit author about integration. https://emacsair.me/2018/12/19/forge-0.1/

Since now you can enjoy making PRs and MRs right from your lovely editor!

Simplicity is an underappreciated property.

In order to dynamically edit content people tend to introduce a lot of complexity by using powerful CMS systems, databases, search engines etc. Moreover, you’ll need to spend significant efforts on maintenance, high availability, for all this stuff.

What if you can just use Markdown and provide a short training course to people? What if you can use Hugo and Github Actions pipelines or similar for publishing?

Literally everything becomes more simple, thus more robust. What power can you gain by using simple text based format like this? Countless amount of tools for editing, processing and automation. Think about this.

This week I’ve saved the following links:

• https://www.javaadvent.com/2019/12/smalltalk-with-the-graalvm.html
• https://github.com/razum2um/google-translate-anki
• https://funretro.io - making sprint retrospectives

I’m always happy to gain a new knowledge, so this time I was putting efforts into Pharo programming course and voila, enjoyed it challenges and got a Certificate of accomplishment.