How to NOT LEARN WebGL Software engineering learning journey

Professional Development
12 followers
6 Video Views·Mar 5, 2026
An insight into how I learned WebGL and the mistakes I did along the way. Based of a comment from this case study video:
Hello everyone! Apart from robotic stuff and just talking about tech in general,
from time to time I publish videos like this. Essentially little showcases about a particular
project I am working on. And these projects, most of the time, are related to a technology
that I absolutely love, which is WebGL. So essentially a graphics library for the web
based on OpenGL to allow you mainly, what it is mainly known for, making 3D things for the web.
You can see an example here on my website, or for example here, on a project I covered
on this video right there. And these projects, I just really like it. It's this pure sense of
creation while still being able to solve problems, just like any software engineer would do. And in
this video particularly, there was this comment. Where does one come to learn about WebGL? I know
the documentation is helpful and everything, but I mean the mathematic aspect of it. Is it matrices,
geometry? Essentially this question was about, like, how can you progress in this very niche
part of the web? And this question, like, tickled my brain a little bit because I realized that,
yeah, I don't really have an actual answer to it. The thing I can answer though is,
how did I learn it? And so for the little story, I think WebGL is what got me into the software
engineering industry. Even before knowing what JavaScript was, web development, and that kind
of stuff, I was exposed to generative design and creative coding in general. Wait, let me actually
get a few things. There you go. We already talked about this one in another video. Old book, but so,
so good. Would highly recommend it. Especially all about, like, big whoops. Especially, yeah,
generative coding with processing. Oh my god, still smells tremendous. Goddamn. But yeah,
this essentially was my first exposition into the world of coding. And while slowly navigating in
this world, discovering all of these things, this new passion, this new trigger of, like,
oh, lines of code can actually create something that is visually appealing, I stumbled upon some
WebGL websites. And so just like anyone, I was familiar with real-time 3D with video games,
but I never was faced with this idea of online real-time 3D stuff just for visual appeal. And
that flipped a switch so hard in my brain. I fell instantly in love with this idea, and I was like,
no, no, I got it about this. And I didn't know ---- at the time. Didn't know ---- about software
engineering. And I kind of felt that that thing, that WebGL thing, was so different from the rest
of the web that it was just a thing on its own, a thing in general. And I directly jumped into,
I don't know, maybe googling some ---- just like, how do I learn WebGL, that kind of stuff. And I
did. And I did it in the most stupid way possible. So when you make your first WebGL research,
there is a pretty high possibility that you will end up on here. Fig.js, which is a JavaScript
library. I didn't even ******* know what a JavaScript library was. But whatever, I fall
on this and I see all of these examples of different websites. I'm like, yeah, this is
exactly what I'm looking for. And so after the first couple of research, I was like, yeah,
how do I go about learning Fig.js? And there is no way I will find this article again,
because we are talking about like 2016, 2017, something like that. And after reading a few
articles or whatever, I was like, yeah, if I just learn by heart how to do that, I'm going to be
okay. So the parallax camera works like this. The perspective camera is there. The materials is here.
I was trying to memorize everything by heart and was sure that this was the way that people learned
how to code. I thought to myself like, yeah, WebGL seems to be fun. I would enjoy to create
these things. And so just hitting two birds with one stone, right? I'm just learning coding while
learning also WebGL. I even also, at the time, bought this book right there, Learning Fig.js,
the JavaScript 3D Library for WebGL. I would never buy this today. Never. This was a ----
investment. It did help me a little bit. See, I still have those old notes right there. What
is that about? Dude, this brings me back. Yeah, damn. What year is that? First published October
2013. Brother. Whatever. So yeah, I was trying to learn this, bypassing anything related to
computer science. It's just like if someone wanted to know how to cook a beef wellington
without even knowing what a whisk is. All right. Does this analogy make sense? Kind of. I didn't
even use a whisk for beef wellington. And anyways, you get my point. I was trying to like burn
through steps. And I don't know if it's still considered a niche part of the web, but at the
time, WebGL was really, really, really niche. I don't think it is as niche today because of some
of the things we're going to talk about. But yeah, I was beating my head against the wall. And that
wall being just knowing what JavaScript is or knowing what a library is, how does the web work.
It took me even like some times to understand that, yeah, by the way, WebGL is just like a
thing. But also the thing is, I don't know if I didn't have these days of struggling,
maybe I wouldn't be where I am today. But I'm not too sure about that. Oh, because there is also
that I forgot about. Like WebGL, as I said in the beginning, or like mostly what it is used for,
it's a web graphics library mainly used for 3D stuff. And just even 3D in general and more like
real-time 3D and 3D modeling, this is also just an entire thing on its own. And so WebGL mixes
real-time graphics, knowing how 3D models work, just like words with UV mapping, stuff like that,
making it work on the web with an entire gigantic code language that is JavaScript. And I was just
focused on like, yeah, what if I can make a cube glow, right? So obviously, don't do that. Don't
do it this way. I was skipping way too many steps. And before learning about this niche,
just learn about the fundamental concepts in general. If you are a complete beginner,
just even avoiding in general, just learn what the web is to begin with. I don't think I know
anyone who is a WebGL developer who doesn't know ---- about web. It doesn't even make sense.
But in any case, to fall back on my feet about this first question that we had, how do you even
learn about this stuff? And nowadays, since WebGL is a little bit more well-known, I would say,
in this industry, you have access to some pretty insanely amazing courses. This is a huge classic
right there. 3JS Journey by this amazing dude over here, Bruno Simon. It's like, it's a staple
now in WebGL. And like, there is really, on the web now, a before and after this online class.
I also did myself a sort of masterclass on all words, but it would be genuinely a joke for me to
even compare the two. If you are really interested into 3JS and that kind of good stuff, and you
really want to get started and have a deep understanding of how that works, learn about
that. Look into this thing. Can you learn WebGL without it? For sure. For sure you can. Simply
reading documentation, right? Talked about that in a previous video, but like, you have everything
you need on 3js.org also. Yeah. Just like you have a getting started here. Everything is explained
by programmers for programmers. And you can essentially not like, you cannot go wrong there,
is what I'm saying. But like, the interesting part of this question is, and I think I understand it,
it's also pretty difficult to put into words, is more like, how do you shape your brain to solve
particular problems? Just like anything related to code, when you are faced with an issue, let's say,
for example, a freelance project where they come to you and they have a pitching idea,
you have 25,000 ways to go about this. Like, very simply, you would like a simple landing page. You
have the choice between so many different frameworks, so many different animation
libraries, and so on and so forth. And even in the tiny niche of 3JS WebGL scenes, you have so
many ways to come up with your own ideas. And I think the goal is to, when you are really interested
into this thing, obviously, is to like, try to be as curious as possible and just read and do.
Read and do. One of the first time I was actually reading docs, because I didn't have any other
options, there was just like, no YouTube stuff related to this, something was suggested by a
co-worker of mine at the time, while working in a studio in Paris, the book of shaders. This
teaches you about something called GLSL. It's the shader library for WebGL. And this is a gigantic
topic on its own. This is just also, this is a niche in a niche. Dude, like, you have software
engineering, which is a big old industry. You have the web, which is like, a portion of this industry.
Then we talked about niche animation-ish type of web thing to do beautiful stuff. This is starting
to become a niche. Then to WebGL, real-time graphics, alright. And then, inside of there,
you can do your own shaders written in a different language than JavaScript. Now we are going into
the deep stuff. And if you are interested into these kind of things, the book of shader right
there, dude, take your time, read it. It's amazing. It's not done. I don't know for how long
this has been going for, but like, yeah, there are some chapters that are missing or whatever.
But this is such a good read. And along with that, take my advice with a grain of salt.
What I'm showing to you right now is what I have been going through to learn things at the time
where 3JS journey didn't exist, and all of these kind of other things. So take it with a grain of
salt. Anyways, the other thing I wanted to talk about is this thing, WebGL fundamentals. So as
we said, 3JS is a JavaScript library, and it's built on top of WebGL. It uses WebGL stuff to
create 3JS. 3JS is a sort of wrapper with already done things. And 3JS, I don't know if it's like a
common word or whatever, but like I heard this term so much, and native WebGL are very, very,
very, very different. And WebGL fundamentals just goes about that. It just teaches you about
what WebGL is and how to use it, essentially. And this goes deep into the math stuff. Because
there is a lot of, like, rotation matrices and that kind of stuff, and like, this is not even
the realm of even computer science. This is just pure calculus, mathematics. There you go, look at
these things. Oof, geez. Do you need this to create WebGL stuff with 3.js? No. Does it give you a
better understanding of how that works, and it's just another tool in your tool belt if you want
to make this your actual full-time job? Yes, absolutely. But it's also a gigantic *******
headache, I'm gonna be honest with you. It's terrible. I tried to create at the time my
own little framework on top of Vue as well. I was trying to have a wrapper or whatever. It didn't
work. Well, I was able to, like, import OBJ models, but like, that's it. But yeah, it was just
terrible. Copy-pasting code, trying to understand the matrices, that kind of stuff. Did I learn
stuff though? Yeah, and plenty of it. So yeah, the book of shaders, WebGL fundamentals. Oh,
just even 3D in general. If you are alone working on your 3.js projects, the WebGL stuff, those are
tools to make something look good online using 3D things that are around it. And if you don't
have good 3D models, understand how UV maps work, animations and all of that, those things, those
are not done with code. Those are done on the side, usually by artists. But it's also a good
thing to just get started. Blender, I think, is the industry standard for WebGL, like the outside
tool you use along with it. And learning about Blender, this is even just an entire different
job on its own. You will never be able to be an expert at both, I think. All right, I think. Maybe
they are up there. There are some pretty interesting people in this field that are absolute
crackheads when it comes to these kind of things. And it is impressive. Maybe you can become one.
But what I'm saying is, learn about these things as well. Learn about 3D in general. And also,
just do. Just create stuff. Create ---- constantly. Read articles, find them, try to...
There you go. It just comes to this. Be curious about these kinds of things. And be patient. Be
patient. Right now, when it comes to WebGL stuff, I know that I have 20 other different processes
that I really want to learn about. And I can. I can find the documentation. I know where to find
it or whatever. But it just takes a lot of time. You are mixing computer science, mathematics,
calculus, algebra, 3D, real-time 3D, autistic processes, and all of that. So if you want to
get into this field, be patient. Read stuff. Buy Bruno Simon's course, if you are interested in
that. It is pricey, but I think it is worth it. I've never done it myself, but I only heard good
things. And it just looks tremendous. Also, this is just even the landing page. And oh my god,
does it look nice. You can buy my course as well. But buy Bruno Simon's one first, please. It will
be better for you, for sure. For your career, at least. And yeah, create your stuff. Show it to
people. Try to find communities. Exchange left and right. Publish it on Twitter. Ask for people to
tear it down. Try to understand what's going on. And yeah, it's a pretty interesting journey,
a long-ass one for sure. But it can only be beneficial for your career in the soft
engineering industry. That's for sure. I will try to put in the description as much of the
different websites and documentation I talked about. And yeah, I hope you enjoyed this video.
I hope it was helpful. I don't really know if I was hitting the bullseye on this question,
but I do hope it helped. Anyways, I think that's it for me. Enjoy the rest of the day. And apart
from that, I see you soon on the internet. Bye-bye, everyone.
