Shouldn't this be accessible only to those who paid $20[1]?
12 karma · joined January 24, 2012
However, what I was trying to suggest is something slightly different. What if a web framework was smart enough to generate a routing configuration for a web server, instead of processing some sort of route table on every request? Think of a workflow like this:
1. Application developers can still define routes somewhere in application code as they do now.
2. Framework takes that route table, and generates a routing config for a web server, offline.
3. Deployment engineer does not need to worry about resources being served, but would have to make sure that the generated config is included where appropriate and trigger configuration reload on web server.
I (naively) think, that the above three could result in:
1. Nothing really changes for the application developer, except a chunk of redundant code is removed from the top of his code in the stack.
2. Web server configuration languages (or a subset related to routing) are fairly robust by now and rarely drastically change (I'm thinking about nginx and Apache2 here). Add this to an auto-generated configuration and a layer of error is reduced.
3. Deployment engineer does not need to configure any routing, but has to make sure a generated file is included in configuration, when deployed.
1. I always prepared (exactly) 2 page CV.
2. One thing, that paid off (I think) I always prepared CV for specific Job offer. Takes time, but exposes the best of you in paper for the position you are applying for.
3. I have a belief that "If text looks good on paper - it will look good on screen", not necessarily otherwise. Thus I print my CV, read it loudly, mark and correct bits and pieces with pencil, edit the electronic form, rinse & repeat until I don't have anything to edit.
4. I wrote cover letter twice in my life - basically it was among the lines of: "I would love to work at your company, because you are cool at something I am interested in working on and I think I have the skills you need (references to CV, showing my experience in what they needed)."
So far so good, through the years I applied to companies in Lithuania, Denmark, Sweden and UK (London) - I got offers from all of them. I applied for Software Engineer position in PHP or Python companies.
"Tenzing has read-only support for structured (nested and repeated) data formats such as complex protocol buffer struc- tures. <...> The engine itself can only deal with flat relational data, unlike Dremel [17]"
And from section #5.4 I assume that currently they use Dremel query engine, but are in the works of creating another one.