The mostly unremarkable journey of two remote software engineers.
This is the 4th part of my learn-in-public shinazz, with me taking a crash course on Algorithms and data structures. In this post, we will talk about a 5-step process I learned in solving programming problems. It's a 5-step process that should help you on implementing and solving complex requirements.
After three months of development using expo for an MVP, I’d like to share some feedback on my experience on using the managed platform. Do note that my prior experience in react native before this project was just a month of R&D two years ago. It’s
I just thought that I’d share what I did on an internal CLI tool that allows others to NOT modify any existing files in the NodeJS CLI Tool project. The ProblemWe thought of creating a tool that would streamline our development workflow by automating some tidious, manual, and repetitive
Yesterday, I had the priviledge to give a talk at FEU Institute of Technology about using web technologies to create desktop applications. For the past few years, I’ve been working on a desktop application wherein the UI component is basically a browser. The experiences I accumulated with this project
Let’s first define an example problem to better understand the issue we have with normal looping: For example, we have an array of post IDs that we would fetch and then print it out on the console const ids = [1, 2, 3, 4]; for (var id of ids) { fetch(
If ever we wanted our WebApp available even if the user does not have any internet connection, we would need to use service workers. But the thing with service workers is that they’re not “easy” to implement. It’s a good thing though that the GoogleChrome team released a
EQCSS allows us to style elements based on the element’s state. It is similar to CSS’ media queries, but with the added feature to style elements based on the element’s dimension and contents, and not just based on the browser’s width and height. This got me interested
