@psd *Dripping* with sweet, delicious irony.
Phil Hawksworth
@philhawksworth •
Wait... when did @SlexAxton change his name to @gavinjames and record this?
@Ben_Phillips Nope. Except in the Thunderdome.
@esh Thanks for sharing, Eric. I'd be interested in hearing about your Lambda development workflow. I'm a huge Lambda fan, but have found the workflow a little tricky. Any hot tips?
Phil Hawksworth
@philhawksworth •
Tonight's experiment care of those lovely people at #hophooligans. Really rather good. http://ift.tt/2kWlNcn
Phil Hawksworth
@philhawksworth •
Never has the jiggley aha-theres-my-mouse-pointer feature been more appropriately expressive. https://twitter.com/rafahari/status/943907045832581120
@charis hhhHappy Old Yearrrrr!
@Netlify I'll say!
This talk evolved a bit over the years. One of the more recent versions was given at @fronttrends last year and they were nice enough to video it:
https://youtu.be/_cuZcnJIjls
This talk evolved a bit over the years. One of the more recent versions was given at @fronttrends last year and they were nice enough to video it:
https://youtu.be/_cuZcnJIjls
@budparr @robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud A very good list.
@chriscoyier Love that response.
I often suspect that people expect CSS to be easy, and when it requires some effort, they get frustrated.
That's not the same as it being bad.
I often suspect that people expect CSS to be easy, and when it requires some effort, they get frustrated.
That's not the same as it being bad.
@budparr @robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud This is great! Reminds me very much of the drum I was banging around the same time!
https://speakerdeck.com/philhawksworth/dynamic-static-site-strategies
https://speakerdeck.com/philhawksworth/dynamic-static-site-strategies
@robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud Excellent!
Phil Hawksworth
@philhawksworth •
After 10 years of reading @24ways, I'm rather happy to have now written for them.
On deployment:
1. Make it scripted
2. Make it automated
3. Make it real
4. Make it first
https://twitter.com/24ways/status/943632412302565376
On deployment:
1. Make it scripted
2. Make it automated
3. Make it real
4. Make it first
https://twitter.com/24ways/status/943632412302565376
Phil Hawksworth
@philhawksworth •
RT @24ways: Day 21: Knowing the Future - Tips for a Happy Launch Day by Phil Hawksworth @philhawksworth https://buff.ly/2oVDf6g
@HenrikJoreteg @Netlify Hmm. That's odd. The team will be keen to figure out what was going on there! Glad to hear that your deployed site was not effected. If you were to share the site name/url you were working on, we could investigate a little more (perhaps DM it to me, or chat with support whenever)
@m1sp Ah that's likely. I believe though that if the assets don't change, subsequent deploys should be fast as atomic changes are pushed rather than repeatedly pushing identical assets.
@HenrikJoreteg @Netlify Hey Henrik! Long time no see!
I'm not aware of any issues on platform at the moment. Have builds been succeding ok previously? Builds that include scripts which run and run should eventually time out. (15mins I think)
The support team will have better visibility which may help
I'm not aware of any issues on platform at the moment. Have builds been succeding ok previously? Builds that include scripts which run and run should eventually time out. (15mins I think)
The support team will have better visibility which may help
@robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud That's a nice benefit of a #JAMstack site... you can host it most anywhere. I like avoid getting locked in due to technology choices.