@billcava@armon@HashiCorp@Wayfair If a "Duce" is a leader of the Italian fascist party, then I guess a preduce would be whatever comes before that. Given the political turmoil at the moment, I'll stop there :).
Really enjoyed the presentation on Consul Connect by @armon at the Boston @HashiCorp meetup tonight, and thanks to @Wayfair for hosting! Clear, concise, and useful. Looking forward to testing it out over the next few days.
Just released a new post discussing the dependency good code has on good naming: https://t.co/6dZBR1PqrM. Would love to hear what you think about the idea that readability takes precedence over design.
CodeBuild running a bit slowly today? Here's a new post with some ideas for how to speed it up: https://t.co/HCfOJvne7M β¦ - Speeding up AWS CodeBuild with Custom Build Environments
New post about continuous delivery. This just about wraps up the series, so we can start getting into more specifics. Let me know what you think! https://t.co/p1F4mP6ukr - What is Continuous Delivery?
@nickramsbottom I'm glad you're enjoying the series! My last newsletter had a list of reading recommendations, and I'm planning to keep doing that in the future.
@MrAakashShah That said, I have nothing bad to say about TypeScript. I learned the basics of both when getting into typed JS, and would like to delve deeper at some point. It provides the same value, and seems to have better tooling. Just haven't gotten around to it yet.
@MrAakashShah Thanks! Glad you're enjoying it. Difficult to answer fully, because I've done far more Flow than TS. Chose Flow originally because I work on a considerable number of React projects, and it had excellent integration (FB owns both, so it made sense to me).
@VivekNayyar09@manjula_dube@ritz078 One less obvious benefit of abstracting the fetch call is that it allows you to work directly with domain objects in your component, rather than with raw API response data. If you ever change your API response, you can always update the mapping in your API layer.
@VivekNayyar09@manjula_dube@ritz078 The most common issue I've seen is when the construction of the fetch parameters makes its way into the component code. This can be very distracting for other developers trying to make sense of what the component is actually doing.