yoshuawuyts / knowledge Goto Github PK

View Code? Open in Web Editor NEW

843.0 47.0 46.0 4.03 MB

notes on things

knowledge's Introduction

notes

notes on things

License

MIT

knowledge's People

Contributors

Stargazers

Watchers

Forkers

broklyngagah franklinjavier hkjels bendrucker faizalpribadi andcollectiom supertong jacob-meacham iamnawa rahul-sindhu tomazin unrepentant-atheist itproto edgar-maciel datafordevelopment sotayamashita isao bluespore clemente abinxzh theatlasroom vijo jd-h ionnlab richardlitt plzthx corderophilosophy barbagrigia daukantas bcomnes dynamicmetaflow cbforks stigi nicknaso ethanfrom ippy04 mikalcallahan chioukhlyes pierd scatko tomkingdom binhapp fxfactorial mariuszmichalowski

knowledge's Issues

algorithms

http://bost.ocks.org/mike/algorithms/
http://machinelearningmastery.com/a-tour-of-machine-learning-algorithms/

documentation

Should dump some stuff about man pages.

    1      User Commands
    2      System Calls
    3      C Library Functions
    4      Devices and Special Files
    5      File Formats and Conventions
    6      Games et. Al.
    7      Miscellanea
    8      System Administration tools and Deamons

client side rendering

http://www.onebigfluke.com/2015/01/experimentally-verified-why-client-side.html?m=1

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/template

Can you please describe how someone else can set this exact setup up?

I wish to do something similar (or nearly exact) as I quite like the way you can search through the knowledge base and the layout.

However I am struggling in setting it up. I set up a GitBook account and made the wiki page but it fails to render like yours does.

Thank you for any help.

github scripts

is:pr author:yoshuawuyts is:closed user:wercker

queues

http://ferd.ca/queues-don-t-fix-overload.html

golang

http://dave.cheney.net/2014/12/01/five-suggestions-for-setting-up-a-go-project

bash

file testing

Bash File Testing
-b filename - Block special file
-c filename - Special character file
-d directoryname - Check for directory existence
-e filename - Check for file existence
-f filename - Check for regular file existence not a directory
-G filename - Check if file exists and is owned by effective group ID.
-g filename - true if file exists and is set-group-id.
-k filename - Sticky bit
-L filename - Symbolic link
-O filename - True if file exists and is owned by the effective user id.
-r filename - Check if file is a readable
-S filename - Check if file is socket
-s filename - Check if file is nonzero size
-u filename - Check if file set-user-id bit is set
-w filename - Check if file is writable
-x filename - Check if file is executable

source: http://stackoverflow.com/a/21164441

Why not using a wiki instead ?

GitHub wikis are Git repos too, with a nicer interface.

vacation

ueeeeeh, investigate what's up in the town you're heading to? Also pick a date before picking a location? Idk, need more of this haha.

stream utils

https://twitter.com/maxogden/status/497472710155722752

Flat file hierarchy

Cause ordening is dumb. Let it be free as in flowers and wildlife.

http status codes

100 "continue"
101 "switching protocols"
102 "processing"
200 "ok"
201 "created"
202 "accepted"
203 "non-authoritative information"
204 "no content"
205 "reset content"
206 "partial content"
207 "multi-status"
300 "multiple choices"
301 "moved permanently"
302 "moved temporarily"
303 "see other"
304 "not modified"
305 "use proxy"
307 "temporary redirect"
400 "bad request"
401 "unauthorized"
402 "payment required"
403 "forbidden"
404 "not found"
405 "method not allowed"
406 "not acceptable"
407 "proxy authentication required"
408 "request time-out"
409 "conflict"
410 "gone"
411 "length required"
412 "precondition failed"
413 "request entity too large"
414 "request-uri too large"
415 "unsupported media type"
416 "requested range not satisfiable"
417 "expectation failed"
418 "i'm a teapot"
422 "unprocessable entity"
423 "locked"
424 "failed dependency"
425 "unordered collection"
426 "upgrade required"
428 "precondition required"
429 "too many requests"
431 "request header fields too large"
500 "internal server error"
501 "not implemented"
502 "bad gateway"
503 "service unavailable"
504 "gateway time-out"
505 "http version not supported"
506 "variant also negotiates"
507 "insufficient storage"
509 "bandwidth limit exceeded"
510 "not extended"
511 "network authentication required"

rest

GET     /users             ->  index
GET     /users/new         ->  new
POST    /users             ->  create
GET     /users/:user       ->  show
GET     /users/:user/edit  ->  edit
PUT     /users/:user       ->  update
DELETE  /users/:user       ->  destroy

css underline

http://www.acusti.ca/blog/2014/11/28/towards-a-more-perfect-link-underline/

food

need to write some stuff down about health / body stuff. No idea what to call it. Want to put in my late grammy's recipes, though not sure how healthy they are.

Please consider contributing to nodejs/docs

Hey @yoshuawuyts, I really enjoy this repository as it has all kinds of useful tidbits in it 👍

The browserify and streams references are very well written. Have you considered contributing them to nodejs/docs?

@Qard or @chrisdickinson any thoughts?

personal dir structure

or how to digitalize your life. Similar to the filesystem hierarchy standard

Etc/              other
Lib/              resources that can be consumed
Log/              scanned materials, sorted by date
Media/            media
  Read/           books, articles and the like
  Cam/            img from camera
  Pub/            public images to share
  Screen/         screenshots
  Tmp/            images that don't belong in any of the above
  Vid/            movies, gifs
Src/              source code
Usr/              personal files, sorted by topics

document pass / pgp setup & usage

a bit, I guess?

unix commands

tail        with `-f` you can follow new changes on a file, useful for logs
pbcopy      pipe into your clipboard
pbpaste     pipe from your clipboard
time        check out how long a command took to run

bash

exec 2>&1

pipe stderr to stdout, useful for writing all data to a file for example.
http://stackoverflow.com/questions/1216922/sh-command-exec-21

json-schema

Create a dedicated overview page - http://spacetelescope.github.io/understanding-json-schema/

Is packages.md auto generated for you?

This page.

I am curious if it is, and if yes how you did it?

git

git branch --merged | grep -v "\*" | xargs -n 1 git branch -d

from: http://stackoverflow.com/questions/6127328/how-can-i-delete-all-git-branches-which-have-been-merged

morning ritual

http://love-aesthetics.nl/morning-ritual/

hey yosh :-)
I really enjoyed all the useful stuff you collected and bookmarked a lot of things.
I did not check things in a long time, but today went through quite a few of my older bookmarks to clean things up and figured that a lot of your links are dead.

It seems you either moved or removed a lot of helpful content.
I guess I can still find it checking previous commit, but I wonder about the reason.

Error in wasm notes

https://github.com/yoshuawuyts/knowledge/blob/master/computers/2018-05-31-wasm-notes.md says this:

Libuv is not ABI stable - that's probably a thing to look at stabilizing.

I don't know if that's a direct quote or a transcription error but it's wrong: libuv is ABI-stable.

//...
window.addEventListener( 'scroll', function()
{
    //...
    if( wScrollCurrent <= 0 ) // scrolled to the very top; element sticks to the top
        element.style.top = '0px';

    else if( wScrollDiff > 0 ) // scrolled up; element slides in
        element.style.top = ( elTop > 0 ? 0 : elTop ) + 'px';

    else if( wScrollDiff < 0 ) // scrolled down
    {
        if( wScrollCurrent + wHeight >= dHeight - elHeight )  // scrolled to the very bottom; element slides in
            element.style.top = ( ( elTop = wScrollCurrent + wHeight - dHeight ) < 0 ? elTop : 0 ) + 'px';

        else // scrolled down; element slides out
            element.style.top = ( Math.abs( elTop ) > elHeight ? -elHeight : elTop ) + 'px';
    }
    //...
});
//...

sauce

api

https://stripe.com/docs/api#errors

{
  message: 'clear description of whats going on with the API, and how to solve it',
  type: <type>,
  code: <code>
}

http codes

200 OK - Everything worked as expected.
400 Bad Request - Often missing a required parameter.
401 Unauthorized - No valid API key provided.
402 Request Failed - Parameters were valid but request failed.
404 Not Found - The requested item doesn't exist.
500, 502, 503, 504 Server errors - something went wrong on Stripe's end.

types


invalid_request_error   Invalid request errors arise when your request has invalid parameters.
api_error   API errors cover any other type of problem (e.g. a temporary problem with Stripe's servers) and should turn up only very infrequently.
card_error  Card errors are the most common type of error you should expect to handle. They result when the user enters a card that can't be charged for some reason.

Codes

incorrect_number    The card number is incorrect.
invalid_number  The card number is not a valid credit card number.
invalid_expiry_month    The card's expiration month is invalid.
invalid_expiry_year The card's expiration year is invalid.
invalid_cvc The card's security code is invalid.
expired_card    The card has expired.
incorrect_cvc   The card's security code is incorrect.
incorrect_zip   The card's zip code failed validation.
card_declined   The card was declined.
missing There is no card on a customer that is being charged.
processing_error    An error occurred while processing the card.
rate_limit  An error occurred due to requests hitting the API too quickly. Please let us know if you're consistently running into this error.