sranso

what is flexbox

• The CSS Flexible Box Layout Model, or "flexbox"
• one of the specifications in CSS3
• defining aspect of the flex layout -- the ability to alter its items' width and/or height to best fill the available space on any display device
  • expands items to fill available free space, or shrinks them to prevent overflow
• elements behave predictably when the page layout must accommodate different screen sizes and different display devices
• considered (in some cases) an improvement over the block model in that it does not use floats, nor do the flex container's margins collapse with the margins of its contents
• display order of the elements is independent of their order in the source code
  • intentionally only affects the visual rendering, leaving speech/navigation based on the source order
• for example

sranso

Designing a Beautiful REST+JSON API

Les Hazlewood (Stormpath)

• fundameantally two types of resources
  • collection resource
    • e.g. /applications
  • instance resource
    • e.g. /applications/a1b2c3
• behavior
  • get = read
• put = can be used for create/update scenarios

sranso

used

• promise as a layout for the talk (we'll do this then this then this if that fails etc)
• why would we use promises (in js and the real world -- highlighting the real world, why even bother with promises)
• "bloopers" -- ideas i had for making this funny that "didn't make the cut"
  • a promise state is like one of these things
    • pending -- outcome tbd (playing hard to get)
    • fulfilled -- completed, and the promise has a value (worth something)
    • rejected -- failed, has a reason why it failed (excuses excuses)
    • settled -- has fulfilled/rejected (you know how you feel)
• diff libs as men i have dated and how they are different. or dates i have been on?

sranso

write it out

my name's sarah

• work at venmo on web team for almost a year
• been an engineer a little longer than that (flatiron school)

i essentially learned js at venmo

• applause, ooh-ing and ah-ing
• lots of things made sense/i could pick up w/ relative ease -- iterating over data, ajax calls -- but others were tougher

sranso

#promises talk for queensjs 4/11/15

• es6 article
• es7 article
• mdn

why do we use them

• js is single threaded
  • you can add listeners to events, but what if the event happens before you start listening for it?
• handling errors becomes really difficult in other async options

sranso

notes of things i learn while watching destroy all software

##das-0001-statistics-over-git-repositories

• git rev-list HEAD -- takes the ref (in this case HEAD) and crawling backwards. so the most recent commit will appear first
  • to reverse (have most recent be first) git rev-list --reverse HEAD oldest -> newest
• xargs
  • takes multiline output and joins them with a space
  • e.g.

$ echo '1

sranso

have a generic placeholder, something like "Securely fetching data 🔒 ..." and a spinner.

you can base 64 encode our spinner and include it right on the page so it gets sent with the initial payload.

you could put style tags in the body too so the styles only exist before onReady

###base64

sranso

##production-ready node architecture

signs of a successful Node app:

it's made of several small processes that start instantly, maintain no state, and communicate via a language-agnostic message bus. each process logs to stdout and responds to unrecoverable errors by exiting immediately. a load-balancer queues requests, which are served in fixed time by scaling service levels. configuration controls behavior without any need to deploy new code. each deploy is archived into a perfect binary copy.

• sm pr -- sm mem footprint, light, not lots of blocking cpu ops
• st inst -- gives level of fault tolerance
• no st -- if process dies, state dies with it
• ex im -- just exit and start over when you have a prob

sranso

#what is an event loop? this vid

• JS
  • heap - where mem allocation happens
  • call stack (in chrome it's essentialy v8) - where stack frames are
    • --> look to...
• web apis - extra things the browser provides
  • dom
  • ajax
• setTimeout

sranso

#cookies nom nom reading this and this and other stuff

###why use cookies

• HTTP is stateless which means it has no way to keep track of user's previos activities. so cookies help create state

##diff kinds of cookies

• session
• persistent
• secure