Twitter API Trainwreck (worst disaster ever) @funfunfunction
Twitter API Trainwreck (worst disaster ever) @funfunfunction
Uploaded October 2018 | Updated September 2026, 2 weeks ago
Sponsored by: Brilliant, thanks! Be one of the first 200 people to sign up with this link and get 20% off your annual subscription with Brilliant.org!
brilliant.org/funfunfunction

🔗 Fun Fun Forum topic for this episode (Patrons only)
funfunforum.com/t/twitter-api-trainwreck-worst-disaster-ever/5832

🔗 mpj on Twitter
twitter.com/mpjme

🔗 Help translate the show to your language
youtube.com/timedtext_cs_panel?tab=2&c=UCO1cgjhGzsSYb1rsB4bFe4Q

Painful pair programming session where we attempt to use the Twitter API - big mistake.
Twitter API Trainwreck (worst disaster ever)Taking over DevTipsMind Control with JavaScript - Charlie Gerard - Developer DiscussionsWhat task would make today great?Zeit Serverless Docker, node.js backend and variables NOT ALLOWEDClass keyword - Object Creation in JavaScript P7 - Fun Fun FunctionTDD with Wallaby.js Part 2Fun Fun Function Returns: Dawn of the Data Developer (and funfun.email)Huge announcement - Going full time YouTuber - Fun Fun FunctionHow long did it take to build Fun Fun Function - Twitch stream highlightLets code with function composition - Fun Fun FunctionHow long to onboard a new developer? (Isa Silveira)
Fun Fun Function |

Twitter API Trainwreck (worst disaster ever)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER