Show HN: CVservant: CV Creator for Academic Types
cvservant.com
cvservant.com
> Forbidden (403) CSRF verification failed. Request aborted.
Also, just some more feedback on making this a business that is charging for holding people's private information:
* Your privacy policy should be an actual privacy policy, stating what information you collect rather than just stating how you are super private and hate all the "crap" that other vendors do. Particularly as when combined with the terms, this is not GDPR compliant.
* Intentionally putting your term and conditions in a hard to read font to make a joke about rental cars is probably not good business sense - Just make them easy to read straight out, it just looks more professional, and also makes it look like you aren't hiding something, particularly when...
* The terms are terrible for customers! "This service is not suitable for any purpose [and users] are expressly warned not to harbor any expectations at all, reasonable or otherwise." - I don't think these terms sound like what is sold on the main page! I'm in the UK and here at least consumers have a right to purchase something that is fit-for-purpose and you can't exclude that within T&C's, but not sure if it's different in the states! Either way, I don't think you should sell something, and then state in the terms and conditions that it's not suitable for the purpose you are selling it for.
Good luck getting it working, it looks like a good idea. The points I’ve raised are a bit critical but meant in the best spirit just to try and help make it a success.
Also, your terms currently let you take payment and not even provide the paid-for service (i.e. cancel it for any reason with no refund, and no right to even ask for refund, and I can't even find a support email!) - this seems shady to me if you are asking for $300 for lifetime membership! I would expect a pro-rated refund for subscriptions as a minimum, and some sort of pro-rata for the $300 (e.g. over 5 years).
Besides - why are you trying to emulate other people’s shitty practices? If someone isn’t happy why not let them at least request a refund?
My personal advice would be - just get some generic terms written by an actual lawyer and put them in instead. Or just copy/paste some pre-written terms you can find available on any number of websites. It will look more professional, protect you more, and be more reasonable to your users :)
You can maintain a collection of CVs with different information, in different styles, for different purposes.
You can enter your publications one at a time, or upload a BibTeX file if you have one. You can export all your data, including your pubs translated into BibTeX, whenever you want. You can control what publications are listed on what CVs, and how.
You can share the PDF of your CV using a URL with a hash, that you can “revoke” if needed, or update while keeping the same URL.
It’s a bit complicated, because the job that it does is complicated. But I tried to guide the user with help tips where needed.
Right now it looks like crap on small screens, but it works.
Designed to load fast, with very small downloads. Works without JavaScript, but I use a little to smooth over the interactions.
It uses Django, Postgresql, and XeLaTeX, and a little htmx.
All criticisms or advice welcome!
Furthermore, the overall website looks a bit like 1995, but that's of course a matter of taste. The fees are hidden somewhere in the lengthy text https://cvservant.com/cv/more/ -- this is almost a "dark pattern" and definetly not transparent.
Furthermore, sharing CVs is advertised at https://cvservant.com/cv/sharing/ but again, I don't see any examples of CVs shared on this site.
I second the opinion that these CVs don't look like the academic ones used in the US and most parts of the EU. Perhaps this service is tailored more towards some other part of the world.
I would focus on the UI, examples, and building a strong user base before charging for the service. You could also add biosketches (as required by different funding agencies). If you do an excellent job at it, you might get acquired by services like Researchgate, Mendeley or maybe Overleaf, if you allowed people to import and edit their documents in LaTex.
On the bright side, I would pay for a well-executed SaaS for academic / grant documents management.
Good luck with your project!
ven though I say it would be useful for grant applications if you had those templates, you will be competing with the government for that use case, NIH created SciENCv, which will generate your NIH and NSF biosketches from a single source of data.
* There is no way to set the order in which publications appear in the CV, default ordering is a bit weird, so this must be customizable.
* Latex error messages could maybe be helpful when something goes wrong.. maybe it's some special character I input?
* It's nice that it's not tied to an email, but I am a bit reluctant to give money to a place where I could loose access any time. If something goes wrong on your side and you loose my credentials, how will I be able to re-identify? Also, how does this go with GDPR?
* Also in this vain.. are answers to secret questions hashed and salted? if they are, maybe this should be stated as the minimalist retro style suggests they are stored plain text.
* There are some standards out there that could make your life easier, and also help users interoperate better. I am not an expert, but there is the european CV xml schema[0], as well as the skills and occupations thesaurus[1]. Also, linkedin and such service GDPR::have to offer some export functionality.. it would be nice to be able to import these.
* Several national funding agencies have their own lousy CV creation tools, maybe it could be a businesses model to approach them and re-do it for them. Of course, they are interested in other things (e.g. application tracking, scienciometrics, etc), so just thinking out loud here.
* There are tools out there that keep track of your publications, and not all allow for bibtex exports. Maybe make crawlers for these? subcontract with the devil (e.g. access scopus)? or make import for the other formats people use for bibliographies (endnote, etc.)
* The approach is nice, so it might be a good idea to keep an eye on the pitfalls of other such ventures, namely:
* we are stuck with your style decisions regarding templates, we might not like them, they might run out of fashion, or in an attempt to mitigate this you will create millions of templates which are difficult to search for, hell to maintain, and most likely a growing nest of bugs (already my publications won't render with the "awesome" template).
* If you want to allow more customization, complexity in the UI will grow (and bugs), and at the end users will be frustrated and just download the data and write their own latex template (or move to another service).
* Malicious actors hosting stuff (allowing for uploads without email-verification / captchas) is, imho, playing with fire.
The best of lucks!
[0] https://europa.eu/europass/en/eportfolio-interoperability [1] https://ec.europa.eu/esco/portal/download
(I’ve made your account free for life to encourage you to test it out some more.)
(Thanks!)
But, I'm still not going to make an account (and then I guess fill in some data) just to see some examples. Also, while you are right I don't need an email address, it's usually a requirement and I wasn't going to go explore.
Here's a screenshot of what I entered: https://share.getcloudapp.com/5zuAZmgX
(I’ve made your account free for life.)
I found another issue where importing a .bib of my publication ends up with a bunch of publications completely unrelated to what I imported.
Happy to discuss further over email if that suits you better...
lee@lee-phillips.org
But if the pubs that appeared on the CV are not even in your .bib, then the problem is not there, but in the code somewhere.