Texas Luminescence
Product engineering organization at the University of Texas at Austin; website built by me
Hi, I'm Roger.
I'm a math and CS student at UT Austin. I enjoy competitive programming, table tennis, and occasional writing.
Check out terminal.rogerwang.dev over ssh!
Things
International Biology Bowl
Biology competition for thousands of high school students across the world
2nnel
Self-hosted ngrok with one-click deploy to tunnel server. Won a hackathon and Cursor hat
Olympus
Real-time PvP game for SAT studying
dotfiles
My terminal setup for efficiency in bash, vim
Thoughts
Having my cache and eating it too: how I made rogerwang.dev so fast
In today's day and age, it's difficult to justify hand-coding a blog website. For one, platforms like WordPress, Wix, and Medium are designed to abstract away the code entirely, letting you focus on content and design. Or, if design is not your forte, you can skip that part entirely and leave it to AI. Having seen many personal websites of peers and Texas Luminescence applicants, I have witnessed AI being used for this to great effect. Many standout design elements, like animations, gradients, and shaders, and design trends, like brutalism, neumorphism, and glassmorphism, can all be wished into existence via a variety of AI genies.
Why is an API?
For a web developer, it is a rite of passage to learn what a web API is. Everyone and their grandmother has probably used one, and if someone were curious enough to ask what it is, they would be met with articles upon articles, from GeeksForGeeks, IBM, AWS, FreeCodecamp, Wikipedia, Coursera, Cloudflare, Oracle, Github, and many, many other sources, answering that exact question. So I think it's safe to say that that request has a response, and a unanimous response at that: an API is an Application Programming Interface, or thing by which a client communicates with a server.