What theoretical knowledge should frontend developer know?

twitter logo github logo 惻1 min read

My older brother says I lack some theoretical skills but I don't know which ones. I'm a frontend developer so I don't know how much do I need.

I already know:

  • Basic parsing (I wrote a function for parsing integers using recursion by myself)
  • Recursion (I rewrote some racket array methods using recursion [source])
  • Basic data structures, such as Heap, Stack, Associated Array, Matrix etc.
  • Function composition, alternativity, optionality
  • Calculating simple syntax trees [source]
  • Basic agebraic structures (monoid, group, half-group etc.)
  • Boolean logic (xor, implication, or etc.)

What other theoretical knowledge should web developer know to write performant web apps (e.g. optimizing with math)?

twitter logo DISCUSS (5)
markdown guide

From whay you've written here, it seems you know quite a lot and are more suited for backend programming.

Although fronted is quite complex and comprises myriad of various tools, UI developers usually don't pay that much attention to optimisations and let alone know the difference between stack and heap. This is not a disadvantage since many of those terms are abstracted in the fronted.

I mean no disrespect to the fronted guys as I have also done my fair share of UI development. It takes a lot of work to be a successful fronted developer these days.

It's up to you to choose your path but given your extensive knowledge, you might aswell try both and decide which suits you better.

Hsppy coding šŸ˜‰


1) I'm fullstack tbh, but mostly frontend

2) Some complex frontend requires math, for example Virtual DOM or optimizing memory

Thank you for your response :)


Modern frameworks like React and Vue usually deal with Virtual DOM. That's why I mentioned that nobody seems to care about manual optimizations since there are so many tools included in the workflow. It's hard to keep track which one does what.

I am a C developer and am currently doing embedded development where every single bit of optimization and minimization is important. That is why, in my personal opinion, believe that you would find it more challenging and fulfilling to lean more towards the back-end development.

Congrats on being full-stack, I know it takes tremendous effort to cover both sides. Whatever you decide, you can't go wrong with that amount of knowledge.



It really depends on your position on a project. What do you prefer to do? I would say you could pursue your learning by having more network oriented courses to understand how the browser handles connections in Http 1 and differences between versions 1 and 2, speed optimization can be beneficial to be able to improve SEO if you work on this direction (and will force you to understand different media formats, bundles that can help you create Webp images from png and jpeg,...), etc...


1) I know how HTTP works, I even tried to read some traffic packets
2) difference between HTTP 1.1 and HTTP2 is a good thing to learn
3) I also know about webp and I try to use it everywhere cos images become tiny.

I don't have a sub direction of frontend, I just learn it all

Classic DEV Post from Jan 22

Self Care for Developers

Self care is a hot topic these days, and Iā€™m not just talking about face masks. There is a growing movement that underscores the importance of taking time to take care of yourself (in addition to all the other things that you already take time for). You can prevent problems down the road by taking proactive steps to ensure your health and happiness.

v 1 r t l profile image
I'm a teen web developer and a bit web designer. I like making interactive stuff with code and try to combine both tech & art.