This document is
an effort to get people up to speed where they feel confident about react and javascript
I am putting together an organized list of what I grab for when solving various problems.
"what I know cold", and these are just the things that currently come to mind it can be updated later.
There are also "warm items", that I know to google and reach for when encountering a situation
an example of that would be an IIFE - immediately invoked function expression.
Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources (e.g. fonts) on a web page to be requested from another domain outside the domain from which the first resource was served. This is set on the server-side and there is nothing you can do from the client-side to change that setting, that is up to the server/API. There are some ways to get around it tho.
Sources : MDN - HTTP Access Control | Wiki - CORS
CORS is set server-side by supplying each request with additional headers which allow requests to be requested outside of the own domain, for example to your localhost. This is primarily set by the header:
Access-Control-Allow-Origin
| __find_open_command_from_Operating_System() { | |
| local open_cmd | |
| OSTYPE="$(uname -s | tr 'A-Z' 'a-z')" | |
| case "$OSTYPE" in | |
| darwin*) open_cmd='open' ;; | |
| cygwin*) open_cmd='cygstart' ;; | |
| linux*) [[ "$(uname -r)" != *icrosoft* ]] && open_cmd='nohup xdg-open' || { | |
| open_cmd='cmd.exe /c start ""' | |
| } ;; |
| #!/bin/bash | |
| # This code allows for pagination, 4 comments below say: "remove me to turn off pagination" | |
| { | |
| paginationCursor=1; # remove me to turn off pagination | |
| paginationScalar=5; # remove me to turn off pagination | |
| baseURL="https://localhost"; | |
| listOfRoutes=$( | |
| rails routes | | |
| grep GET | |
| # Basic usage: Tell iex to write all history to | |
| # rlwrap -a iex # --always-readline | |
| # Full working script: | |
| # Increment the file name with the session pattern. based on what files currently exist: | |
| rlwrapVersion=$(ls $HOME/.$filePrefix* | wc -l | awk '{print 0$1 + 1}'); | |
| # This is the path we will be writing to: | |
| rlwrapTempPath="$HOME"/."$filePrefix"_"$rlwrapVersion"_history; |
Elixir
(note: you could skip a step here by just having a list of keys.)
Starting place: https://devdecks.io/2022-remove-multiple-key-value-pairs-from-map/
map = %{k1: :v1, k2: :v2, k3: :v3}
3 contraversial things that I believe
Programs/applications can be completed and stand on their own: (Accomplish a feature set that a customer finds value in and do not allow scope creep outside of that feature set. This is crucial to be able to build software without handcuffing yourself with legacy code. If your career was an endless list of technical debt it would only ever increase and you would constantly be disappointing by dropping support throughout your career. This does happen but we should design our software especially open source software so that it can stand on its own.)
Tasks can be impossible (You can have a dependency that says you cant have that thing and does not give you access)
Something can be explored completely: (Something can be deemed logically complete by exploring all options available, or proving that the task is not solvable. I watched a video once that mentioned humans are unique in being able to prove things are not solvable instead of solving them which is often d