With the request variables feature from Kulala you can now access the access_token and use it in the next requests. GET {{apiURL}}/items HTTP/1.1Accept: application/jsonAuthorization: Bearer {{login.response.body.$.access_token}}
In Authorization header {{login.---}} login is a name of the login handler. It's defined by ### login above.
the model can inspect existing elisp, propose changes, and iterate directly inside the document. It turns into an interesting and (dare I say it) fun form of agentic, REPL-driven co-development
Making ai agent "mold" your environment for the task by creating supporting mappings, configurations and plugins. Something like: "Create an optimal marks and window layout for this project"
it’s fast, declarative, has locking, can handle compiled dependencies and can manage virtual environments
Can handle PyPI dependencies because of changes in PyPI, not because it provides these features
ansible.builtin.set_fact: one_fact: something other_fact: "{{ local_var * 2 }}" cacheable: yes
Directive set_fact is very useful for decomposing your tasks and sending proper input to them thus using handlers like functions with dynamic parameters. You can just register result of the set fact into reg-variable and then notify handler. It will be available at the handler like "{{ reg-variable.ansible_facts.one_fact }}".
This "register-notify" construct works for any task but not every task returns the output you wish to see at handlers.
Grouping tasks with blocks
You can also add vars: for the block: these vars will be available for all tasks of the block. But you can't add the same listen to all tasks at the block level: you'll have to add it on a per-task basis.
Step 2: Create a Looped Task with with_items#
In recent versions loop is more preferred than with_items but the idea is the same: you can use handlers via notify to trigger multiple actions per item in the loop. You just need to place same listen value to all needed handlers to run them all. These handlers can be even decomposed into different files if you want. Just include them in the main file to actually register them.
To watch a file, its parent directory must be watched in order to receive change events for all the directory's children, recursively at any depth.
May be an issue for us as we want to only watch for high-level items in a directory. Watching recursively is: 1. potential performance hit 2. unnecessary items in a database (storage hit)
private
Not personalized (without cookies)
A mode called ‘ansible-pull’ can also invert the system and have systems ‘phone home’ with scheduled Git checkouts to pull configuration directives from a central repository.
Can be used to create a more dynamic system of configs
Go to from Here…: enter/paste a location to jump to Ctrl + Shift + G
Prepopulates input with current path
nix flake lock --update-input mysecrets
Good practice but before it file should be added as flake input.
Using Hashed Passwords for Declared User Credentials
Using both hashing and encryption for better security.
Right hand
It's easy to remember notations if we base on right hand. it's either obvious translation for us or just "m.d". Left hand in all languages is different.
The 'major' alteration is usually superfluous, as a key description missing an alteration is invariably assumed to be major.
Cmaj and Cmin become C and Cm.
Emulate devices
As a local alternative to BrowserStack?
import pandas_profiling
Package for generating profile report for pandas. Allows see overview for data.
What is it about you that they love? Can you do more of that? Where can you find more people who love that sort of thing?
Very insightful questions that help discover weak / strong parts of your business and directions in which you should develop it.
10,000
Isn't it, like, huge?
gitfs is useful in places where you want to keep track of all your files, but at the same time you don't have the possibility of organizing everything into commits yourself
May be useful for kbn
old-branches
As a complementary util to delete-merged.
Melting datasets¶
Allows concat multiple columns into single column. Something like a join for each value in each column by is unique cell id.
NpmNix includes a very simple Golang parser, parser.go (~70 lines of code), that parses the package-lock.json and generates the complete Nix expression.
Gist of dynamic nature of this feature
task config journal.info off
You can also change it temporarily for command
It is heuristically known that content which has not been updated for a full year will not be updated for some time after that. Therefore, the client stores this response (despite the lack of max-age) and reuses it for a while. How long to reuse is up to the implementation, but the specification recommends about 10% (in this case 0.1 year) of the time after storing.
Browser has it's own heuristics for caching even if max-age is not set.
<# .SYNOPSIS Adds a file name extension to a supplied name. .DESCRIPTION Adds a file name extension to a supplied name. Takes any strings for the file name or extension. .PARAMETER Name Specifies the file name. .PARAMETER Extension Specifies the extension. "Txt" is the default. .INPUTS None. You can't pipe objects to Add-Extension. .OUTPUTS System.String. Add-Extension returns a string with the extension or file name. .EXAMPLE PS> Add-Extension -Name "File" File.txt .EXAMPLE PS> Add-Extension -Name "File" -Extension "doc" File.doc .EXAMPLE PS> Add-Extension "File" "doc" File.doc .LINK http://www.fabrikam.com/extension.html .LINK Set-Item #>
Notice that you have to enter a new line after keyword otherwise it won't work.
For instance:
.EXAMPLE
Add-Extension
But .EXAMPLE Add-Extension won't work. Only some keywords like PARAMETER expect something on the same line.
Get-Help -Name "Add-Extension" -Full
Get full description (including examples).
an excess of planning - really just another type of procrastination
Be careful when planning something to not fall into trap of procrastination (planning instead of doing something). Always measure if something worth planning: if the thing is 5 minutes to do - just do it. If there're a lot of such things and you're scared of loosing track of them - write them down but don't dive into planning them too much. Sometimes it's much easier to just outline what you want to do - and this list of things to accomplish will just come into mind.
cond = nil
Disable all plugins by default when using firenvim.
Formatting requests are tricky. But formatting is handled very well by conform.nvim also for injected code via their injected formatter (example from my config: link).
Formatting injected languges
should not store this response.
Good when you don't want to cache big documents.
Determining the return on investment (ROI) for AI initiatives is difficult: The savings may not be immediate, and some of the benefits, such as freeing up employee time to perform more value-added work, are indirect.
Estimation techniques play important role in long-time initiatives like AI.
Make sure everyone on the team understands that in the case of an acquisition, any emails and meeting notes will transfer to the new buyer.
Be considerate when writing mails to your colleagues. They may not be private even if the person you're writing to is very considerate of your feelings.
specific element in the document which is an ancestor of the element
So it doesn't work with elements in different stacking contexts (for example, rendered via react portals).
// const authors = _.map( // authorIds, // id => await authorModel.fetch(id));
Насколько помню, без использования lodash в обычном map такое сделать нельзя.
It's common to have logic directly in components, such as making an async request in a click handler or a useEffect hook and then processing the results.
Meaning we can get around without thunks: just use actions in .then and .catch, for example.
const dispatch = useDispatch()
Just react hook to get dispatch of the store to replicate the same functionality as in the first code snippet: call store.dispatch(…).
Snippets
Nice snippets but need to be converted to LuaSnip. Also some of them (such as code block) are better derived from markdown plugins aka mkdx. Some are even better implemented in a non-snippet plugins (images, tables)
differentiating the square of the TD error and see if you arrive at the same update (i.e. δ∇wV(S,w)).
Differentiating critic_loss from above gives us a delta w.
pushd ~/Documents/*/*/${1}*
Interesting minimalistic alternative to zoxide
People will come to hold a deeper mutual respect for each other.' --What a big fat lie. It amounts to nothing but loss, after all, for someone to perceive pain at times when they are not the one in pain themselves. Nor does it make pain go away from the person who is the source of such feelings...
Issue in comprehension of a problem: we don't have enough compassion bot because we don't understand people but because we don't hirt ourselves (including by understanding then)
May be very useful for faster writing. The only takeover I see is that it's hard to create a abbrevitaiton system that's fast and not clunky to use .
Another options is to add an additional URL to the origin: git remote set-url --add origin git@github.com:<USERNAME>/<PROJECTNAME>.git When you push to origin it will push to both the original origin (gitlab) and the one added above (github).
Painless way to maintain several remotes synced without Premium.
OCR for lectures
Nx may be good for personal monorepo projects where you want to have a full-stack app in one repo.
t’s been a running joke for a long time that we have more email groups than employees. But we’ve been careful to organize the groups, for example identifying different types by prefixes to their names (t- is a mailing list for a project team, d- a mailing list for a department, l- a more open mailing list, r- a mailing list for automated reports, q- a request list, etc.) And for me at least this makes it plausible to remember what the right list is for some mail I want to send out.
Use prefixes for chats and group them this way. You can have 3 or even more chats with the same name like 'shepherd' but with different prefixes. This helps naming things.
with time I couldn’t recall the conditions of the studies any longer and wasn’t confident in using those notes. Nowadays, I always write down what the actual study design was.
Always provide context to the note contents.