<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Case studies on Andy Gongea — Product Designer</title>
		<link>https://gongea.com/work/</link>
		<description>Recent content in Case studies on Andy Gongea — Product Designer</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>© {year} Andy Gongea</copyright>
		
		
			<atom:link href="https://gongea.com/work/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Color Forklift</title>
				<link>https://gongea.com/work/color-forklift/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://gongea.com/work/color-forklift/</guid>
				<description>&lt;section class=&#34;chapter&#34; id=&#34;problem&#34; aria-labelledby=&#34;problem-h&#34;&gt;&#xA;  &lt;span class=&#34;chapter-head label&#34;&gt;01 · The problem&lt;/span&gt;&#xA;  &lt;h2 id=&#34;problem-h&#34;&gt;Even steps in HSL don&amp;#39;t look even to people.&lt;/h2&gt;&#xA;&lt;div class=&#34;prose&#34;&gt;&#xA;&lt;p&gt;A color scale looks simple: pick a base color, then generate lighter and darker steps. Most generators do that in HSL, and HSL isn&amp;rsquo;t perceptually uniform. Yellows wash out, blues turn muddy, and a &lt;code&gt;500&lt;/code&gt; in one hue looks heavier than a &lt;code&gt;500&lt;/code&gt; in another.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Iveeo</title>
				<link>https://gongea.com/work/iveeo/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://gongea.com/work/iveeo/</guid>
				<description>&lt;section class=&#34;chapter&#34; id=&#34;problem&#34; aria-labelledby=&#34;problem-h&#34;&gt;&#xA;  &lt;span class=&#34;chapter-head label&#34;&gt;01 · The problem&lt;/span&gt;&#xA;  &lt;h2 id=&#34;problem-h&#34;&gt;Recording your screen shouldn&amp;#39;t come with a list of conditions.&lt;/h2&gt;&#xA;&lt;div class=&#34;prose&#34;&gt;&#xA;&lt;p&gt;Recording a quick demo shouldn&amp;rsquo;t require choosing a subscription. Yet every option I looked at charged something: money, features, privacy or an account. I wrote the conditions down and designed the product to remove every one of them.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Snyk Code</title>
				<link>https://gongea.com/work/snyk-code/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://gongea.com/work/snyk-code/</guid>
				<description>&lt;section class=&#34;chapter&#34; id=&#34;merge&#34; aria-labelledby=&#34;merge-h&#34;&gt;&#xA;  &lt;span class=&#34;chapter-head label&#34;&gt;01 · Launch&lt;/span&gt;&#xA;  &lt;h2 id=&#34;merge-h&#34;&gt;Two cultures, one product, in under five months.&lt;/h2&gt;&#xA;&lt;div class=&#34;prose&#34;&gt;&#xA;&lt;p&gt;DeepCode was a small, research-led startup. Snyk was an established scale-up with its own platform, patterns and customers. Merging the two was hard at times, and it paid off. We had to turn DeepCode&amp;rsquo;s engine into a product that felt native to Snyk, and we had one release window to do it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Update Now</title>
				<link>https://gongea.com/work/update-now/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://gongea.com/work/update-now/</guid>
				<description>&lt;div class=&#34;prose&#34;&gt;&#xA;&lt;p&gt;Checking for outdated packages usually means leaving the editor: run a command, read a table, then edit version numbers by hand. Update Now puts that information in the manifest itself. A label above each dependency shows whether the update is a &lt;strong&gt;patch&lt;/strong&gt;, &lt;strong&gt;minor&lt;/strong&gt; or &lt;strong&gt;major&lt;/strong&gt; change, so the risk is visible before you click. Clicking applies the update and keeps your &lt;code&gt;^&lt;/code&gt; or &lt;code&gt;~&lt;/code&gt; prefix.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
