<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: shi warren</title>
    <description>The latest articles on DEV Community by shi warren (@shi_warren_01ffb98ae5d415).</description>
    <link>https://dev.to/shi_warren_01ffb98ae5d415</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3922196%2F08d1e44b-ced3-418d-8627-8d790b70dadb.jpg</url>
      <title>DEV Community: shi warren</title>
      <link>https://dev.to/shi_warren_01ffb98ae5d415</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shi_warren_01ffb98ae5d415"/>
    <language>en</language>
    <item>
      <title>AI makes building faster, but semantic distribution is now the hard part</title>
      <dc:creator>shi warren</dc:creator>
      <pubDate>Thu, 21 May 2026 04:49:33 +0000</pubDate>
      <link>https://dev.to/shi_warren_01ffb98ae5d415/ai-makes-building-faster-but-semantic-distribution-is-now-the-hard-part-3jc1</link>
      <guid>https://dev.to/shi_warren_01ffb98ae5d415/ai-makes-building-faster-but-semantic-distribution-is-now-the-hard-part-3jc1</guid>
      <description>&lt;p&gt;Shipping products feels dramatically easier now.&lt;/p&gt;

&lt;p&gt;Between AI coding tools, templates, and browser-side tooling, I can build and deploy things faster than ever.&lt;/p&gt;

&lt;p&gt;But distribution feels harder.&lt;/p&gt;

&lt;p&gt;Not technically harder.&lt;/p&gt;

&lt;p&gt;Semantically harder.&lt;/p&gt;

&lt;p&gt;A lot of the work now is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;understanding how users actually search&lt;/li&gt;
&lt;li&gt;matching workflows instead of technical terms&lt;/li&gt;
&lt;li&gt;figuring out where intent really exists&lt;/li&gt;
&lt;li&gt;building trust before distribution channels suppress you&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Building became compressed.&lt;/p&gt;

&lt;p&gt;Attention became fragmented.&lt;/p&gt;

&lt;p&gt;Honestly feels like distribution is becoming the real product skill now.&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>ai</category>
      <category>webdev</category>
      <category>seo</category>
    </item>
    <item>
      <title>Most people search “remove location from photo”, not “EXIF”</title>
      <dc:creator>shi warren</dc:creator>
      <pubDate>Fri, 15 May 2026 08:49:20 +0000</pubDate>
      <link>https://dev.to/shi_warren_01ffb98ae5d415/most-people-search-remove-location-from-photo-not-exif-5186</link>
      <guid>https://dev.to/shi_warren_01ffb98ae5d415/most-people-search-remove-location-from-photo-not-exif-5186</guid>
      <description>&lt;p&gt;Most people search “remove location from photo”, not “EXIF”&lt;/p&gt;

&lt;p&gt;While building a metadata removal workflow, I realized something interesting:&lt;/p&gt;

&lt;p&gt;Most people never search for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;EXIF&lt;/li&gt;
&lt;li&gt;IPTC&lt;/li&gt;
&lt;li&gt;document properties&lt;/li&gt;
&lt;li&gt;metadata&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;They search for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;“remove location from photo”&lt;/li&gt;
&lt;li&gt;“hidden info in PDF”&lt;/li&gt;
&lt;li&gt;“remove GPS from image”&lt;/li&gt;
&lt;li&gt;“does this file still contain private data?”&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The technical layer and the user intent layer are often completely different.&lt;/p&gt;

&lt;p&gt;Developers think in systems.&lt;/p&gt;

&lt;p&gt;Users think in outcomes.&lt;/p&gt;

&lt;p&gt;That changed how I started thinking about both SEO and product design.&lt;/p&gt;

&lt;p&gt;A lot of users are not trying to “inspect metadata”.&lt;/p&gt;

&lt;p&gt;They’re usually just at the moment before sharing something publicly and wondering:&lt;/p&gt;

&lt;p&gt;“wait… is there still something hidden in this file?”&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>metadata</category>
      <category>seo</category>
    </item>
    <item>
      <title>Your photos may still contain GPS metadata after editing</title>
      <dc:creator>shi warren</dc:creator>
      <pubDate>Sat, 09 May 2026 17:09:15 +0000</pubDate>
      <link>https://dev.to/shi_warren_01ffb98ae5d415/your-photos-may-still-contain-gps-metadata-after-editing-242b</link>
      <guid>https://dev.to/shi_warren_01ffb98ae5d415/your-photos-may-still-contain-gps-metadata-after-editing-242b</guid>
      <description>&lt;p&gt;A lot of people assume cropping, resizing, or screenshotting a photo removes hidden information.&lt;/p&gt;

&lt;p&gt;That’s often not true.&lt;/p&gt;

&lt;p&gt;Many images still contain metadata like:&lt;/p&gt;

&lt;p&gt;GPS location&lt;br&gt;
device information&lt;br&gt;
timestamps&lt;br&gt;
camera details&lt;br&gt;
EXIF data&lt;/p&gt;

&lt;p&gt;In some cases that can unintentionally expose:&lt;/p&gt;

&lt;p&gt;where a photo was taken&lt;br&gt;
what device was used&lt;br&gt;
when it was captured&lt;/p&gt;

&lt;p&gt;I started noticing this more while working with:&lt;/p&gt;

&lt;p&gt;screenshots&lt;br&gt;
AI-generated images&lt;br&gt;
product demos&lt;br&gt;
travel photos&lt;br&gt;
shared work files&lt;/p&gt;

&lt;p&gt;One thing that surprised me is how many people don’t realize metadata exists until they accidentally leak something.&lt;/p&gt;

&lt;p&gt;Privacy tooling on the internet still feels mostly reactive instead of preventative.&lt;/p&gt;

&lt;p&gt;I think lightweight browser-side privacy workflows will become much more important as AI-generated and shared content keeps increasing.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>security</category>
      <category>metadata</category>
    </item>
    <item>
      <title>How to Convert JSON to Excel Online</title>
      <dc:creator>shi warren</dc:creator>
      <pubDate>Sat, 09 May 2026 17:04:37 +0000</pubDate>
      <link>https://dev.to/shi_warren_01ffb98ae5d415/how-to-convert-json-to-excel-online-4l84</link>
      <guid>https://dev.to/shi_warren_01ffb98ae5d415/how-to-convert-json-to-excel-online-4l84</guid>
      <description>&lt;p&gt;JSON is great for APIs and structured data, but reviewing large responses in raw format gets painful fast.&lt;/p&gt;

&lt;p&gt;I kept running into this while debugging APIs, checking exported records, and reviewing nested logs.&lt;/p&gt;

&lt;p&gt;Most of the time, I didn’t actually need the raw JSON. I needed something readable.&lt;/p&gt;

&lt;p&gt;Converting JSON into a spreadsheet ended up being the fastest workflow for things like:&lt;/p&gt;

&lt;p&gt;API debugging&lt;br&gt;
exported records&lt;br&gt;
nested logs&lt;br&gt;
sharing structured data with non-technical teams&lt;/p&gt;

&lt;p&gt;One thing I noticed is that nested JSON matters a lot more than people expect. A lot of converters technically work, but still leave deeply nested fields unreadable.&lt;/p&gt;

&lt;p&gt;So I built a lightweight browser-side workflow for flattening JSON into readable spreadsheet columns.&lt;/p&gt;

&lt;p&gt;It supports:&lt;/p&gt;

&lt;p&gt;JSON → XLSX&lt;br&gt;
nested JSON flattening&lt;br&gt;
browser-side processing&lt;br&gt;
no signup&lt;/p&gt;

&lt;p&gt;I also added XLS export because some older Excel workflows still depend on it.&lt;/p&gt;

</description>
      <category>json</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
