Jesse Martin

@motleydev

Developer Advocate @ GraphCMS. Brand, product and technology fanatic. Family man and follower of Jesus. Speaker, writer, full-stack maker. OG .

Germany
Vrijeme pridruživanja: studeni 2011.

Tweetovi

Blokirali ste korisnika/cu @motleydev

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @motleydev

  1. Prikvačeni tweet
    16. lis 2019.

    In a month or so I'll be giving a talk about error handling in . What are some of your favourite libraries for error handling? Appreciate RT's for the spread. Follow for the slide link later. 😉

    Prikaži ovu nit
    Poništi
  2. prije 5 sati

    The implementation agnostic nature of means it's really, really good at domain modeling. Data modeling needs implementation details to answer the "how" of your business. GraphQL answers the "what" and often the "why".

    Poništi
  3. 2. velj

    I did mean to write "Better, BUT that would exclude users from our free tier" - oh well.

    Prikaži ovu nit
    Poništi
  4. 2. velj

    Like this message or follow me if you want to be notified when the article drops. I'll update this thread then. Have a great weekend! And, remember to measure twice and cut once. Now time to go do a small refactor… 😉

    Prikaži ovu nit
    Poništi
  5. 2. velj

    Ok, this is becoming more salesy than I originally intended and is approaching the number of words I intend for the blog post, but I think it really highlights how flexible dev tooling and proper content planning really make it a great time to be building digital products.

    Prikaži ovu nit
    Poništi
  6. 2. velj

    It's also another reason that GraphQL is so great because we can do "additive" schema evolution without breaking existing development builds and won't need to provision a new endpoint or anything like that.

    Prikaži ovu nit
    Poništi
  7. 2. velj

    It's also another reason why having a completely unopinionated CMS is such a great thing because you can "just add an audio length field real quick" without needing a developer to do that for you. We are one of the low number of CMS that provides that. Even still.

    Prikaži ovu nit
    Poništi
  8. 2. velj

    There's always going to be a balance in content creation between seamless / low-effort workflows, and actually letting people control some of the details.

    Prikaži ovu nit
    Poništi
  9. 2. velj

    And that's what I'm going with. If a user is creating an audio file, they have all the data they need when they upload the data. Also, going to talk with our file delivery service about optional flags for the meta-data, cause it's 2020, people.

    Prikaži ovu nit
    Poništi
  10. 2. velj

    Lastly, as I thought about the problem some more, I realized that for this demo, a user would at MOST be adding new audio files maybe twice a week. So why not just have the user check their audio length and add it to the CMS at point-of-creation?

    Prikaži ovu nit
    Poništi
  11. 2. velj

    Second, I could create a serverless hook that would get pinged by a webhook when I add a new entry in my CMS with the audio file so that it would do a lookup of the metadata, and write it back into my content repo. Better, that would exclude users from our free tier.

    Prikaži ovu nit
    Poništi
  12. 2. velj

    First, I could simply "play/pause" the audio file when it's loaded so that I get the metadata payload. But I also want to stuff this data into an RSS feed which means that I'd have to somehow ping the CDN for each audio file. That would then need to introduce local caching.

    Prikaži ovu nit
    Poništi
  13. 2. velj

    Content architecture thread: This will be written up this week in an accompanying article about the latest demo I'm creating for . I need the duration of an audio file that is delivered via CDN. The CDN strips the metadata off of the file. So I had a few ideas.

    Prikaži ovu nit
    Poništi
  14. 31. sij

    Nothing is certain except death, taxes, and catching every sickness that goes around your child's school.

    Poništi
  15. 31. sij

    Several people in the React community will tell you not to rush out and switch everything to hooks. I'm not one of those people. Use hooks for everything! It makes code so much more readable!

    Poništi
  16. 29. sij

    And now here's one for the people! 😎 Learn how to architect a headless project and maintain serverless functions + front-end code in the same codebase! 🔥🔥🔥

    Poništi
  17. 29. sij

    Here's one for the people. Learn how to re-use your knowledge in the build and on the client.

    Poništi
  18. 29. sij

    Daughter (First Grade): "How old do I have to be to get my ears pierced and get a cell phone?" My Wife: "Well, it's something we need to talk about…" Me: [Googles real estate prices in Greenland]

    Poništi
  19. 29. sij

    Working in dev rel, I tend to create more "one off" sites than the average dev, this tool is great for finding a font to help add that extra layer of realism.

    Poništi
  20. 28. sij

    Just saying, I think this would be an awesome addition to the map function.

    Poništi
  21. 28. sij

    When dealing with single-page applications, an important mental model is to consider the URL as an instruction for application state. It is possible to get to the same state multiple ways, the URL is just a way to share the state as you experienced it.

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·