Search

Recently I decided to begin learning GraphQL because in the past I have worked a lot with REST APIs, and initially based on a lot of info, it seemed like GraphQL was perfect and could be the ultimate successor to REST APIs. However, hands-on experimentation quickly dispelled that notion, highlighting that GraphQL, despite its robustness, isn't a one-size-fits-all solution.

Welcome back to the part two of this blog post series, this is a quick preview of the content: 4. Small and slim components and the Single Responsibility Principle, 5. State management, 5.1 What is state management?, 5.2 Why are we considering Recoil.js for global state management?, 5.3 Should you deprecate your current implementation of React Redux? 5.4 React Redux 5.5. Is Redux here to stay? 6. Design patterns 6.1 React Hooks 6.2 React Context API 6.3 Component composition 7. Automated testing

What is it valoralo.mx? Some time ago, I found an interesting service Website called judge.me and I got inspired by that, because here in México, most of the time, owners don’t really know, about their customers experience, and sometimes it is very difficult for them...

https://smsparatodos.com – The english version is  https://smsforall.org ​ I chose that name because in México since ancient years, transactional SMS communication is been very expensive, and even with the usage of International services such as Twilio.com they are still quite expensive(cost per message), and I...

I accepted the challenge of creating a robust technology platform…. I was invited to the INVESMARK CONSULTORIA Y SERVICIOS SAS DE CV company founded in México City and decided to accept the challenge of creating a robust technology platform to handle territorial and on-site research...

I have a long story with this personal project As I developed this application for two doctors in 2012 and and they are still satisfied with the latest version of this Electronic Health Record Application(v4). During all these years I was able to migrate them...