Beshimo?
Thereās a funny scene in Rush Hour 2 involving Chris Tuckerās character and a Taxi Driver. They go back and forth exchanging āIāmma slap youā andĀ āBeshimoāĀ until Chris Tucker gives the driver money. To this he responds:
āNow youāre speaking my language.āĀ
And they finally start driving. Itās one of my favorite scenes in the series.Ā
I believe the actual words are:Ā āBei Qin Lorā orĀ āęÆé±åÆā according to YouTube comments.Ā
What does this have to do with todayās post? Well as a designer, I work hand and hand with developers often. Itās definitely a building block to the job. I wouldnāt say itās necessary to know how to actually code, but it definitely helps if you have some understanding to it.Ā
A lot of my work tends to build off of the needs of the user, but I have to keep in mind how itās going to be translated into the developer realm. Iām noticing more and more how different our mindsets are. Itās not a bad thing, but sometimes itās hard to communicate certain instructions.Ā Thatās the beauty of my job right now. Because we work cross functionally and hands on, weāre encouraged to work hand-in-hand with the dev team if need be. Itās a great collaborative effort that lets us get to see how the other side works.Ā
Because of this, Iām able to see how we operate differently. For instance, as a designer, our instructions are free from constraints other than the parameters of the brief. Weāre free to run around within those parameters with our creativity. A developerās instructions will usually be to the T, and they follow it down to each pixel. Iāve definitely made some missteps in this exchange, but I'm working on getting better at it. Because of these missteps, sometimes we have to redo some work. Itās a learning process, butĀ I'm gladĀ I'm going through it.
Itās funny because itās not just designers and developers. It can be applied to all fields, and I just realized that itās happened at one of my old jobs. I used to work at a print shop. The gist of one of my duties was to take down the instructions from the customer, and give it to the printers. Pretty straight forward, right? Not really. If I didnāt have enough details, the job would end up back on my desk because the instructions were not clear enough. Anytime that happened, that job would be halted and would be reprocessed, or the entire schedule would be halted. I eventually learned to write up the instructions as if they could take my jobs without me having to explain them.Ā
I hope to be able to master the dev handoff, and sometimes it means to just slow down. My advice to you all is to try to look at your work with a developer hat on. It might just help save you time in the long run.
On an ending note, Itās been a while sinceĀ I've posted, but like I said, I want to post on my own time and rather than giving myself deadlines to make it more organic. Although I feel like I should keep up more with myĀ āHow I became a UX Designerā series.... weāll see.Ā
Thanks for keeping up with my stuff if youāve enjoyed it so far!











