| export default function createCrudHooks({ | |
| baseKey, | |
| indexFn, | |
| singleFn, | |
| createFn, | |
| updateFn, | |
| deleteFn, | |
| }) { | |
| const useIndex = (config) => useQuery([baseKey], indexFn, config) | |
| const useSingle = (id, config) => |
In this gist we are going to learn about basic goodies that we get from the library lodash/fp (fp stands for functional programming, great for ensuring immutability).We'll learn just by doing (step by step guided sample + codepens).
We'll cover lodash set and flow functions
| ssh-keygen | |
| -t ed25519 - for greatest security (bits are a fixed size and -b flag will be ignored) | |
| -t rsa - for greatest portability (key needs to be greater than 4096 bits) | |
| -t ecdsa - faster than RSA or DSA (bits can only be 256, 284, or 521) | |
| -t dsa - DEEMED INSECURE - DSA limted to 1024 bit key as specified by FIPS 186-2, No longer allowed by default in OpenSSH 7.0+ | |
| -t rsa1 - DEEMED INSECURE - has weaknesses and shouldn't be used (used in protocol 1) | |
| -b 4096 bit size | |
| -a 500 rounds (should be no smaller than 64, result in slower passphrase verification and increased resistance to brute-force password cracking) | |
| -C "[email protected]" comment.. |
| // this is a big array of 76 items I need to split into groups of 10 | |
| const hugeArray = Array.from({ length: 76 }, (_, i) => i); | |
| function chunkify(array, chunkSize = 10) { | |
| // make a new array | |
| const chunks = Array.from( | |
| // give it however many slots are needed - in our case 8 | |
| // 1-7 with 10 items, and 8th slot will have 6 | |
| { length: Math.ceil(array.length / chunkSize) }, | |
| // this is a map function that will fill up our slots |
| """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" | |
| " Font | |
| :set guifont=Source\ Code\ Pro:h14 | |
| """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" | |
| " Hide pointless junk at the bottom, doesn't work in .vimrc for some reason? | |
| :set laststatus=0 | |
| :set noshowmode "don't show --INSERT-- | |
| :set noruler "don't show line numbers/column/% junk |
this essay has been updated on my personal site, together with a followup on how to get started
If there's a golden rule, it's this one, so I put it first. All the other rules are more or less elaborations of this rule #1.
You already know that you will never be done learning. But most people "learn in private", and lurk. They consume content without creating any themselves. Again, that's fine, but we're here to talk about being in the top quintile. What you do here is to have a habit of creating learning exhaust. Write blogs and tutorials and cheatsheets. Speak at meetups and conferences. Ask and answer things on Stackoverflow or Reddit. (Avoid the walled gardens like Slack and Discourse, they're not public). Make Youtube videos or Twitch streams. Start a newsletter. Draw cartoons (people loooove cartoons!). Whatever your thing is, make the thing you wish you had found when you were learni
| // Usage of the useHover hook | |
| import React from 'react'; | |
| function Component() { | |
| const [hovering, attrs] = useHover(); | |
| return ( | |
| <React.Fragment> |
This week NN Group released a video by Jakob Nielson in which he attempts to help designers deal with the problem of customers being resistant to their new site/product redesign. The argument goes thusly:
There's slightly more to it than that, he caveats his argument with requiring you to have of course followed their best practices on product design, and allows for a period of customers being able to elect to continue to use the old site, although he says this is obviously only a temporary solution as you don't want to support both.
| /** | |
| * detect safari | |
| * | |
| */ | |
| detectSafari = () => | |
| /^((?!chrome|android).)*safari/i.test(navigator.userAgent); |