CFS Water CFSWater is a mobile application that reports scheduled and current water release and power generations for Army Corp of Engineer Tailwaters.Overview A team of consultants architected and developed CFSWater, a cross-platform mobile application using Flutter. The result was a highly functioning mobile app that reports scheduled and current water release and power generations for Army Corp and Engineer …
Over the years, we’ve seen many approaches to HTTP API design. While REST APIs are still very popular throughout the industry, they offer no inherent guarantees that the client’s assumptions about the response structures will be valid.
GraphQL fills this gap to an extent by allowing client-side code greater control over the resulting structures but at the cost of added complexity. RPC (remote procedure call) frameworks attempt a different solution by sharing generated type definitions between the client and server implementations. What if there was a way to achieve the type safety of RPC by simply inferring the type definitions from the server’s code?
Enter tRPC. Since JavaScript (and specifically TypeScript) can already span across client and server implementations, tRPC allows a client to directly consume structures defined by the server’s exposed procedures. Essentially, you import your dependencies from the server to access these procedures, their return types are inferred and checked at build time, and your client code can confidently consume the returned data.
In this post, we’ll look at how it achieves these goals and what limitations it places on your project stack.
Kent Beck, a software engineer famous enough to have his own Wikipedia page, is quoted as saying, “Make it work, make it right, make it fast.” A quick web search will show you several pages discussing this quote, some in great detail.
So, I’ll write another, and hopefully, I’ll provide two things to build on the existing literature. First, I’d like to put this concept in front of some programmers that might not have heard it, or if they have, haven’t taken it to heart.
Second, I’ll provide my own philosophy on the subject. Maybe it will different enough that you’ll get something new from it. I do have a slightly different take on it. Although I don’t want anyone to change the quote, maybe we can instead think of it as, “Solve the problem, make it maintainable, and make it perform.”
In the post, I’ll be talking more about the map() function – how it differs from other common loops, exploring its optional second parameter, using mapping in the return statement, and tracking with keys. By the end, I hope you’ll have a clearer understanding of how the map() function can be useful in your React projects.
Please note, this post is geared toward React beginners and new coders. Veteran users may not glean as much from the content.
There is such a rich, user-driven ecosystem around React that it can be difficult to discern which frameworks, if any, should be used to develop enterprise-grade applications. This blog post dives into the most popular ones and analyzes which are most suitable for that specific use case.
Before diving in, please remember: the decision of which one is the right one for a given organization or application is very context-specific, so diligent consideration is required to ensure an optimal outcome.