Amy Blankenship
1 min readApr 12, 2023

--

I have an article submitted to CodeX that hasn't yet been approved that talks about the flip side of why people do this, since I was recently asked to try to implement functionality in Django that wasn't suited to it. In short, part of the page was a list of items, each of which had a button to delete it and one to edit it. As long as I only needed delete, I could make it work with the deletes being radio buttons inside the li tags, but if we hadn't shifted approach to go into React (too late to save my job, since the people who decided to go with the unworkable approach threw me under the bus rather than acknowledge their role in it), I have no idea how we would have done a form post in a clean way from the same physical part of the page we did a delete from. And I caught heck for the multiple form tags people didn't understand.

But you can bet that if _I_ don't know how to solve these types of problems after as many years as I've been doing it, your average recent bootcamp grad certainly won't. And even you don't see this kind of interaction design at the beginning of a project, you can bett your ass some designer will add it at the least convenient moment. And "stakeholders" don't want to hear that now we have to tear everything down and rebuild it another way or that their golden designer child has to change one detail on their design.

--

--

Amy Blankenship
Amy Blankenship

Written by Amy Blankenship

Full Stack developer at fintech company. I mainly write about React, Javascript, Typescript, and testing.

Responses (1)