A few years ago I learned that the nba releases json files daily to the public. Immediately, I jumped on the opportunity to build nba related applications, yet one thing that always stood out to me about their api is the difficulty building relationships between its data collections. Take for example this snippet of json for a collection of players: [ { "firstName": "Ben", "lastName": "Simmons", "teams": [ { "teamId": "1610612755", "seasonStart": "2016", "seasonEnd": "2020" }, { "teamId": "1610612751", "seasonStart": "2021", "seasonEnd": "2021" } ], "draft": { "teamId": "1610612755", "pickNum": "1", "roundNum": "1", "seasonYear": "2016" }, } ] Here we have we have some basic information about the player such as his first and last name.

Over the years React has matured well in making sure the development process is predictible, especially for newer programmers, but every once in a while React developers come across a process in the framework that requires a deeper level understanding. Keys in react lists are one of those processes. function ExampleComponent() { const [list, setList] = React.useState([ { name: 'a' }, { name: 'b' }, { name: 'c' }, ]) return ( <ul> {list.

An Early Career Lesson… Years ago when I was interviewing for the first time, I distinctly remember a coding challenge I received that asked me to create an app that allows users to enter a prefix and receive a list of words that contained the entered prefix. I was given a little over two hours to complete the challenge. Eager to impress, I tried to spin up a React app, which at the time was the latest and greatest front-end js framework at the time (this was before create-react-app was a thing), and Redux because that technology was cool and new.