The AWS Resume Challenge

Hello everyone, welcome to my edition of the 'Cloud Resume Challenge' using AWS. The first step of the challenge was to pay for a cert... But here I am with a functioning webpage and no $100 line of HTML in my resume :)

Visitors:

One of the challenges was to implement a 'visitor tracker'. This isn't as compliated as it seems.

Each time the website refreshes (try it?), the javascript sends a request to a lambda function running on AWS server. This lambda function pulls the numbers from a database and adds one.

WaniKani Stats


Level:
Lessons Due:
Reviews Due:

I have been working on my kanji for a few years now through the WaniKani app. Luckily they have an API I can call! This portion is mainly so I can do a quick check on how screwed I am.

The review system is similar to Anki and relies on spaced repitition system (SRS). I am a big fan of this method of memorization and review whether it be for kata, vocab, or theorems.

Twitch Progress


Followers:
Subscribers:

Twitch also has an API but this one is more likely to break as the token resets like every 90 days. Follow me at layneStreaming.

More Comments

I enjoyed CSS formatting better than backend development. I wholeheartedly believe

\(\LaTeX > \text{Microsoft Word}\)

because the authoritarianism of formatting via code makes it so only I may express creativity here. I spent waayy too long making a sakura petal drift between the sections of my resume. I had to force myself to move on!!! But now the hard part is done and the challenge is completed.


I've made substantial progress including creating my own (basic, I know) template. In the evolving world of AI-slop, clickbait media, and content farming, it's even more important to keep the tradition of personalized websites alive. More blog posts about things I find interesting (which probably don't have an exact duplicate source elsewhere) will be added as well.


I did the challenge in numeric order (besides step 1 lol) so I ended up creating my db, api, and lambda twice: once through the AWS online interface, and again using YAML. I think this is for the best, but I'm just kind of bitter because I don't even like the back end stuff very much...


There are so many documentations/videos giving overly-complex yet incomplete solutions to the same problem. Content creators have uploaded entire playlists detailing how to complete this challenge so an interviewee citing 'Completed AWS Challenge Website' proves nothing about webdev capability. But hey, maybe that's what the certification is for.