Show HN: aufond.me — a résumé for the modern age [Meteor.js MVP]

I should write something more elaborate, but for the sake of not leaving your comment hanging, this is what I can highlight out the back of my head:

- The best thing by far is sharing the same code for both client and server. It is as good as it sounds, at least as far as productivity and having a small codebase goes

- Everybody is worried about security, but they got it covered. For each collection you can filer who can publish/insert/update or delete. Each go through a filter you attach a callback to, where you have the userId at hand and can easily only allow the owner of a document to be able to update or delete it. Or just as easy publish (for read) only the documents that a user owns, for all regular users, and publish all of them for an admin user.

- It takes a while to create an organized structure though, there is a loading order for certain folder names, but basically everything that is in your project will be loaded in the project asynchronously, w/out having any control on the order. This makes it painful when dealing with inheritance, but in the end you get around it using the folder order of loading they provide and using the Meteor.startup callback, where you can assume all files have loaded

- Another thing that I found a bit counter intuitive at first is that everything is template oriented. Usually you have a module of some sort, which loads a template. Here you have a template, which has _code_ attached to it. It's very easy to go the spaghetti-code no-framework JavaScript way. But if you like having control and are able to create a scalable pattern for modules/widgets, it becomes a very powerful tool

I like it, it would make a great "about" page for someone's blog.

I'm not sure that it really works as a resume though (at least in my small part of the world which is finance in London). Where I am recruitment is dominated be recruiters, and the majority of them need a CV that they can change into their format (word) and send over to their client.

I'm also interested to know what meteor specifically brought to this, did you need the real time features of meteor in some way or is it just that you wanted to try it out?

It looks awesome though, really great work!

P.S. Are you really a paratrooper?

Interesting perspective, you're not the first to mention that even though you like it, you don't necesserily see it as a CV. That's why I posted early, to validate the idea and direction. It's a common thing to pivot the market with the same product, after getting feedback from potential users. I'll certaintly think about this some more, thanks!

This is not your typical Meteor project. Almost everything is realtime, but because that's how Meteor works, not because it was a requirement. So yes, mostly I just wanted to try it out. But I can can confirm it can also be used as your everyday web framework, not just for chat servers or what one might imagine it was made for

Not an actual paratrooper, that would've been cool!

If you need any help with the static HTML generation with Meteor, I'll gladly lend a hand. It's not rocket science of course, but if you want to save time, I can share code snippets. I hang out in #meteor on IRC as matb33

Damn, it's timing out for me as well. I'll restart it immediately and stretch the Rackspace instance if won't take long. Sorry