7 months ago, I was looking for a job and got frustrated with the current resume builders, so decided to build one exactly how I wanted a resume builder to be.
I adore tagging systems and have worked on them in several different applications and implementations, but there are always pitfalls and trade offs, and it’s possible to bury yourself
Nowadays I nearly always store the assigned tags as an integer array column in Postgres, then use the intarray extension to handle the arbitrary boolean expression searches like “((1|2)&(3)&(！5))”. I still have a tags table that stores all the metadata / hierarchy / rules, but for performance I don’t use a join table. This has solved most of my problems. Supertags just expand to OR statements when I generate the expression. Performance has been excellent even with large tables thanks to pg indexing.
7 months ago, I was looking for a job and got frustrated with the current resume builders, so decided to build one exactly how I wanted a resume builder to be.
- Free (like really free).
- No signup, no login.
- Has AI features to improve text.
- Find jobs matching the resume.
https://resumeyay.com