<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jennifer Wong on Medium]]></title>
        <description><![CDATA[Stories by Jennifer Wong on Medium]]></description>
        <link>https://medium.com/@mybluewristband?source=rss-cdafa7d9387c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*dO1eP_uZza7sJtleC1G9hg.jpeg</url>
            <title>Stories by Jennifer Wong on Medium</title>
            <link>https://medium.com/@mybluewristband?source=rss-cdafa7d9387c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:47:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mybluewristband/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[San Francisco’s Secret Fruit]]></title>
            <link>https://medium.com/@mybluewristband/san-franciscos-secret-fruit-b1883a62bb68?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1883a62bb68</guid>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[fruits]]></category>
            <category><![CDATA[family]]></category>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[food]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Sun, 23 Aug 2020 19:26:05 GMT</pubDate>
            <atom:updated>2020-08-23T19:26:05.349Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Secret in Plain Sight</h3><p>It’s early summer 2014, and we’ve just finished shopping at the local Chinese grocery store. We extend our walk home a bit, weaving our way through the Richmond District. As a lark, we wander into the open house of a whatever-point-whatever-million dollar home. We stroll through the halls, perusing the listing sheet, eyes wide from the price. We continue down the stairs, and then I see it: a secret hidden in plain sight. Through the in-law unit that borders the garage, through the sliding glass door that leads to the backyard — a huge tree covered in plump, bell-shaped, light orange fruits. SCORE.</p><p>I turn to the real estate agent who had followed me into the backyard and I can’t help myself. I point, open-mouthed at this tree, “THAT. Is a loquat tree.” He replies, “Oh yeah! Did you want to take some fruit?” I am giddy with excitement. I rummage through my tote bag and grab a reused produce bag while recounting my loquat knowledge to the agent. Then I transform into a director, showing my then-boyfriend which bunches to pluck. When I reach into my tote for a second produce bag, he has to stop me. I protest, but he convinces me we’ve overstayed our welcome. I slump in disappointment, but the agent is friendly and happily sends us on our fruit-filled way. I slink back through the sliding door, quietly hoping the future owners recognize the treasure they’ll acquire with this house.</p><figure><img alt="Perfectly round and ripe loquats on a branch surrounded by deep green leaves." src="https://cdn-images-1.medium.com/max/728/1*kx-8uyrsQuNHOOqh_ZcN8Q.jpeg" /><figcaption>Image by Walter Weaver</figcaption></figure><h3>Introducing: The Loquat</h3><p>The loquat, a phonetic translation from the Cantonese <em>lou4 gwat1, </em>originated in Southern China¹ — as did my ancestors. It is an incredibly versatile fruit that grows in subtropical (like Guangdong Province in China) to mild temperate climates (like the San Francisco Bay Area).</p><p>The loquat tree has large, slightly fuzzy, and deeply veined leaves. Their colors range from light to deep forest green. They’re stiff and almost brittle. The tree’s branches are slightly gnarled, bumpy and fuzzy like alert, brown caterpillars. A tree can live to be 150 years old², but requires eight to 10 years of growth before it bears fruit. And, even then, trees only bear fruit every two or three years.³</p><figure><img alt="Watercolor of a Victor variety of loquats (scientific name: Eriobotrya japonica) specimen originating in Orange County, CA" src="https://cdn-images-1.medium.com/max/734/1*en1Z-yDXpp_OWiqUGqOgfg.jpeg" /><figcaption>Image from Wikipedia</figcaption></figure><p>When ripe, loquats boast a soft, slightly floral flavor, reminiscent of summer peaches and delicate mangoes. Their sweetness brings to mind a mellow honey or turbinado sugar sparkling on the tongue. When unripe, the loquat carries a lightly acidic tartness like a sweet Meyer lemon or raspberry lemonade, that causes the mouth to water. The loquat’s flesh is soft, yet firm like a grape: juicy without a mess. Its seeds are smooth, shiny brown pits.</p><p>I’ve been known to describe the loquat as an extremely delicious mashup of a peach and apricot.</p><p>For optimum enjoyment, peel the skin (I recommend from the bottom up), split the fruit in half and remove the oversized seeds. It’s exceedingly difficult to have just one.</p><p>“Loh gwat!” my grandmother exclaims as she presents a bowlful of peeled fruit halves to myself and the rest of her grandchildren.</p><p>I dutifully take a piece and eat it. She smiles and nods approvingly. It’s sweet and delicious, so I take another. The second is tart and I scrunch my face, eyes watering a bit from the acid. My grandma mimics my face and laughs to herself, coaxing us to eat more.</p><p>As a child, I never quite understood what “loh gwat” were. To me, they were just another fruit that my grandmother conjured, ready-to-eat, from the kitchen.</p><p>It wasn’t until years later, as a teenager, that I realized my grandma labored over every fruit, carefully peeling and coring this one or diligently slicing that one into perfectly manageable bits. I also learned that in all those years, my grandma was pronouncing “loquat” with a Chinese accent. But teenage Jenn was wrong — loquat is <em>lou4 gwat1</em> pronounced with an American accent.</p><p>Once in 2015, I saw a woman in my neighborhood with two May Wah bags filled to the brim with loquats. My eyes light up. Again, I couldn’t help myself — I stopped her on the street.</p><p><strong>Me</strong>: “Oh my gosh. Where did you get those? Those are loquats, right? Was May Wah selling them?”<br><strong>Her</strong>: “No, my friend has a tree in her backyard and gave them to me! I was just visiting her… do you have a bag?”<br><strong>Me</strong>: “Huh? Yes?”<br><strong>Her</strong>: “If you have a bag, I will give you some!”<br><strong>Me</strong>: “What?! Wow. Thank you so much!”</p><p>I hold my bag out to her and she shovels loquats into it. I am elated.</p><h3>But where tho?</h3><p>Loquats bruise easily and have a relatively short shelf life, rendering them near impossible to find in commercial grocery stores. They grow reliably with little maintenance, but harvesting and storage require a gentle touch. Commercial loquat production in the United States is (sadly) not lucrative because of these factors. However, stronger consumer awareness of the fruit in countries like Brazil, Japan, Israel, Italy, and Spain means one sometimes finds them in markets or fruit stands there.⁴</p><p>If you’re lucky, you might discover loquats at a local farmer’s market, specialty fruit store, or nearby orchard. And as soon as you learn to recognize the trees, you’ll start to notice them everywhere. A former coworker grew up eating loquats in Florida and said that he’s seen them growing as San Francisco street trees. And he’s right. With technology and <a href="https://data.sfgov.org/City-Infrastructure/Street-Tree-List/tkzw-k3nq/data">DataSF</a> on our side, we know that San Francisco has approximately 2,700 loquat street trees! And that doesn’t even include trees growing in people’s backyards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d46O1s9-loRXqhww" /><figcaption>Screenshot from DataSF visualization of loquat street trees</figcaption></figure><p>A farm in the Contra Costa County,<a href="http://www.peterwolfe.com/"> Wolfe Ranch in Brentwood</a> which specializes in U-Pick fruits like peaches and cherries, once sold pre-picked loquats. I couldn’t believe it! Alas: A few years after they popped onto my radar, they ceased selling loquats. Unfortunately, I never made it to one of their harvests.</p><p>I once saw them at a Chinese fruit and vegetable market in the Richmond District close to a decade ago, but haven’t seen them for sale since.</p><p>However, one might have more luck on the east side of The City. I was recently informed that one can, at times, <a href="https://freefarmstand.org/2014/06/16/dreaming-green/">purchase these beauties</a> at the <a href="https://sfgov.org/realestate/alemany-farmers-market">Alemany Farmers Market</a>. And a quick search online returns <a href="https://cuesa.org/food/loquats">K&amp;J Farms</a>, who sell loquats in May and June at the Ferry Plaza and Mission Farmers markets. Exciting!</p><p>My loquat source? It’s an open secret — my grandmother in the Richmond District, of course.</p><h3>My Loquat Herstory</h3><p>Pau Pau, sometimes written “Po Po” or “Paw Paw”, is a Cantonese (or Mandarin dependent on the intonation) term referring to one’s maternal grandmother.</p><p><em>As an aside, Chinese languages contain honorific titles for each person in a family which indicate how they are related to you. Pau Pau is just one of many. </em><a href="https://www.youtube.com/watch?v=A1HaZ4WLo50"><em>This video</em></a><em> describes most of them in Cantonese.</em></p><p>Decades ago, Pau Pau’s neighbors gave her some loquats from their backyard tree. Pau Pau was surprised to see this rare, but familiar fruit, a memory of her youth in <a href="https://en.wikipedia.org/wiki/Xiangshan_County,_Guangdong">Zhongshan County</a>, China, from which she immigrated directly to San Francisco in 1948 as a young adult. She enjoyed the fruits at home with her children and decided to plant a few seeds in her own garden. Pau Pau always had a green thumb, pruning all types of plants from plum trees to rose bushes. As a child, I remember being confused by all the egg shells and coffee grounds in the dirt. Eventually, the tree grew and blossomed, and Pau Pau had her own share of loquats to dole out to family, friends, and neighbors.</p><p>Years later, my father planted a second seed toward the back of Pau Pau’s yard, making harvests even more plentiful. Dad has also grown a few small loquat trees in large pots in my parents’ front yard. Recently, he transplanted them to more spacious soil in the backyard.</p><p>I have attempted to grow tiny versions of the plant in my apartment. I am, officially, 0-for-2 having underwatered my fragile seedlings or forgetting them while on vacation, but I haven’t given up. In fact, I planted eight new seeds from Pau Pau’s harvest this year into pots a few weeks ago. One day, this seedling will be planted in the fantasy backyard at the fantasy property that I fantasize that I can afford.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q0unkdgtKuPHuOJXgm1YZw.jpeg" /><figcaption>This year’s harvest of loquat seeds from Pau Pau’s house (2020)</figcaption></figure><p>When the loquats start to ripen on the branch, Pau Pau calls my family and sometimes our extended relatives (from her landline), letting us know it’s time to pick “loh gwat.” Best to do it before the birds eat them all or they fall on the ground, as she says. We trek over with gloves, a branch-cutter, fishing net strapped to a bamboo pole, gardening shears, and a palpable hunger for delicious fruits. It’s an hours-long operation and we walk away with bags, boxes, or buckets of loquats.</p><figure><img alt="My grandma looking up at the camera and smiling, a few boxes in front of her filled with leaves, branches, and loquats" src="https://cdn-images-1.medium.com/max/1024/1*gk-D0OKggXXFDbVlyCdLRQ.jpeg" /><figcaption>My Pau Pau in her backyard (2014)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cLDDi2o-06l28JVwzbtuXQ.jpeg" /><figcaption>Pau Pau, Mom, and me sorting loquats (2018)</figcaption></figure><p>One tragic year, my family hired gardeners to remove two very large trees in my grandma’s backyard. In addition to this work, they weeded and trimmed. This was something new — Pau Pau used to do all of the gardening herself, before age forced her to stop. No one advised the gardeners, and they trimmed the loquat tree back so hard that it didn’t bear fruit for several years.</p><p>In 2019, the June heat wave killed our chances at loquats.</p><p>Each of these is a sad and devastating event, but it only renews our hope in the next year’s harvest. Because loquat trees only bear fruit every two to three years, it’s always a gamble anyway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*quX-7Wiw4O1IXP9r9kFqgA.jpeg" /><figcaption>Part of our harvest (2020)</figcaption></figure><p>It’s Alli and Alex’s housewarming party in Oakland. By the time we arrive, the event is well under way. We walk through the house to the backyard, greet everyone, and then I see it. The tallest loquat tree I’ve ever seen. Its branches are laden with beautiful, ripe — and unreachable — fruits.</p><p>I eagerly share the secret with my friends. I point, open-mouthed at this tree. “THAT. Is a loquat tree.” Alli and Alex laugh. “Yes, it is.” “Have you had any yet?” I ask. “Yes, but they were a bit sour,” Alex replies. “They look ripe now to me!” I exclaim. Desperation takes over and I panic internally thinking of ways to acquire the loquats. I need them.</p><blockquote>Do you have a ladder? Have you tried them again yet? Can I climb your fence?</blockquote><p>Alli and Alex offer what I take as permission, warning me that the fence isn’t the sturdiest. Sam and I had just started dating, so I strong-arm him into climbing a fence to pick some by talking about what a great rock climber he is. He manages to gather a few bunches before reaching higher begins to feel dangerous.</p><p>I take the loquats inside and carefully peel them, remove their seeds, and place them in a bowl. Wandering around the party, I offer them to people like hors d’oeuvres.</p><blockquote>Do you want some loquats? Oh, they are a delicious fruit, kinda like a cross between an apricot and a peach, but way tastier. You’ll love them. These are from Alli and Alex’s tree right there!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8iQYT6gZG2Ox6w5n" /></figure><p>Without Pau Pau, none of my family would know about loquats.</p><p>The story of loquats in my family is also an immigration story. Just as Pau Pau immigrated to the United States from China, so did the loquat arrive on these shores. Loquats and my family share a lineage that goes back to the land in Southern China. We thrive in temperate localities: Zhongshan, San Francisco.</p><p>Adaptation takes many forms. For loquats in the United States, new soils and climate meant a physical adaptation. When Pau Pau arrived here in San Francisco, she adapted to the culture, the language, and a new way of life. Adaptation does not preclude retaining a sense of self, though. A loquat is still a loquat. And my family still keeps our Chinese traditions close thanks to my grandparents and great-grandparents.</p><p>The community Pau Pau built in San Francisco is forged from a common understanding of this uncompromised adaptation. Over time, that community presented her with gifts of remembrance from our motherland, including the loquat. Pau Pau recognized something familiar in this fruit. Community in the form of a mutual secret. “We are new to this place. But we preserve ourselves.”</p><p>Secret fruit from home. Secret seeds distributed and planted.</p><p>As the loquat trees grow in Pau Pau’s backyard, so do our family and traditions. We’ve created a new biennial ritual around loquats — every two years, the family comes together to create a cacophony of falling branches and sorted fruits. We keep planting these precious seeds, growing ever deepening roots in what was once an unfamiliar land.</p><p>It is a secret that I keep, but one that cries out to be shared with others.</p><p><em>Article inspired by </em><a href="https://selfevidentshow.com/"><em>Self Evident podcast</em></a><em> and a shitty NY Times article about equatorial fruits, and originally published on </em><a href="https://missionlocal.org/2020/08/loquat/"><em>Mission Local</em></a><em>.</em></p><p>[1]: “<a href="https://en.wikipedia.org/wiki/Loquat#History_and_taxonomy">Loquats History &amp; Taxonomy</a>”, Wikipedia. Retrieved July 19, 2020.<br>[2]: Eulalia Palomo, “<a href="https://homeguides.sfgate.com/fruitless-loquat-tree-60325.html">Fruitless Loquat Tree</a>”, SF Gate. Retrieved July 19, 2020.<br>[3]: “<a href="https://crfg.org/wiki/fruit/loquat/">Loquat</a>”, California Rare Fruit Growers. Retrieved July 19, 2020;<br>Lynne Rossetto Kasper, “<a href="https://www.splendidtable.org/story/david-karp-loquats">Loquats may be rare, but they’re worth looking for</a>”, The Splendid Table. Retrieved July 19, 2020.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1883a62bb68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–07–30 Mission Police Station Community Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-07-30-mission-police-station-community-meeting-c09ca4231b3b?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c09ca4231b3b</guid>
            <category><![CDATA[transparency]]></category>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[police]]></category>
            <category><![CDATA[mission]]></category>
            <category><![CDATA[volunteering]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Wed, 25 Mar 2020 23:20:20 GMT</pubDate>
            <atom:updated>2020-06-05T02:49:38.161Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.lwvsf.org/police/">League of Women Voters of San Francisco</a> Observer Corps Report</p><p>Official League Observer name: Jennifer Wong</p><p>Location: 630 Valencia St, San Francisco, CA 94110 (Community Room)</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p><a href="http://sanfranciscopolice.org/mission-station">Mission Police District</a>, Regularly Scheduled Community Meeting</p><h4>Did you attend the whole meeting?</h4><p>Yes.</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Yes. It was generally allowed throughout the meeting, but most of all at the end of the meeting. It did seem adequate.</p><p>About 10 people from Clinton Park area showed up in force to discuss issues of drug dealing and violence in the area. They were each allowed a fair bit of time to speak and the</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><p>Chief Gaetano Caltagirone<br>Sgt. Cole<br>Scott Madison from Citizens’ Advisory Board<br>Eddie from Community Ambassador Team<br>Art Campos from SF SAFE<br>Tom Temprano (Supe. Mandelman Legislative Aide &amp; member of City College Board)</p><p>Everyone was attentive, courteous, and prepared. Presentations were well prepared, people listened and offered potential solutions and contact information when problems were presented.</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>There was an interesting presentation on a man named Dave experiencing homelessness that had interacted with police. They were auctioning off one of Dave’s art pieces to help him raise money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*ejqqATWzBgEU5OR-M6p7Cg.jpeg" /><figcaption>Mission District Map</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c09ca4231b3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-07-30-mission-police-station-community-meeting-c09ca4231b3b">2019–07–30 Mission Police Station Community Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–11–19 Richmond Police Station Community Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-11-19-richmond-police-station-community-meeting-b1d3ef9d93ac?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1d3ef9d93ac</guid>
            <category><![CDATA[police]]></category>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[cupcakes]]></category>
            <category><![CDATA[richmond]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Wed, 25 Mar 2020 23:17:52 GMT</pubDate>
            <atom:updated>2020-06-05T02:50:09.845Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.lwvsf.org/police/">League of Women Voters of San Francisco</a> Observer Corps Report</p><p>Official League Observer name(s): Jennifer Wong</p><p>Location: 461 6th Ave, San Francisco, CA 94118 (Community Room — west of or behind the main building)</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p>Richmond Police District, Regularly Scheduled Community Meeting</p><p><a href="https://www.sanfranciscopolice.org/stations/richmond-station">https://www.sanfranciscopolice.org/stations/richmond-station</a></p><h4>Did you attend the whole meeting?</h4><p>Yes.</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Yes, it was completely open for public comment and it seemed adequate. There were times when it may have helped to move the meeting forward or onto other topics though.</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><p>Sgt. Jim O’Meara<br>Sgt. Lin Cueba<br>Art Campos from <a href="https://sfsafe.org/">SF SAFE</a></p><p>Yes, they were attentive and courteous. At some points, one of their radios were making noise, but then they turned them off. They paid close attention to any aired grievances and gave thoughtful responses while also trying to help solve issues.</p><p>A message was passed on by Sgt. Cueba from Capt. Jean stating that she’ll be at the next community meeting.</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>Some helpful meetings mentioned during the discussion:</p><p>Digital Device Drop-In at the Main Branch library<br>Computer Help for Seniors at Richmond Branch library (every other Wed)</p><p>Also, <a href="https://sfsafe.org/">SF SAFE</a> provides a lot of resources such as free home safety assessments for single family homes.</p><p>Two of the community members brought a box of cupcakes!</p><p>There was a lot of discussion about car break ins in the neighborhood and it felt like there was some speculation around who is involved and where the criminals come from. Some blame was placed on state proposition 47 that passed in 2014 as it classifies theft as a misdemeanor, and it was stated that officers are not allowed to pursue misdemeanors or engage in high speed chases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aaY9H_rg9QTvq48O7T764g.jpeg" /><figcaption>Richmond Police District Map</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1d3ef9d93ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-11-19-richmond-police-station-community-meeting-b1d3ef9d93ac">2019–11–19 Richmond Police Station Community Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The How, and Why, of Creating an Empathetic Design System]]></title>
            <link>https://medium.com/thinking-design/the-how-and-why-of-creating-an-empathetic-design-system-8312c335f579?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8312c335f579</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[empathy]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Mon, 19 Aug 2019 15:02:07 GMT</pubDate>
            <atom:updated>2019-08-21T11:54:12.934Z</atom:updated>
            <content:encoded><![CDATA[<h4>Software engineer Jennifer Wong explains how empathy can help shape an ever-changing, morphing design system and whom you should make it empathetic towards.</h4><p>It’s incredibly important to create design systems empathetically. Empathy can solve many frustrating problems that may arise during the creation of a new UX process. In this article, I’ll first define design systems and empathy. I’ll also describe in depth some of the key takeaways from a case study on creating design systems with little empathy, the problems that arose, and how empathy helped solve them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_M72RTH0a3zvJwkvdDdgsw.png" /><figcaption>Illustration: Justin Cheong.</figcaption></figure><h3>What are design systems?</h3><p>What is a design system? And what makes it empathetic? When you hear about design systems, you may come across the phrases, “component library,” “pattern library,” or “style guide.” Don’t let that fool you — on their own, these are not a design systems, but they are all pieces of that same puzzle.</p><p>According to <a href="https://medium.com/eightshapes-llc/defining-design-systems-6dd4b03e0ff6">Nathan Curtis</a>…</p><p>“A design system is:<br>a kit of reusable, interconnected parts,<br>a set of cohesive, interconnected products, and<br>a community of collaborative, interconnected people.”</p><p>Typically, a component library refers to a set of commonly used elements for use across an entire company. A pattern library refers to a set of design patterns for use across an entire company. And a style guide refers to static documentation that describes the design system itself, i.e. how products should look and feel, use cases for UI patterns, correct typographic scales, and more.</p><h3>What is empathy?</h3><p>Empathy is the ability to understand and share the feelings of another. It comes from the two Greek words “em” and “pathos,” which mean “in feeling.” If we look at <a href="https://books.google.com/ngrams/graph?year_start=1800&amp;year_end=2008&amp;corpus=15&amp;smoothing=7&amp;case_insensitive=on&amp;content=empathy&amp;direct_url=t4%3B%2Cempathy%3B%2Cc0%3B%2Cs0%3B%3Bempathy%3B%2Cc0%3B%3BEmpathy%3B%2Cc0">Google Books Ngram Viewer</a>, we can see that the popularity of the term “empathy” has risen in the last 70+ years. It’s unsurprising as we all try to connect more in this digital age of deep divisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Za2O6rs5bz7dKBKI.png" /></figure><h3>Putting empathy and design systems together</h3><p>What does it mean to put empathy and design systems together? Well, it means being attentive to the needs of your users who use the apps built with the design system, coworkers who use the design system, or external stakeholders who use your design system if it’s open sourced.</p><p>When discussing UX process issues with coworkers in application development, you’ll often hear answers run the gamut. Everything from testing with users, clarifying requirements with product managers and designers, collaborating between multiple feature teams, or handing off designs to engineers. Each of these is different, but note that each is related to empathy, whether that be for users or coworkers. So to help solve the UX process problems, inject a bit of empathy!</p><h3>A case study</h3><p>In my previous job, I took part in the inception of a design system. We were creating it because, in the midst of a company rebrand, it just made sense to start incorporating those new designs into a system. We also wanted to replace our existing style guide, which used an older CSS generation library called <a href="https://github.com/kneath/kss">KSS</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Ep49k0_6UA163CVB.png" /></figure><p>We dedicated an entire frontend platform team to this project. They included three of the most senior front-end engineers, three new engineers hired out of boot camps, and up to 15 designers contributing at any point in time.</p><p>Additionally, this front-end platform team made the decision to move from Backbone to React as part of the design system process.</p><h3>What we did well</h3><p><strong>File Generator</strong>: We used <a href="https://plopjs.com/">plop.js</a> to help create a set of files with each new component added to the design system, which came with the benefit of consistency in the file system and folder structure.</p><p><strong>Documentation</strong>: On the homepage of the design system, we described the atomic system used, how to contribute, and information on the component approach we took.</p><p><strong>Planned approach: </strong>In order to contribute to the design system, you had to create a document with a standard set of information.</p><p><strong>Accessibility: </strong>We used the `eslint-plugin-jsx-a11y` package to help automate some accessibility across the design system. We also paid special attention to the new modals, which can be accessibility nightmares, to ensure they were accessible as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*wOfqRpFrCQ4otajv.png" /></figure><h3>What we did… not so well</h3><p><strong>Search: </strong>The search functionality of the design system was based on the component name alone. They often say that you don’t know what you don’t know, and this was certainly true of the design system. How could you search for a component if you didn’t know what its name was?</p><p><strong>Naming things: </strong>Naming things is hard. Initially the design system was under a code name, Black Panda, which could be confusing to newcomers. Later the name was changed to the company’s design system, but was often referred to as CDS. Acronyms by their nature obfuscate what they represent. So we didn’t do much better in the name change.</p><p><strong>Deprecation: </strong>When components were deprecated, they just showed a banner that said, “Component is unstable and subject to change.” But what do “unstable” and “subject to change” mean? Should you just not use the component, or is it ok to move forward with it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*OTTa2LJcFfkjSevf.png" /></figure><p>Another time, a feature team was the first to use a component called “Text Input,” not knowing that the “Input Field” was a new fangled component that the designers created to replace the former. The feature team was delayed many weeks because they ended up tasked with the new component creation.</p><p><strong>Component confusion: </strong>We had components called Dropdown, Dropdown Menu, Select, and Select Field. It was difficult to tell what the differences between all of these were. Not only that, but the Select Field was a subcomponent of the Input Field. Again, naming things is hard.</p><p><strong>Designer inclusion: </strong>Because we moved our system to React and a component based architecture, it was more difficult for designers to make minor changes. React has a steep learning curve, and the CSS folder architecture was difficult to navigate.</p><p><strong>CSS `display` property conflicts: </strong>As part of the move into the future, the design system’s new grid system used Flexbox or `display: flex`. Unfortunately, we carried over our alignment classes, which used `display: inline-block`, a relic of the old style guide. These two would overwrite each other when used on the same component, causing weird layout issues.</p><p><strong>Release process: </strong>Only the frontend platform team could release the design system and only once a week. This meant only three engineers out of over one hundred had the ability to do so. After that, the latest version design system needed to be “bumped” in our core repository. This caused delays for product teams as they waited for new components to be available for development work on new features.</p><p>All in all, we took many missteps on our way to a design system. How did we fix these issues, and could we have avoided them altogether?</p><h3>Fixing the problems: Empathize it!</h3><p>Having empathy for coworkers was the way forward.</p><h4>Better communication</h4><p>We started Frontend Guild meetings where we could discuss things such as our grid system versus alignment classes cascade issue or up and coming components, such as the Input Field.</p><p>We stopped using code names and acronyms, and purged the code base of both.</p><h4>Clearer labeling</h4><p>A plan was hatched to create a search page with small screenshots of the components themselves. That way, anyone could search the design system at a glance. We also planned for a search with keywords across the code base rather than just component names.</p><p>We changed the wording and user interface around deprecated components to make it clear and obvious when not to use a component in the design system.</p><h4>Inclusion</h4><p>Tools such as <a href="https://reactstudio.com/">React Studio</a> and <a href="https://framer.com/">Framer</a> were introduced to help designers learn React. Both tools auto-generate <a href="https://reactjs.org/docs/introducing-jsx.html">JSX</a> based on designs created in that software.</p><p>The release process started happening twice a week. Additionally, one engineer created a bot that tagged a new engineer each time to run the release process. That way, every engineer was empowered to do so in the future.</p><h3>What should you do?</h3><p>Ask yourself: do you <em>need</em> a design system? If you don’t, start small! Build one component at a time. Don’t build ahead of your needs, or you’ll end up with components that are completely unusable when put into practice via a new feature like the Text Input.</p><p>We had a team of six engineers and up to 15 designers just for the design system. Think about what resources you have before planning a full blown design system.</p><p>And most of all, use empathy when building a design system. Consider who will be using it, contributing to it, or marketing it. Engineers, designers, product managers, marketing, or external stakeholders?</p><p>Here are some resources to help you along the way:</p><ul><li><a href="https://www.smashingmagazine.com/design-systems-book/">Design Systems</a> by Alla Kholmatova</li><li>‘<a href="https://publication.design.systems/distilling-how-we-think-about-design-systems-b26432eefef9">Distilling How We Think about Design Systems</a>’ by Sarah Federman</li><li>Video: ‘<a href="https://www.youtube.com/watch?v=1wATzhRorxQ">An Intro to Design Systems</a>’ by Sarah Federman</li><li><a href="https://storybook.js.org/examples/">Storybook</a></li></ul><p>Learn about Adobe XD, our all-in-one design and prototyping tool:</p><ul><li><a href="http://www.adobe.com/products/experience-design.html?scid=social52541916&amp;source=post_page---------------------------"><em>Download Adobe XD</em></a></li><li><a href="https://twitter.com/adobexd?source=post_page---------------------------"><em>Adobe XD Twitter account</em></a><em> — also use #adobexd to talk to the team!</em></li><li><a href="https://adobexd.uservoice.com/?source=post_page---------------------------"><em>Adobe XD UserVoice</em></a><em> ideas database</em></li><li><a href="http://www.adobe.com/go/xd_forums?source=post_page---------------------------"><em>Adobe XD forum</em></a></li></ul><p><em>Originally published at </em><a href="https://theblog.adobe.com/creating-empathetic-design-systems/"><em>https://theblog.adobe.com</em></a><em> on August 19, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8312c335f579" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thinking-design/the-how-and-why-of-creating-an-empathetic-design-system-8312c335f579">The How, and Why, of Creating an Empathetic Design System</a> was originally published in <a href="https://medium.com/thinking-design">Thinking Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–07–10 Police Commission Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-07-10-police-commission-meeting-e7ef085cde46?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7ef085cde46</guid>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[police]]></category>
            <category><![CDATA[policecommission]]></category>
            <category><![CDATA[open-government]]></category>
            <category><![CDATA[police-brutality]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Fri, 09 Aug 2019 00:29:28 GMT</pubDate>
            <atom:updated>2019-09-13T23:03:17.535Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.lwvsf.org/police/">League of Women Voters of San Francisco</a> Observer Corps Report</p><p>Official League Observer name(s): Jennifer Wong</p><p>Location: City Hall, Room 400</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p><a href="http://sanfranciscopolice.org/police-commission">San Francisco Police Commission</a>, regular.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-july-10-2019-agenda-0">Agenda</a>.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-july-10-2019-minutes">Minutes</a>.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-july-10-2019-supporting-documents-0">Supporting documents</a>.</p><h4>Did you attend the whole meeting?</h4><p>No. They went into closed session and I left at that time.</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Yes. Much of the public comment occurred after Agenda Item 3 and related to the police shooting of <a href="https://www.theguardian.com/society/2016/aug/12/luis-gongora-san-francisco-police-shooting-homelessness">Luis Gongora Pat</a>. It seemed adequate and everyone was allowed to speak.</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><p>All of the Police Commission were in attendance except Commissioner Hamasaki and Commissioner Brookter. Department of Police Accountability (DPA) Director Paul Henderson and Police Chief William Scott were also present. Additionally, Deputy Chief of Investigations Greg McCracken, Captain Sergio Chin, John Sanchez discussed Collection and Analysis of Sexual Assault Kit Evidence and Reporting of Results.</p><p>The government representatives were overall prepared, but it was announced last minute during the meeting that Agenda Item 4 regarding SB-1421 would not be addressed. Comm. DeJesus recommended it be agendized ASAP.</p><p>President Hirsch was a bit snippy with the public for commenting about Luis Gongora Pat after Agenda Item 3 instead of during general public comment.</p><p>One of the SF Sheriff Deputies present was disrespectful and audibly scoffed at some of this public comment. He and some members of the public had a verbal confrontation about shouting over Pres. Hirsch.</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>Comm. Mazzucco and Comm. Elias chaired the meeting on SB-1421. It was announced at the beginning of the meeting that the commission was skipping Agenda Item 4 addressing SB-1421 until the Working Group can meet again, to the displeasure of members of the public. The Working Group will be meeting again August 5, 1pm, <a href="https://sfgov.org/policecommission/meeting/police-commission-august-5-2019-agenda">agenda</a>.</p><p>The Police Commission is not meeting for the rest of July through beginning of August. The next meeting is scheduled for August 7, 2019.</p><p>Comm. DeJesus suggested having community members sit in and advise the Fire Arms Discharge Review Board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*DdzYkcs6RFrqEpeo5GJoBw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7ef085cde46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-07-10-police-commission-meeting-e7ef085cde46">2019–07–10 Police Commission Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–06–05 Police Commission Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-06-05-police-commission-meeting-773f9b565f73?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/773f9b565f73</guid>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[transparency]]></category>
            <category><![CDATA[policecommission]]></category>
            <category><![CDATA[police]]></category>
            <category><![CDATA[san-francisco]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 14:25:31 GMT</pubDate>
            <atom:updated>2019-09-13T23:03:38.242Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.lwvsf.org/police/">League of Women Voters of San Francisco</a> Observer Corps Report</p><p>Official League Observer name(s): Jennifer Wong</p><p>Location: City Hall, Room 400</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p><a href="http://sanfranciscopolice.org/police-commission">San Francisco Police Commission</a>, regular.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-june-5-2019-agenda">Agenda</a>.</p><p>Minutes are not yet available, <a href="https://sfgov.org/policecommission/meetings/19">but will be posted here</a>.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-june-5-2019-supporting-documents">Supporting documents</a>.</p><h4>Did you attend the whole meeting?</h4><p>Yes.</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Yes. It happened multiple times.</p><p>After agenda 3a-3d (Reports to the Commission), several members of the public stood including a member of the United Public Workers commented on the illegal monitoring of a journalist Bryan Carmody’s phone and the illegal raiding of his home. Two representatives of Officers for Justice stood up to state their support of Police Chief Scott.</p><p>During agenda item 6 (general public comment), multiple law students, and representatives and interns of the Public Defenders Office stood to voice their support for SB1421 and disappointment in the delay of receiving requested police record documentation. Magick Altman also stood to address the Sunshine Ordinance Task Force’s ruling that the commission’s vote on adding tasers to the police use of force policy was illegal.</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><ul><li>Vice President Damali Taylor</li><li>Commissioner Petra DeJesus</li><li>Commissioner Thomas Mazzucco</li><li>Commissioner Cindy Elias</li><li>Commission Dion-Jay Brookter</li><li>Police Chief William Scott</li><li>Head of Department of Police Accountability, Paul Henderson</li></ul><p>The commissioners and those in the police department were overall prepared, but there were documents some of the commissioners did not receive, i.e. Bulletin 19–092 addressed in agenda item 4, or that speakers did not have, i.e. the memo in supporting documents Re: First Quarter, 1st Session 2019 Firearm Discharge Review Board Findings and Recommendations.</p><p>There was some underlying issue between Commissioner DeJesus and Elias, and President Hirsch and Vice President Taylor regarding the use of the Police Commission letterhead and leadership’s ability to represent the entire commission in this way.</p><p>Deputy Chief Gregory Yee and Deputy Chief Ann Mannix of Firearms Discharge Review Board were there to discuss Q1 2019 Officer Involved Shootings (OIS) and Officer Involved Discharge (OID).</p><p>A representative for the Early Intervention System was there to discuss Q1 2019 numbers, which have been improving.</p><p>Assistant Chief Robert Moser was there to discuss agenda item 4 (Dept. Bulletin 19–092, Investigative Services Detail name change from Internal Affairs — Criminal Unit.</p><p>Lt. Dave Falzon was there to discuss agenda item 5 (issuance of Dept. Bulletin 19–101, Outside Agency Courtesy Reports, modifying DGO 5.11).</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>There were lots of questions regarding the Office Involved Shooting (OIS) Memorandum of Understanding(MOU) from the commissioners — it seems like there will be more discussion especially related to commission involvement until this is approved.</p><p>Agenda item 4 was not passed. Agenda item 5 was passed.</p><p>The June 19 commission meeting will take place at Park Station and not at City Hall. The July 10 meeting is where the commission will address SB1421 and related issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*DdzYkcs6RFrqEpeo5GJoBw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=773f9b565f73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-06-05-police-commission-meeting-773f9b565f73">2019–06–05 Police Commission Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–04–30 Mission Police Station Community Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-04-30-mission-police-station-community-meeting-9cb2702c035f?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cb2702c035f</guid>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[mission]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Thu, 16 May 2019 16:32:36 GMT</pubDate>
            <atom:updated>2019-06-07T15:39:13.405Z</atom:updated>
            <content:encoded><![CDATA[<p>General Member of the Public Report</p><p>Observer name(s): Jennifer Wong</p><p>Location: 630 Valencia St, San Francisco, CA 94110 (Community Room)</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p><a href="http://sanfranciscopolice.org/mission-station">Mission Police District</a>, Regularly Scheduled Community Meeting</p><h4>Did you attend the whole meeting?</h4><p>Yes.</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Yes. It happened throughout the meeting and many people including local citizens spoke. There were many opportunities to make public comments and also interact with the officers and government officials who were present.</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><p>Captain Gaetano Caltagirone, a sergeant, and a lieutenant from the Mission precinct. They were attentive, prepared, and courteous. They listened attentively to the public comments, addressed them, and offered to stay in touch. Capt. Caltagirone also shared his email address with the entire room. He was good about asking clarifying questions of guest speakers to help the audience understand as well.</p><p>Also, Vivian Mendoza from Department of Emergency Management (DEM), who was also attentive, prepared, and courteous. She addressed questions and answered them thoroughly.</p><p>Lastly, Dr. Claude Hemphill, Chief of Neurology at SF General Hospital was prepared, courteous, and answered any questions that the community had.</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>The captain, sergeant, and lieutenants all addressed gang violence in the district. Vivian Mendoza discussed emergency preparedness and how to get alerts on issues around the city and how to make the correct calls to 911, 311, or a non emergency police line. Dr. Hemphill discussed a research study called BOOST, Brain Oxygen Optimization in Severe Traumatic and getting community opinion on how patients are enrolled in that study.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*ejqqATWzBgEU5OR-M6p7Cg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cb2702c035f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-04-30-mission-police-station-community-meeting-9cb2702c035f">2019–04–30 Mission Police Station Community Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–05–08 San Francisco Police Commission Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-05-08-san-francisco-police-commission-meeting-e1ecaa800839?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1ecaa800839</guid>
            <category><![CDATA[policecommission]]></category>
            <category><![CDATA[police-brutality]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Thu, 16 May 2019 16:24:58 GMT</pubDate>
            <atom:updated>2019-09-13T23:04:07.919Z</atom:updated>
            <content:encoded><![CDATA[<p>General Member of the Public Report</p><p>Observer name(s): Jennifer Wong</p><p>Location: City Hall, Room 400</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p><a href="http://sanfranciscopolice.org/police-commission">San Francisco Police Commission</a>, regular.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-may-8-2019-agenda">Agenda.</a></p><p>Minutes are not yet available, <a href="https://sfgov.org/policecommission/meetings/19">but will be posted here</a>.</p><p><a href="https://sfgov.org/policecommission/meeting/police-commission-may-8-2019-supporting-documents">Supporting documents.</a></p><h4>Did you attend the whole meeting?</h4><p>From the beginning until the Closed Session.</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Yes. It happened for agenda item 5 (Discussion and possible action on the release of certain police officer records pursuant to Senate Bill 1421 that would apply to the Police Commission, Police Department, and Department of Police Accountability), after agenda items 3a-3d (Chief’s Report and DPA Director’s Report) were completed, as part of agenda item 6 (General Public Comment), and no comments were made but was open for public comment after agenda item 7 (Public comment on all matters pertaining to Item 9 below, Closed Session, including public comment on Item 8, vote whether to hold Item 9 in closed session.). Each speaker was given 2 minutes to speak and that seemed adequate. About two people spoke after agenda item 5, six people after agenda items 3a-3d, and one after agenda item 7.</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><p>All of the commissioners, Paul Henderson, Executive Director of the Dept. of Police Accountability (DPA), and Police Chief William Scott, Police Cmd. Bob Moser, Sgt. Maura Pengel, and Sgt. Art Howard. They were attentive, prepared, and mostly courteous. There was a bit of heated discussion around agenda items 3a, 3b, and 5.</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>It was concluded that agenda item 5 would be revisited for both public comment, presentations, and to give police fair warning about this discussion. Item 4 will be discussed after the commission is presented with an MOU. There is concern over the fact that DPA has only published one report this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*DdzYkcs6RFrqEpeo5GJoBw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1ecaa800839" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-05-08-san-francisco-police-commission-meeting-e1ecaa800839">2019–05–08 San Francisco Police Commission Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019–02–24 San Francisco Police Commission Meeting]]></title>
            <link>https://medium.com/lwvsf-observer-corps/2019-02-24-san-francisco-police-commission-meeting-20b9c3143bb3?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/20b9c3143bb3</guid>
            <category><![CDATA[policecommission]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[transparency]]></category>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[police]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Tue, 23 Apr 2019 04:35:46 GMT</pubDate>
            <atom:updated>2019-05-09T05:43:43.086Z</atom:updated>
            <content:encoded><![CDATA[<h3>2019–02–20 San Francisco Police Commission Meeting</h3><p>General Member of the Public Report</p><p>Observer name(s): Jennifer Wong</p><p>Location: City Hall, Room 400</p><h4>What meeting did you attend (name of the body, whether it was a regular or special meeting, etc)?</h4><p><a href="http://sanfranciscopolice.org/police-commission">San Francisco Police Commission,</a> regular</p><p><a href="https://sanfranciscopolice.org/meeting/police-commission-february-20-2019-agenda">Agenda</a></p><p><a href="https://sanfranciscopolice.org/meeting/police-commission-february-20-2019-supporting-documents">Supporting documents</a></p><h4>Did you attend the whole meeting?</h4><p>Yes, all the portions the public could attend</p><h4>Tell us about public input: Did it happen? How was it conducted? Did it seem adequate?</h4><p>Public input did happen. It was conducted per agenda items and each individual was given two minutes to speak. It seemed adequate. People commented about: Contract with Matrix Consulting (methodology used) Complaints about officers handling of those with mental illness and a need for a mental health team in lieu of police What is “proactive time” related to stop and frisk? The death of a neighbor downstairs and someone running a “dope house” there — this community member was referred to speak with Lt. Yamaguchi at the meeting. Motions brought by the commissioners, such as accepting the findings of Sunshine Ordinance Task Force (SOTF) Mayor Breed’s sudden support of tasers after taking office The vote on Proposition H from June 2018 against the use of tasers</p><h4>Tell us about the government: Who was there? Were they attentive? Were they prepared? Were they courteous with each other and the public?</h4><p>Representing the Police Commission: President Hirsch, Vice President Taylor, Commissioners Brookter, DeJesus, Elias, and Hamasaki. Police Chief William Scott and Director Henderson of Department of Police Accountability (DPA) They were attentive and prepared. They were overall courteous to each other and the public. There were, however, instances when President Hirsch seemed irate and was curt with people in the public as well as fellow commissioners.</p><h4>Want to tell us anything else (about the process used, the content of the meeting, decisions made, adherence to laws and regulations, etc)?</h4><p>There were updates on the Staffing Task Force resolution. The First Amendment video is a decade out of date and to be updated. There will be an upcoming agenda item regarding a reported robbery and 4 hour wait time until police arrived, possibly due to a language barrier, which was discussed with Chief Scott. The next Police Commission meeting is March 6th at 5:30pm, City Hall, Room 400.</p><p>Item 4: DGO 2.04, discussion that an MOU is more difficult to amend and that the Department of Police Accountability (DPA) shouldn’t have to comply with Administrative Investigations Unit (IAD) because they don’t have access to the IAD file or subpoena power. PDA should have access to full investigative files when it comes to complaints, but should not be swayed by the conclusion of the San Francisco Police Department (SFPD) or IAD. There was a motion to remove the second paragraph of Part 6 which failed. President Hirsch said that the document should go back to Committee.</p><p>Item 5: Commissioner DeJesus discusses the findings of Sunshine Ordinance Task Force (SOTF), The Brown Act, and the decision to add Tasers to use of force policy by the Police Commission. She said she was there, they moved from office to office hiding, she could see that the building was closed for longer than 15 mins, were not let back in after getting food, pushing to be transparent, Tasers cannot be used against mentally disabled, need to retake the vote, error should be fixed, President Hirsch also discusses this, says that no business was discussed outside of the meeting and a sign was put on the door of the original room to inform the public. He states that members of the public were escorted up to the new room by the Sheriff’s department and that the public was limited to 2 mins of comment. He states that the SOTF was incorrect in ruling re: that, saying the blocking of access can’t be pinned on the commission and should be put into the Sheriff who handles security, the previous President passed away before being able to comment on the SOTF letter, meeting in Nov letter in Jun, Commissioner DeJesus raises a motion to accept the SOTF ruling and retake the vote regarding tasers. The motion dies because it lacked a second vote. She then raises a motion to accept SOTF, comply with the Brown act, and ensure transparency, resolve to do better in the future, and rescind the vote until the Police Commission if fully compliant. There is a bit of an argument between President Hirsch, and Comm. DeJesus and Comm. Hamasaki on the ability to amend the motion. They discuss with Assistant City Attorney, who states that the motion must be specifically related to agenda items. In the end, they allow the motion to rescind the taser vote so the commission can do due diligence, allowing time as a new commission to study up and make a vote. A vote is taken on the second motion fails 3–3 with DeJesus, Elias, and Hamasaki AYE, Brookter, Hirsch, and Taylor, NAY.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*txoDdNWa_YBfZCoKQcvBOQ.jpeg" /><figcaption>Gavel</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20b9c3143bb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lwvsf-observer-corps/2019-02-24-san-francisco-police-commission-meeting-20b9c3143bb3">2019–02–24 San Francisco Police Commission Meeting</a> was originally published in <a href="https://medium.com/lwvsf-observer-corps">LWVSF Observer Corps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Catch-22 of Being “Too Junior”]]></title>
            <link>https://medium.com/@mybluewristband/the-catch-22-of-being-too-junior-43af002958c?source=rss-cdafa7d9387c------2</link>
            <guid isPermaLink="false">https://medium.com/p/43af002958c</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Jennifer Wong]]></dc:creator>
            <pubDate>Mon, 01 Jun 2015 19:31:50 GMT</pubDate>
            <atom:updated>2015-06-02T21:13:14.981Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently I was laid off for being “too junior” after four months of work. The company’s founders said they’d be replacing me with someone “more senior”. I asked for feedback on my performance. They said there were no complaints — I was just too junior. When I prodded for more, the founders told me that they just needed someone more senior.</p><p>Throughout my time at said company, I expressed insecurity about my abilities. Coworkers (including the founders) alleviated my worries by saying that they knew I was “junior” when they hired me and expected me to build up my skills while working at the company.</p><p>My reviews were consistently good with minor feedback about what skills I should focus on. I spent time inside work completing my assigned tasks and outside work trying to learn those skills to better my working knowledge.</p><p>After the layoff, I spent time asking myself what I could have done better and why they hired me in the first place if I was “too junior”. And then I realized I hit upon a catch-22. Without a job, I can’t gain more working experience. But without that working experience, I can’t get a job. So where do I go from here?</p><p>I decided that rather than question what went wrong, I would focus on what could be done right. So here is my advice on what to do (and don’t) when thinking about hiring a junior developer.</p><h4><strong>Consider Your Resources</strong></h4><p><em>Don’t hire a junior developer if you don’t plan on investing in their future. </em>What happened to the idea of apprenticeship? The idea of training an inexperienced worker and helping them build their career. When you hire a developer, imagine yourself working with them for the long haul and helping to shape their future at the company.</p><p><em>Don’t hire a junior developer if you don’t have the resources to mentor them. </em>I cannot emphasize this enough — do <strong><em>NOT</em></strong> hire a junior developer if you do not have resources to do so. If members of your team cannot take 5–10 minutes a few times a day to sit down and explain a problem or concept, you do not have the resources.</p><p><em>Don’t hire a junior developer if you can’t afford the time expense. </em>People still in the process of learning new skills go slowly. If you’re in a time critical situation, make sure to account for the extra time it might take for a new developer to understand new concepts.</p><h4><strong>Do It For the Right Reasons</strong></h4><p><em>Don’t hire a junior developer as a marketing effort or PR stunt. </em>This reason only considers your company’s best interests rather than those of the candidate. If you’re doing this, you probably haven’t read anything I mention above or below this paragraph.</p><p><em>Don’t hire a junior developer to do your grunt work. </em>Doing so will prevent them from learning… anything. If you consistently assign the same type of work (especially boring or undesirable work) to one person, they’re unlikely to develop new abilities <em>and</em> unlikely to stay at your company. Giving new developers projects that aren’t time sensitive and just outside their comfort zone is one of the best ways for them to learn.</p><h4>Be Prepared</h4><p><em>Do assess what “junior” means to you and your company. </em>The term “junior” is used loosely and widely in the tech industry. But there’s no standard skill set that describes this title. Try creating a standard or list of skills that your developers need which you can compare potential candidates against. That way, you’ll have a better sense of what level of developers you can hire.</p><p><em>Do set up, at the very least, a loose mentorship program to ensure your developers are learning. </em>Pair programming is a great way to help both novice and expert developers grow their knowledge. Short workshops or lectures can supplement any learnings from day to day tasks. Scheduling set times for such activities and regular check-ins provides structure and assurance that your new programmer is developing new expertise.</p><p><em>Do have a support system in place for your developers. </em>When a developer has a question, who should they go to? Whether it’s a person, group, or team on rotation, establishing a support system will increase the collaboration and flow of ideas. Developers should never feel too scared to ask questions, so make it a point to ensure someone is always available.</p><p>If there’s a shortage of developers in the tech industry, what do we do? The pool of existing “senior” developers is fixed, so you can’t just continuously try to recruit them away from their existing positions.</p><p>We’re just going to have to <em>make</em> senior developers. Following the above advice puts you on the path towards hiring and cultivating junior developers the right way. By doing so, you provide solutions to both sides of the Catch-22 — a job to gain experience and experience to gain (and keep) a job. It takes patience and dedication, but it’s worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43af002958c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>