I used to use the beginning of clutch’s psychic warfare. The first track is some low murdering, and then it comes in hard with X-ray visions. Always woke me right up.
I also used slothrust’s “like a child hiding behind your tombstone” for a while. That also starts a little quiet and then ramps up. Never hated the song, somehow. https://slothrust.bandcamp.com/track/like-a-child-hiding-behind-your-tombstone
Now I just have one of the default alarms and I kind of hate it.
Product owners say, "We want to change the site so users see a list of all the other users on their team with access to this project "
Okay. Do some thinking. Going to need the backend to return that information to the front end. Decide what URL that should be under (api/v1/projects/users, maybe?).
Now we make the backend actually do that. Create a new file for this endpoint. Update the routes file so that url points to this file. Write the handler class.
Does this endpoint take any particular input? We know who the caller is for free from the framework. We only want to return info about one project or all projects? Make that decision. Update URL if needed.
Write the code to get the other users on the projects in question. Maybe that’s SQL, but might also be ORM (code from a framework that generates SQL based on objects). Decide what information we actually need. Package that up and send it back. The specifics depend on language and framework.
Write automated tests for this. Make sure it works for
Realize this needs to paginate. Go back and change the handler code to do that.
Realize due to some quirk of how permissions work, someone can be on the project twice. Talk with the team about if we should just decide that here, or try to fix the root problem. Probably the former.
Add deduplication code, then, and test cases.
Open this up for code review.
Start the front end work.
Make a dummy page first and update your API calling code to know about this new route, assuming you don’t have that auto magically set up somehow. Make sure it calls it and gets a response.
Realize that staff users technically have access to every project in the system. Ask product if that’s how they want that to behave. If no, figure out what you all want that to do instead.
Do a bunch of react work to make the page pretty, put the response in the right UI elements with links to the right place. Realize the response you’re sending back makes building the links annoying because you didn’t send some part of it, so you’d need to make another request to the backend for every link. That sucks. Update the backend to include the user’s team-id that is for some stupid reason still in the URL. Comment on code review.
And now I’m tired of writing.
Edit: I hit submit before I was done. Finished now. Edit: fix typo