Compilers are very complex beasts, some of the most complex bits of software engineering, but don't let that discourage you! If I use the analogy of engineering, building a compiler could be thought of as building a structure like a bridge.
It is somewhat trivial to make a very simple bridge - to put a tree trunk over a small stream perhaps. It isn't going to be very useful to many people. It might just be useful to you. But that's OK.
But as you try to make bigger bridges that offer more utility to more people, with the strength and robustness to carry heavier workloads in safety the cost and complexity ramps up quickly.
Soon it becomes too difficult for an unassisted person to build a small bridge, and if you are not a bridgebuilder by trade you will need specialist advice, and possibly skills. Think of something that will allow you to safely drive a light vehicle over it. Such a bridge will need proper foundations and abutments to spread the load. It quickly becomes an engineering problem.
I'm not saying that you shouldn't try to build your own compiler - I would actively encourage it, and can point to projects like TCC (
TCC : Tiny C Compiler ) and LCC (
LCC (compiler) - Wikipedia ) where people have done this with great results. You will learn some really interesting stuff, and deep knowledge can be very useful. But to write a useful compiler is a very large undertaking, and will take many years of skill and effort.
Where you will meet resistance is if you start to use forums to answer every question and line of enquiry, rather than to solve a very specific problem (e.g. asking "how can I build a symbol table" vs "my symbol table implementation doesn't work correctly because of ..."). In my experience people on forums like fixing things, not explaining things that are better explained elsewhere.
Reading a good book on compiler building will cover that topic and more - tokenizing source, lexical analysis, maintaining symbol tables, code generation, parsing, building directed acyclic graphs, efficient register allocation, dataflow analysis, data type representation, operator precedence, code optimization strategies...
When I was young, The Dragon Book was a must-read for the budding compiler writer -
Compilers: Principles, Techniques, and Tools - Wikipedia - I don't know what the current recommended one is.