Resume Builder Used AI

I rewrote the frontend, kind of. It jumped from ~~700 to ~~1000 lines. I wrote a lot of it with Claude, but like 30% was by me :). IDK why it returned the same thing I typed, but I think that next I will work on the system instruction.

That took much longer than it should have. ChatGPT took me down a rabbit hole of wrong code. I had to get Claude to help me out of this. Not gonna lie, claude is better. But, back to the main coding, I finished the backend for the ai generating better descriptions now i gotta do the frontend

I made a readme.md file! I think I covered everything in it. Probably will ship in 30 minutes, just have to come up with a better description for this :)

ohhh my gawd. that took so looong. let me break it down for you. I wrote 700 lines in 2 hours. then I spent 30 mins debugging, then I spent 30 mins writing to 800 lines. I debugged some more for half an hour, and lastly I erased some lines for better functionality and removed all of the comments for no reason:~{. I typed a bit too slow, but I was vibin to the music alr.

I have spent all of this time squashing bug after bug after bug and I am tired. I realized that I am sending user data to the backend which not very safe. I decided to completely overhaul how it works so everything is in the frontend and it stores data very soomthly. I am just worried how long this will take me hope not to long :}

I spent all of this time trying to find a way to download the generated file as a PDF. It took me so long because almost every single way to do this required me to download some sort of either .exe file ro sudo apt install somethine. I didn't have a problem with this but as I planned on hosting it on nest and I obviously don't have sudo acces for that so I tried and tried to look for another solution. This involved looking online downloading libraries using pip and trying tutorial after tutorial of this. sadly at the end It still wasn't working so I pretty much just gave up. I never even thought about looking online to see if anythin supported me sudo apt installing something. I did this after taking a break and found out that render supported this so thats what I decided to go with. During this time I also encoded the ids so that it is impossible to guess the id. Still working on making the id system better though.

I made it accessible directly from the frontend

Whew! That was a lot of work. I finally made a template for the resume. It took a while and I made it look good with tailwind css as well. Lastly I would like to mention my next steps. Make it more secure so that only if you know the right id can you see the data. I will use uuids for this so that it is practically impossible for someone to guess. and make it so that the template is actully visible on the main webiste. Right now its just an endpoint on the backend which return html. I have to take that and bring it to the frontend. <-- sry it pretty long

I made it look pretty good, I think. I tried to use Tailwind CSS at first, but that didn't work out, so I just used a style.css file. It's not the best, but if you were to rate it out of 10, what would you give?
Note: I zoomed out a bit to get this picture, so it will probably look a bit bigger in the actual website.

Ok, that wasn't as hard as I thought it was. It was just doing the role thing twice and then integrating the print underneath it. I am gonna try to add TailwindCSS to the project next to make it look cool 😎. It's my first time using it, so let's so how it goes.

As I think I said earlier, the experience and skills tab required the user to input the correct JSON format into it, so I fixed the skills tab as seen in the picture. The experience tab will be harder as it has more inputs, such as company role, and I might work on adding start and end dates later on.

I made a simple frontend that takes the info and sends it to the backend api. This relies on the user inputting their information as a JSON array, which could cause problems, so I will add a layer that will do it for them.

first, I started off by making the backend. It was pretty simple, so I finished it quickly and started with the frontend. I tested the backend using Postman, as shown in the picture, which made it significantly easier.