
Sam Richard
@Snugug
BBQ lead, ChromeOS DevRel. Mostly food, sometimes design and development, especially for the web. 7008px tall. He/him.
An archive of my Twitter timeline up until I moved to Mastodon. You can find me there at @[email protected]
-
@HackyGoLucky that’s fabulous. Simply marvelous.
-
@HackyGoLucky /giphy slow clap
-
@HackyGoLucky oh wow. I fly @united and have only had that happen once or twice.
-
@HackyGoLucky are you delayed before boarding?
-
@HackyGoLucky @JetBlue long delays? I’m sure I’m delayed more than I feel it but usually not enough to complain.
-
@HackyGoLucky haha the other side of the world!
-
@HackyGoLucky boo! How long and often do you? Who do you fly?
-
@HackyGoLucky I’m in the UK, was gonna say the same about you!
-
@HackyGoLucky for me if there are delays they’re small enough to be eaten while sitting in the plane, ~<20min
-
RT @auchenberg: Net Emoji Score™
-
RT @KuraFire: Include accessibility notes in your documentation! (I cannot stress this one enough. RT everywhere) — @cordeliadillon #clarit…
-
Look what we found at @IBM Hursley! #IBMHackademy
-
RT @stack72: Every time I give a DevOps / CD talk, @davemangot and @cread make their way into it :)
-
RT @KuraFire: What matters is that your whole team knows it, uses it, and understands the ‘why’ behind each part of it. @MiriSuzanne #clari…
-
RT @KuraFire: Make your naming conventions consistent across all teams: design, front-end and back-end. @MiriSuzanne #clarity2016
-
RT @KuraFire: “These elements share a purpose” focuses on UI semantically: the purpose, meaning & use case behind them. @MiriSuzanne #clari…
-
RT @KuraFire: Don’t Repeat Yourself, but also: Don’t Stretch For Patterns. “These elements share a border style” is too fragile. @mirisuzan…
-
RT @ThePracticalDev: The only correct way to write JavaScript is whatever you were not doing last week.
-
@itsmisscs @jensimmons bah! Waitlisted! Can I sneak in anyway?
-
RT @itsmisscs: Ooooooooooo zeldman/714929143280832512
-
@itsmisscs @MiriSuzanne agreed. Nunjucks ++
-
RT @rauchg: This is the right way to handle dependency updates with
npm
(surprise-free) github.com/dylang/npm-check