Twitter API Trainwreck (worst disaster ever)
Вставка
- Опубліковано 3 жов 2024
- 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/...
🔗 Fun Fun Forum topic for this episode (Patrons only)
www.funfunforu...
🔗 mpj on Twitter
/ mpjme
🔗 Help translate the show to your language
www.youtube.com...
Painful pair programming session where we attempt to use the Twitter API - big mistake.
Quote of the day: “As developers it is our job to slam our heads against it until it’s solved”
So true lol
Couple minutes later... “oh shit it worked!!!!”
Sounds like my experience learning React.
Words cannot describe the amount of distaste I have for Twitter's API.
It would be nice if it even worked half the time. I made something that just had to write the tweet in the terminal when a new tweet showed up in my feed and it only worked occasionally and then a few minutes in (maybe 5 tweets), it just gave up.
The owl was an inspired decision, it's perfect. I look forward to watching the interview of how it got into coding...
David: "Do you know what we should do?"
mpj: "GIVE UP"
😂😂😂
OK, I know you said this is going to be the worst episode over but I am loving this 🦉.
Kudos for the improv on the technicalities. I fear, though, that owl plush might have upstaged you. ;0) LOL
I often get frustrated like this when I have to use others' code, and I feel bad like maybe I'm being too cranky, and I'm being overly dramatic or critical, but really sometimes some of these things are really that bad. It sucks when it's something like Twitter, being a big tech company and all, and you start to wonder whether you're the crazy one. I'm glad I'm not the only one that gets worked up about unintuitive APIs.
Your avatar was surprisingly not weird
We are all so used to watching dev videos or tutorials where the whole plate is already set up & served before the recording even starts. Have to admit they're pretty boring at times. Struggling is a part of being a developer, and seeing others struggle helps oneself
broaden their perspective and knowledge when facing different situations. Watching these episodes brings me and others (I hope) to reality. Aside from being a nice learning experience, you guys are entertaining as hell, and make it funny and relaxing. I love these. Keep it up.
Daniel shiffman uses the Twit npm package for access to the Twitter API
This is comedy gold XD
Nice API, Twitter
After many episodes were you struggle and do very little, I think it would be nice to change the concept to actually finish something rather than having a random time limit. At this point, it's been like 4 episodes were I feel like "ok cool, you're struggling like all of us. But is it really that interesting to watch 30min of this with no finality?". But that's just my opinion...
I agree. Much preferred would be to do something challenging like this, and walk through the steps from encountering a problem, to how to find a way to overcome it.
I have other opinions... I really like how this concept is realistic, it does feel like real problems since it is. so what if they don't make it to where they wanted in one episode :) what they should do in my opinion is add more episodes to one episode idea. like a twitter api episode 2. and then dont change anything about the format.
I would like to see working programs. this is one of of getting there without changing the concept.
Hmm. We did succeed and finish in the last episode (ua-cam.com/video/vyUNwihe9hI/v-deo.html). To be honest, it turned out pretty boring IMHO and the ones where we fail and learn are much more interesting rather than where everything is smooth and we succeed but really get no learning out of it.
That said, we recognize the problem that they become repetitive and we just slam our heads against an API. We're thinking about carefully expanding it to more episodes on one task but we've had bad experiences with multi-part episodes - the audience doesn't like them at all - there is massive dropoff on each episode, probably because it becomes harder and harder for each episode to catch up on viewing, and people that arent interested in the particular subject become more and more isolated. Keep the feedback coming and we'll keep on tweaking.
The "boring" part, in my opinion, comes more from the fact that you are unprepared for the task (for your video example: not knowing basic CSS, even doing it with div instead of a canvas, etc... Or in this one, not looking how the API works beforehand) than the fact that you are struggling with the task or not. I'm not talking about doing something closer to a tutorial, but at least, be prepared to do what you want to do, and then do it in front of the camera. In my opinion we'll learn more about real, interesting problems rather than feeling the "oh that happened to me too" sympathy over and over and not seeing anything real in the end.
I've got to agree with chop here, I don't mind the errors or lack of knowledge. But its more the lack of planning which annoyes me hope it gets better.
I have been working on something with their API for fun for like 2 weeks... I can find tweets between a time and limit the count...I figured I would be making some awesome full-featured bot with sweet bells and whistles by now.
Took me like a whole day just to get where you both got in far less time lol
Mpj "this api is a ludicrous pile of shite". Sounds just like me on a work day lol
This is the exact conversation I carry out in my head each time I start a project that needs to consume someone else's API
Trying to watch this on the bus on the way to work makes me look like a proper weirdo.. hahaha
On my previous job I had to build an analytic tool (collect number of tweets/retweets for ~2M blogposts).
The first my reaction was exactly as yours - OMG, Twitter API is so awful!
But several days later you on the one hand are getting used to it, and on the other - starting to understand that there is no other way to manage so big amount of data.
So, in my use case I have split collection mechanism into 2 phases:
1. Grab all available data and save into my own DB (it was running slow but only once)
2. Subscribe to a stream API (with needed params) and handle all new broadcast events (analyze if it is tweet or retweet) and also save to my DB (it was listening almost permanently)
This was my way of achieve the goal, is anybody know better solution? would be cool to hear your feedback.
P.S. Regarding the video - I liked it!
I'm watching this in my free time and feeling very stupid , ppl passing behind me thinking i'm watching some show for babies
First time I've not skipped the sponsor, that plushy worked. 🤣
Wondering you did not get any email to describe what you want to do with the TWITTER API ... I had a 2 weeks conversation with them and I still have no access ...
Having a hard time getting the approval as well...
I love these pair programming episodes. I thought your revisiting the Reddit Place clone was really great.
gif little bit distracting, in my opinion, a static image is better. and with fika it easier to watch.
"This API is like a ludicrous pile of shite" haha
This was surprisingly easy to watch, I think I was distracted by the train wreck.
I never knew an owl could *snap*.
The More You Know™
MPJ have a new haircut?
It is just starting to grow a bit wild
I was trying to make a joke like MPJ is now an owl and I didn't see the difference but now it's time to good old Coldplay - Fix You,
Anyway, MPJ =>{ return
Nah, its just the beak...
The Australian version of Fika is “smoko” 😁
Reminds me of Brian Lonsdorf's Professor Frisby tutorials. I only wish mpj's voice had been pitch-shifted. Love it though!
Hi MPJ, are you in the process of taking the channel into a new direction or will there more structured videos about specific programming subjects again in the future?
Nevertheless really enjoyed this video actually. Good to see I'm not the only one complaining about other peoples' work all the time ^^
Yeah, were taking a new direction. Partially because I need to make the channel more social as staring alone into a camera kills me, but also that the tutorial format is not sustainable (I cannot learn things fast enough for a video per week). Tutorials are also a saturated market, lots of people doing it - I want a format that plays more to my strengths.
Ah yes, being a remote worker I can totally imagine that. Personally what stood out to me about your videos is your critical approach to structure and architecture. I can't really word it, but I follow a few different channels and your videos have inspired me to work on my code simplicity, readability and file organization habits the most by FAR. I've also never seen someone explain the composition vs inheritance argument so well.
JS's "dangerous freedom", combined with your expertise on this topic, combined with the serious lack of quality in-depth videos about JS architecture could possibly be really interesting!
Not sure if it would fit into a social thingy, but coworking is probably the thing that drives the importance of structure and readability the most... So there's that
Holy crap, Twitter need to be looking at GraphQL, that REST API is nasty. Laughing my ass off at the video though, genius.
I have had to use the new Twitter API for a project and I can say the experience doesn't get much better after you have been approved access...
I like your solution to the missing footage
Twitter API - Premium operators
in_reply_to_status_id
Deliver only explicit replies to the specified Tweet.
When does the owl get it's own channel? That guy is good
I love the fika break format!
Eating coffee ☕
haha we said that? That's amazing, if so.
"Eating coffe" -> 3:47
you could do a followup and play with the mastodon api instead :-)
A puppet show! :D
Only a min in and I know this is going to be the best episode ever.
"Keep it simple, Stupid... "
- David 2018
Thank you for the insights wise owl of youtube.
What's the talk called? =D
The Jonathan Blow talk? It's this one ua-cam.com/video/k56wra39lwA/v-deo.html
Yes, thank you sir!
I hope you are paying the owl. He did good.
"relay on this really really old crap, somebody build in PHP". :/
Is it weird that it feels totally normal to me to see Owly there talking about programming instead of MPJ ?
PS: I hate twitter api docs too.
So it seems there's a lot of back and forth in the comments on whether they like this format or not, So I decided I'd add my opinion here too... Because everyone always needs more opinions! I'm relatively new to the whole developer scene and I am still learning some core fundamentals, So take this with however many grains of salt you need to BUT! I really like this format. I like seeing you guys slam your head against things, I like how you guys are honest and get frustrated. If this was any other dev channel, You'd have already written the program 50 times and rehearsed the whole thing. Having a general guide and not a hardcore thought out plan seems to make these videos very FUN. (It puts the Fun into Function!). Maybe having a slightly longer time (if possible) would solve some complaints. It seems towards the end of most of these videos you are just coming to the point where you're understanding the way to complete the task (Which personally I have no problem with since this isn't a tutorial, more of an insight into how developer life is). Anyway, Great job having the "balls" to put this video up and not feeling it necessary to hide all mistakes. It really makes newbies (like me) have more confidence in ourselves, seeing that those moments are just a part of the job and helps us avoid feeling like imposters. Thank you!
That was fun. Thanks, guys
I love these Try Try Fail videos 👍
it took me a long time to notice that owl is on reply.
I guess you should spend 5 minutes looking at the documentation of the API before running the cameras and decide to do such kind of projects.
Anyway, looking the small plush animal talking instad of MPJ was quite fun though
We did in one previous episode and it became super smooth and super boring. Sort of like an action movie where there is no villain. :) It also became inauthentic, as it showed an unrealistic view of what software development is - it's mostly a big struggle fighting with unpredictable bullshit.
Don't ask me why, but I really liked watching this beautiful disaster.
What did we learn ?
Nothing 😃😃😃.
I think you should try stripe or github they have a nice api documentation.
A discussion from the both of you about Jon Blow's views on (web) programming would be really interesting! Just title it that way too, so he can rant about the two of you on one of his livestreams ;)
Jon Blow dislikes basically everything that is not low level statically and strongly typed so there should be some interesting topics to focus on:
- Unit testing is BS (because you get nothing done)
- garbage collection is BS (very game specific, because you have to maintain 60 fps and the garbage collector screws that up, so you have stutters every time)
- exceptions are useless (although he says panics, i.e. sort of uncaught exceptions are useful for debugging)
- coroutines are not that useful (I think he said they are not worth the added language cruft)
- scripting languages are a failed experiment (because they hide complexity that you have to deal sooner or later, so you should go visual scripting if you want non-programmers to program high level stuff)
- ... I'm sure there's loads more
Train wrecks are fun fun fun to watch!
Y'all are hilarious lol.
This is how true development normally is. All the other channels are cool, but it's something about watching actual coding. At least on this channel.
I would recommend to stay on this path for this channel, but maybe on dev tips work on things before hand and just step through things considering that's how the channel was before.
Also please get rid of the fika breaks lol
Thank you, and I totally hear you, we should have more fika breaks
More videos with the plush owl!!!!
LMAO 25:31 made my day
I think the problem here (and I'm not saying this to put a downer on the video, its feedback - and probably jumping the gun because I've not watched the full video yet) was that the aim was to build "something" with the twitter API. Whenever I've wanted to build "something" its always been a disaster, not saying it couldn't work but from experience I've not seen it.
also sounded like a webscaping problem to me ;)
also googling becuase I was interested in the problem, this is impossible to solve with their API.
Hi nuttygold - we had a very specific goal, not “something’
You guys know what fika (written fica) means in Italian, right? XD
I laugh out loud every time they shout "fika time" because of that...
where can i find the jonathan blowe talk?
Also I think Twitter was the flagship Ruby on Rails app. so...
s/PHP/Ruby on Rails
David !!! have you read all those books behind you ?
He has not, uses them for seeming fancy
Got it Mattias , tip noted :p
Ahahaha ... very funny episode! LOL
this reminds me of mr rogers' neighborhood 😀
Use Scraper Js
The Gif was a horrible Idea. Extremely distracting
Great video though, sorry I am annoying
Could you not have looked at the requests in the network tab of devtools and copy the curl request?
Today was Pain Pain Function ahah
FunFunClusterF.. This whole layout reminds me of early web pages. Just too much going on.
Haha! 0!