I'm certified in Cybersecurity and JavaScript.
I have a long history of programming and development. I initially learned Python after seeing how easy it was to make things. Eventually I wanted to make something that other people could use without needing to download. I barely knew JS at the time I made Gloriaware. OG users might remember the fact that the very first original account page was a notepad download containing your UID, when you joined, and your username. From there, I worked with a great frontend and C++ developer Tohru/Legend27 to form the Gloriaware site and presence. His login, register, and FAQ page he created for Gloriaware is still being used to this day.
I've bought silly domains, make stupid projects, and overall learned tons for making anything web-related.
Here are my (announced public) projects and their use cases, ordered in amount of effort put in (They are linked. Feel free to click them!):
I'll host anyone's site and domain for cheap really. If you'd like a domain and website, feel free to contact me. If you use GW, you'll know where.
If you have any ideas for improving my sites, or any new ones, feel free to contact me same as above.
Making sites at first is going to be an incredibly daunting task. Just learn the basics of making websites: Favicon, CSS/Design, HTML, and Backend. The backend is the core of any site. All you need to do with the backend is make it serve a file. That's the origin of every site.
You'll learn fast and eventually want something with a login. It happens. Just please, PLEASE use the bcrypt library. And if you don't understand the importance of hashing, please google it. It's vital to any website with a login. PROTECT. YOUR. USERS!!!!
Make sure you do things as efficiently as possible when you're doing the backend. Learn Socket.io if you're so inclined to make forms that don't redirect on submission. They're super easy and you can read the docs to understand everything you need.
Think with the future. While you learn, think of how you'd teach others. You become receptive to your information better.
All things procedural should be known. It is vital to inform others of security vulnerabilities in everything. Problems created by a developer should be broadcasted everywhere on how to do it. There are other ways to approach lack of developer action, but there is only one way (this way) to truly push those lazy enough to make their userbase vulnerable to fix their issue. Make those who hold your data stop taking your trust for granted.
Create all you can. The existence of methods of doing creates more possibilites. The more tools in your toolbox, the more creation you can do.