This past week I started a new React project at work and was dealing with a weird issue with one of my components. It turns out the issue was caused by Strict Mode
NASA's Ingenuity Copter has flown its last flight, the EU blocking Amazon's iRobot acquisition, TypeScript in 2024, and more.
One of my side projects uses React Hook Form
for my forms and ran into some speed bumps while building tests for the individual components. I figure I can’t be the only one so I figure I’ll share my solution.
I’ve finally started going through all my RSS feeds, so there’s a lot to this week’s log. The topics are all over the place from the IRS doing what it should have done from the beginning, to a boneheaded decision to add some new top level domains, to the US Supreme Court saving Section 230.
Podcast heavy this week. I've been trying to go through and listen to my unruly queue.
Some criticism and defense of React this week.
This week we look at the next version of TypeScript, the new version of EntityFramework, a big acquisition at Netlify and more.
A little light this week. Identity thieves targeted a credit reporting agency, a look at the podcasting market, and more.
After stuffing Pocket with a bunch of articles, I've finally gotten around to going through them.
Was a little busy last week so this week is a little longer.
Quite a lot this week.
One of the things I needed to do recently was write unit tests for one of the pages of Digital Family Cookbook where I pull a value from a query parameter in the URL. I ended up having some trouble with it so I figured I'd share what I did to get it working.
I think I'm going to start this series of entries again. Trying to continue to share the interesting articles and stories I've read over the course of the week.
Ever feel like you can never completely get started with a project? That's sometimes how it feels with the fitness tracking app I'm building.
I've been using Jekyll to run this blog for the better part of the last six years. But recently, I've been giving serious consideration to switching to Gatsby or Next.js.
A little while back, I started a new project. I have been using spreadsheets to track a lot of my fitness goals
. This approach generally works, but I thought it would be easier if I had an app for that. So I did what any self-respecting fitness enthusiast developer would do...make one myself! But with that, also come unit tests.
In all of my professional experience, I've never worked for a company that did any unit testing and because of that, I haven't really done any either. I knew what unit testing is and the general concepts behind it, but never got around to actually building or implementing any tests. I decided that for Digital Family Cookbook, that would change.
I’ve often joked that the recipe project I’ve been working on is my “white whale”. I have in the past thrown everything out only to start over. I first built it in Ruby on Rails, but it was buggy and my limited knowledge of Rails made it a little hard to debug and figure out exactly what was wrong. I opted to rebuild it in PHP since I was quite familiar with PHP after building OpenVoter. I decided then that I wanted to start over to teach myself Node.js...well you get the idea.
Lately, I’ve been making steady progress on my side project, which I’m currently calling Digital Family Cookbook. I’m making it as a content management system for cooking recipes. As I’ve mentioned previously, I’m writing it using Node.js, React, & GraphQL. It’s been quite a learning curve, but I’m definitely glad I’ve been working on it. The tools are pretty cool and easy-ish to use once you get used to the syntax and some of the idiosyncrasies of React and JSX.
The last couple months have been really hectic for me and unfortunately I didn’t get much done on my recipe side project.