<?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: 0byte</title>
    <description>The latest articles on DEV Community by 0byte (@0byte).</description>
    <link>https://dev.to/0byte</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%2F3750706%2Fd27b1b5b-ba82-40b5-8d2c-38bed405d805.jpg</url>
      <title>DEV Community: 0byte</title>
      <link>https://dev.to/0byte</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/0byte"/>
    <language>en</language>
    <item>
      <title>The Shape of a Neuron — Weights, Bias and Activation Functions Explained Visually</title>
      <dc:creator>0byte</dc:creator>
      <pubDate>Wed, 03 Jun 2026 10:39:39 +0000</pubDate>
      <link>https://dev.to/0byte/the-shape-of-a-neuron-weights-bias-and-activation-functions-explained-visually-3ioe</link>
      <guid>https://dev.to/0byte/the-shape-of-a-neuron-weights-bias-and-activation-functions-explained-visually-3ioe</guid>
      <description>&lt;p&gt;The word “neuron” in machine learning can make the whole thing sound unnecessarily complex. But when you build it step by step, the idea becomes surprisingly geometric.&lt;/p&gt;

&lt;p&gt;In this video I explore neural networks from a geometric perspective. We start with a single neuron and build an intuition for weights, bias, decision boundaries, and activation functions by visualising them as surfaces moving through an input space.&lt;/p&gt;

&lt;p&gt;Instead of treating activation functions as formulas to memorise, we look at what they do to the geometry. Why does a sigmoid produce probabilities? Why does ReLU behave differently? What exactly is a decision boundary, and what is the neuron actually deciding?&lt;/p&gt;

&lt;p&gt;Topics covered:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Affine transformations&lt;br&gt;
Input space and decision boundaries&lt;br&gt;
The geometric interpretation of a neuron&lt;br&gt;
Binary Step, Sigmoid, tanh, ReLU, Leaky ReLU, ELU, Swish, and GELU&lt;br&gt;
How training moves and rotates boundaries through space&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;My experience learning machine learning is that intuition usually comes before terminology. Once you can see the geometry, the equations stop feeling like magic.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>llm</category>
    </item>
    <item>
      <title>I've Been Using This Word My Entire Career</title>
      <dc:creator>0byte</dc:creator>
      <pubDate>Sat, 18 Apr 2026 11:32:38 +0000</pubDate>
      <link>https://dev.to/0byte/ive-been-using-this-word-my-entire-career-485k</link>
      <guid>https://dev.to/0byte/ive-been-using-this-word-my-entire-career-485k</guid>
      <description>&lt;p&gt;As a person who went through many phases, 3d graphic, real-time engines, programming and now AI, I noticed that there is a plethora of words that persist through these fields. At the very fundamental level, they might describe the same thing, but they are abstracted into a unique, niche fitting idea.&lt;/p&gt;

&lt;p&gt;That's why, depending on your expertise you'll understand the word "model" differently. Mostly because you see it through a different abstraction or you use models in a conceptually different way. A model can be used as a predictive tool but it can also be used as a descriptor. Is some cases it's also prescriptive.&lt;/p&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.amazonaws.com%2Fuploads%2Farticles%2F3hrvaav9cmd5vnshtaat.png" 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.amazonaws.com%2Fuploads%2Farticles%2F3hrvaav9cmd5vnshtaat.png" alt=" " width="800" height="390"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  3D MODEL – MY FIRST MODEL!
&lt;/h1&gt;

&lt;p&gt;If you're a 3D Modeller working in Blender, 3Ds Max or other tool, you see a mesh that can be deformed, textured, animated or rendered. That all it was for me. Something I look at and manipulate with instant feedback.&lt;/p&gt;

&lt;p&gt;At some point I got involved in interactive applications and worked alongside Unity (a real time engine) engineers. I realised “model” meant something completely else to them. They were asking about vertex orders and weights. Flipped normals, gizmos that weren’t matching Unity coordination system. (Damn you, right-hand coordinate system!). Model wasn’t a visual thing for them. It was a weird combo of constraints and very specific properties.&lt;/p&gt;

&lt;p&gt;Then I talked to graphic programmers. The world I knew shattered to pieces. Literally. Those solid-looking shapes I'd been happily pushing and pulling for years? Not solid. Not even connected. Just points in 3D space, grouped into triangles, moving together while remaining fundamentally separate. The mesh - the thing I thought I understood completely - was an illusion the renderer was constructing 30+ times a second.&lt;/p&gt;

&lt;p&gt;At this point there wasn’t even a model. It was trigonometry.&lt;/p&gt;

&lt;p&gt;Read Mode: &lt;a href="https://0byte.io/articles/many_meanings_of_model.html" rel="noopener noreferrer"&gt;https://0byte.io/articles/many_meanings_of_model.html&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>tech</category>
    </item>
    <item>
      <title>Many Meanings of the Word Model</title>
      <dc:creator>0byte</dc:creator>
      <pubDate>Thu, 19 Mar 2026 22:54:48 +0000</pubDate>
      <link>https://dev.to/0byte/many-meanings-of-the-word-model-pej</link>
      <guid>https://dev.to/0byte/many-meanings-of-the-word-model-pej</guid>
      <description>&lt;p&gt;As a person who went through many phases, 3d graphic, real-time engines, programming and now AI, I noticed that there is a plethora of words that persist through these fields. At the very fundamental level, they might describe the same thing, but they are abstracted into a unique, niche fitting idea.&lt;/p&gt;

&lt;p&gt;That's why, depending on your expertise you'll understand the word "model" differently. Mostly because you see it through a different abstraction or you use models in a conceptually different way. A model can be used as a predictive tool but it can also be used as a descriptor. Is some cases it's also prescriptive.&lt;/p&gt;

&lt;h2&gt;
  
  
  3D MODEL – MY FIRST MODEL!
&lt;/h2&gt;

&lt;p&gt;If you're a 3D Modeller working in Blender, 3Ds Max or other tool, you see a mesh that can be deformed, textured, animated or rendered. That all it was for me. Something I look at and manipulate with instant feedback.&lt;/p&gt;

&lt;p&gt;At some point I got involved in interactive applications and worked alongside Unity (a real time engine) engineers. I realised “model” meant something completely else to them. They were asking about vertex orders and weights. Flipped normals, gizmos that weren’t matching Unity coordination system. (Damn you, right-hand coordinate system!). Model wasn’t a visual thing for them. It was a weird combo of constraints and very specific properties.&lt;/p&gt;

&lt;p&gt;Read the rest on my blog: &lt;a href="https://0byte.io/articles/many_meanings_of_model.html" rel="noopener noreferrer"&gt;https://0byte.io/articles/many_meanings_of_model.html&lt;/a&gt;&lt;/p&gt;

</description>
      <category>learning</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Visual Introduction to PyTorch</title>
      <dc:creator>0byte</dc:creator>
      <pubDate>Mon, 16 Mar 2026 11:21:26 +0000</pubDate>
      <link>https://dev.to/0byte/visual-introduction-to-pytorch-43jm</link>
      <guid>https://dev.to/0byte/visual-introduction-to-pytorch-43jm</guid>
      <description>&lt;p&gt;PyTorch is currently one of the most popular deep learning frameworks. It is an open-source library built upon the Torch Library. &lt;/p&gt;

&lt;p&gt;Most tutorials assume you're comfortable jumping straight into code. I made a visual introduction that walks through the core concepts step by step, with animations and diagrams instead of walls of text.&lt;/p&gt;

&lt;p&gt;Whether you're completely new to deep learning or just want a clearer mental model of what's happening under the hood, this should help.&lt;/p&gt;

&lt;p&gt;What's covered:&lt;br&gt;
&lt;strong&gt;Tensors&lt;/strong&gt; - what they are and how PyTorch thinks about data&lt;br&gt;
&lt;strong&gt;Initialisation Functions&lt;/strong&gt; - how weights get set up before training&lt;br&gt;
&lt;strong&gt;The basic ML training loop&lt;/strong&gt; - forward pass, loss, backward, update&lt;br&gt;
&lt;strong&gt;Activation functions&lt;/strong&gt; - ReLU, Sigmoid, Tanh and when in the training pipeline they are used&lt;/p&gt;

&lt;p&gt;...and a few more concepts to tie it all together!&lt;/p&gt;

&lt;p&gt;

  &lt;iframe src="https://www.youtube.com/embed/G4UAQ6bxQzE"&gt;
  &lt;/iframe&gt;


&lt;/p&gt;

</description>
      <category>machinelearning</category>
      <category>ai</category>
      <category>programming</category>
      <category>python</category>
    </item>
  </channel>
</rss>
