PRs for Organizing File Hierarchy
Software engineer. Interested in small and efficient tech product teams and ambitious projects that move things forward.
Search for a command to run...
Software engineer. Interested in small and efficient tech product teams and ambitious projects that move things forward.
No comments yet. Be the first to comment.
Hello to anyone that might reach this website! Just want to let you know that I've changed the place where I publish and build new things. You can find things I'm up to on apisurf.dev. Cheers!
There are two good articles that touch on some of the concerns and annoyances I also share, but I'll try to cover some of my views about it. I had a chance to use Next.js 13 for a few weeks and noticed that some things make my job a lot simpler, whil...
new Date('YYYY-MM-DD') might not do what you think it does

Recently I stumbled upon an interesting test case where I needed to cover many possibilities and make sure everything continues to work as intended in the future. I had 7 boolean flags that needed to be used to toggle an app functionality. It's a bit...

Some old methods of accessing uploaded file contents inside a Next.js route handler don't work anymore or at least not in a way many tutorials explain it. E.g. many outdated online examples use page router which has route handlers that receive differ...

Tldr: be swift :)
I just wanted to mention 2 things I noticed helping with file hierarchy refactors.
This makes it easier to do code reviews, check and spot import misreferences etc. It'll also make things easier to revert, or discard the work altogether
This type of PRs can bring chaos to reviews and merge process of new branches if they stay open for too long. You typically want to do the review and merge back to the source branch as soon as possible.
The most common problem with this kind of PRs is when someone else decides to work on the same files that no longer exist under a certain path. When merging code changes with a branch that changed file paths it's too easy to overlook code changes and lose them by just accepting the file location change. This can be time-consuming to troubleshoot afterwards. It's much easier to spot this if a PR that does the file organization is merged sooner rather than later.