<?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: Anton Zaharenko</title>
    <description>The latest articles on DEV Community by Anton Zaharenko (@anton_zaharenko).</description>
    <link>https://dev.to/anton_zaharenko</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4008716%2Fde67ba1b-34e0-4c93-be05-b908a14f2032.jpg</url>
      <title>DEV Community: Anton Zaharenko</title>
      <link>https://dev.to/anton_zaharenko</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/anton_zaharenko"/>
    <language>en</language>
    <item>
      <title>New CSS Units: svh, lvh, and dvh</title>
      <dc:creator>Anton Zaharenko</dc:creator>
      <pubDate>Thu, 02 Jul 2026 15:11:35 +0000</pubDate>
      <link>https://dev.to/anton_zaharenko/new-css-units-svh-lvh-and-dvh-544</link>
      <guid>https://dev.to/anton_zaharenko/new-css-units-svh-lvh-and-dvh-544</guid>
      <description>&lt;p&gt;For a long time, using 100vh seemed like the perfect solution for responsive layouts.&lt;br&gt;
But on mobile devices, things turned out to be more complicated: &lt;br&gt;
dynamic browser address bars would shrink the viewport, &lt;br&gt;
causing layouts to jump unexpectedly.&lt;/p&gt;

&lt;p&gt;To fix this, CSS introduced three new units:&lt;br&gt;
svh measures the viewport height immediately after the page loads.&lt;br&gt;
lvh represents the maximum available viewport height, for example, after the address bar collapses.&lt;br&gt;
dvh reflects the real-time dynamic viewport height as the user interacts with the page.&lt;/p&gt;

&lt;p&gt;With these updates, responsive layouts are more stable, content no longer shifts unexpectedly on mobile, and the user experience is significantly improved.&lt;/p&gt;

&lt;p&gt;If you want your websites to feel polished and professional across all devices, it is time to start using these new units.&lt;/p&gt;

&lt;h1&gt;
  
  
  CSS #Frontend #WebDevelopment #ResponsiveDesign
&lt;/h1&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd0smdqoohocpz893nh1p.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd0smdqoohocpz893nh1p.jpeg" alt=" " width="800" height="511"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>I built a Chrome extension</title>
      <dc:creator>Anton Zaharenko</dc:creator>
      <pubDate>Tue, 30 Jun 2026 08:25:51 +0000</pubDate>
      <link>https://dev.to/anton_zaharenko/i-built-a-chrome-extension-nn0</link>
      <guid>https://dev.to/anton_zaharenko/i-built-a-chrome-extension-nn0</guid>
      <description>&lt;p&gt;I built a Chrome extension that extracts code from tutorial &lt;br&gt;
videos using Claude's Vision API. Wrote up what I learned:&lt;/p&gt;

&lt;p&gt;Key findings:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Vision models handle code extraction surprisingly well better than OCR for anything syntax-sensitive&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Prompt engineering matters more than model choice. &lt;br&gt;
"Extract the code" vs "identify all code blocks, preserve &lt;br&gt;
indentation, differentiate from terminal output" huge &lt;br&gt;
difference in quality&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Latency: ~2-3 seconds for a 1080p frame. Acceptable for &lt;br&gt;
this use case, too slow for real-time&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Edge case: slides with code + screenshots of code — &lt;br&gt;
model correctly identifies both as "code" even with &lt;br&gt;
different visual styling&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Full writeup with prompt examples: [link to dev.to article]&lt;/p&gt;

&lt;p&gt;The extension itself is free if anyone wants to try the &lt;br&gt;
output quality: &lt;a href="https://codera.click/" rel="noopener noreferrer"&gt;codera.click&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>showdev</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
