Can't code anything without vim key bindings or I can without them but I don't want to.
use only via terminal and I use below:
- neovim: https://www.neovim.io
- spacevim: https://spacevim.org
- TabNine: https://tabnine.com/install
Can't code anything without vim key bindings or I can without them but I don't want to.
use only via terminal and I use below:
| # in case you want to scrape 'https://my-url.com:9999/metrics?a=1&b=2' | |
| - job_name: your-job-name | |
| scheme: https | |
| static_configs: | |
| - targets: ['my-url.com:9999'] | |
| metrics_path: /metrics | |
| params: | |
| a: ['1'] | |
| b: ['2'] |
as of April, 2020
After reading this, https://www.javierchavarri.com/data-first-and-data-last-a-comparison/,
I thought I should use -> over |> for a performance reason.
by the way, the post was an excellent article 👍🏼
| /* After learning how to do testing for rxjs6 from here, https://medium.com/@kevinkreuzer/marble-testing-with-rxjs-testing-utils-3ae36ac3346a. | |
| * I'm saving/sharing this gist to remember and understand again quickly in the future. | |
| * I've altered some parts in the code to work with Jest and Javascript and CommonJS. | |
| * In the post originally it was for Typescript and ES modules and Other(?) testing framework. | |
| */ | |
| const { TestScheduler } = require("rxjs/testing"); | |
| const { Observable } = require("rxjs"); | |
| const { filter, map } = require("rxjs/operators"); |
watcher = currentUser() AND lastviewed >= startOfWeek(-1w) ORDER BY lastViewed DESC
I named this query, What I possibly worked on last week
The query actually searches for issues that I viewed so I still filter some manually but it's quite close to what I actually did because usually I mostly view what I work on not other issues that much.
This is about https://exercism.io/tracks/rust/exercises/triangle
Non generic solution wasn't so hard.
at least compare to the generic one that I tried to make afterawards
But I sturuggled quite a bit with making it a generic solution.
I wasn't super familiar with (Rust concepts of) generic nor lifetime.
First attempt was making the validate_triangle generic, which you can see it here
Let me be honest. I'm not a big fan of Python. Wait a minute, I know it's everywhere and it's loved by many people. It's just not for me though. It doesn't agree with me a lot. I just never cared too much of it. It simply wouldn't be my first choice of programming language.
However sometimes, I simply can't avoid using packages (thanks for all the people who worked on them thought!) and maintaining python code/projects.
So I decided to keep track of things that makes me confused many times (because I don't get to work with python not so often, too)
| // get every possible case from ranges | |
| const ranges = { | |
| a: [1, 2, 3], | |
| b: [4, 5], | |
| c: [6, 7, 8], | |
| }; | |
| console.log('ranges:'); | |
| console.log(ranges); |