<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_17_182238</id>
	<title>How To List FOSS Experience On Your Resume</title>
	<author>kdawson</author>
	<datestamp>1255781760000</datestamp>
	<htmltext>maximus1 writes <i>"If you're <a href="http://www.itworld.com/open-source/80513/what-include-your-open-source-resume">selling skills gained in an open source project</a>, you have additional opportunities to shine, say experts in this ITWorld article. But what is the best way to explain your FOSS experience? 'Someone stands out because of how they talk about the project, says Zack Grossbart, author of <em>The One Minute Commute</em>. His advice is to describe the project and discuss your contributions in detail: 'If you were a committer, what did you do to earn that status? What features did you work on? Did you design new areas, or just implement predefined functions? Did you lead meetings? Define new architecture? Set the project direction?' If the FOSS experience is part of your background but not a shining beacon or job equivalent, it's common to list it under 'other experience.' Andy Lester, author of <em>Land The Tech Job You Love</em>, says: 'Think of each project as a freelance job that you've worked on. Just as different freelance gigs have varying sizes and scopes, so too does each project to which you contribute. The key is to not lump all your projects under one "open source work" heading.' Good examples are worth a thousand words. Grossbart offers up his resume as a <a href="http://zackgrossbart.com/hackito/bsamples/ZackGrossbart.pdf">sound but not perfect example</a> (PDF) that includes open source experience. (His article on <a href="http://www.zackgrossbart.com/hackito/resume">how to format your resume</a> might also be of interest.)"</i></htmltext>
<tokenext>maximus1 writes " If you 're selling skills gained in an open source project , you have additional opportunities to shine , say experts in this ITWorld article .
But what is the best way to explain your FOSS experience ?
'Someone stands out because of how they talk about the project , says Zack Grossbart , author of The One Minute Commute .
His advice is to describe the project and discuss your contributions in detail : 'If you were a committer , what did you do to earn that status ?
What features did you work on ?
Did you design new areas , or just implement predefined functions ?
Did you lead meetings ?
Define new architecture ?
Set the project direction ?
' If the FOSS experience is part of your background but not a shining beacon or job equivalent , it 's common to list it under 'other experience .
' Andy Lester , author of Land The Tech Job You Love , says : 'Think of each project as a freelance job that you 've worked on .
Just as different freelance gigs have varying sizes and scopes , so too does each project to which you contribute .
The key is to not lump all your projects under one " open source work " heading .
' Good examples are worth a thousand words .
Grossbart offers up his resume as a sound but not perfect example ( PDF ) that includes open source experience .
( His article on how to format your resume might also be of interest .
) "</tokentext>
<sentencetext>maximus1 writes "If you're selling skills gained in an open source project, you have additional opportunities to shine, say experts in this ITWorld article.
But what is the best way to explain your FOSS experience?
'Someone stands out because of how they talk about the project, says Zack Grossbart, author of The One Minute Commute.
His advice is to describe the project and discuss your contributions in detail: 'If you were a committer, what did you do to earn that status?
What features did you work on?
Did you design new areas, or just implement predefined functions?
Did you lead meetings?
Define new architecture?
Set the project direction?
' If the FOSS experience is part of your background but not a shining beacon or job equivalent, it's common to list it under 'other experience.
' Andy Lester, author of Land The Tech Job You Love, says: 'Think of each project as a freelance job that you've worked on.
Just as different freelance gigs have varying sizes and scopes, so too does each project to which you contribute.
The key is to not lump all your projects under one "open source work" heading.
' Good examples are worth a thousand words.
Grossbart offers up his resume as a sound but not perfect example (PDF) that includes open source experience.
(His article on how to format your resume might also be of interest.
)"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781081</id>
	<title>Re:Open source.</title>
	<author>John Hasler</author>
	<datestamp>1255786560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Because they are PHBs.  They are not interested in what you actually did (and couldn't understand it anyway).</p></htmltext>
<tokenext>Because they are PHBs .
They are not interested in what you actually did ( and could n't understand it anyway ) .</tokentext>
<sentencetext>Because they are PHBs.
They are not interested in what you actually did (and couldn't understand it anyway).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781047</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29791413</id>
	<title>Re:How to format? Is not it about CONTENT?</title>
	<author>mi</author>
	<datestamp>1255947300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>It's an interesting gimmick, but not sure what purpose it'd have for anyone other than XML monkeys.</p></div></blockquote><p>There are <em>automated</em> ways to generate HTML, PDF, PostScript, and Plain Text from the XML-resume (this, for example, is <a href="http://freebsd.org/~mi/resume/" title="freebsd.org" rel="nofollow">how I do it</a> [freebsd.org]), that I use to generated mine). Yes, recruiters ask me about the Word-version once in a while, and I tell them, no, I don't use Word.

</p><p>The result looks pretty good to me (although it does not attempt to cram everything into a single page the way TFA's author does). One can even <em>comment stuff out</em> or make inclusion of certain items conditional. You may be looking for a sysadmin <em>or</em> a developer position, for example. With this you can produce different flavors of your resume <em>from the same source</em>...

</p><p>It can also make your resume easier to search some day &mdash; when the search engines recognize this particular XML-template...

</p><p>There is certainly nothing "gimmicky" about it &mdash; this sort of thing is, what XML is best suited for...</p></div>
	</htmltext>
<tokenext>It 's an interesting gimmick , but not sure what purpose it 'd have for anyone other than XML monkeys.There are automated ways to generate HTML , PDF , PostScript , and Plain Text from the XML-resume ( this , for example , is how I do it [ freebsd.org ] ) , that I use to generated mine ) .
Yes , recruiters ask me about the Word-version once in a while , and I tell them , no , I do n't use Word .
The result looks pretty good to me ( although it does not attempt to cram everything into a single page the way TFA 's author does ) .
One can even comment stuff out or make inclusion of certain items conditional .
You may be looking for a sysadmin or a developer position , for example .
With this you can produce different flavors of your resume from the same source.. . It can also make your resume easier to search some day    when the search engines recognize this particular XML-template.. . There is certainly nothing " gimmicky " about it    this sort of thing is , what XML is best suited for.. .</tokentext>
<sentencetext>It's an interesting gimmick, but not sure what purpose it'd have for anyone other than XML monkeys.There are automated ways to generate HTML, PDF, PostScript, and Plain Text from the XML-resume (this, for example, is how I do it [freebsd.org]), that I use to generated mine).
Yes, recruiters ask me about the Word-version once in a while, and I tell them, no, I don't use Word.
The result looks pretty good to me (although it does not attempt to cram everything into a single page the way TFA's author does).
One can even comment stuff out or make inclusion of certain items conditional.
You may be looking for a sysadmin or a developer position, for example.
With this you can produce different flavors of your resume from the same source...

It can also make your resume easier to search some day — when the search engines recognize this particular XML-template...

There is certainly nothing "gimmicky" about it — this sort of thing is, what XML is best suited for...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781335</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781125</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>houstonbofh</author>
	<datestamp>1255787160000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>I have not had a 1 page resume in 20 years.  I seem to make all the automated HR filters too...  I just wonder if that is connected?<nobr> <wbr></nobr>:)<br> <br>
A friend and I were co-workers in a company that went bust.  We had almost the same job and almost the same experience.  We both applied at the same company, and I got a call back and a job.  He never got a call back.  My new boss asked if I knew anyone else.  I said, "Uh, Yes?" and told him about my friend.  He never saw the resume.  I got it for him and he hired my friend as well.  HR was pissed at him for at least 2 years.<nobr> <wbr></nobr>:)  He is still there, and I have long since left.  HR is worthless...</htmltext>
<tokenext>I have not had a 1 page resume in 20 years .
I seem to make all the automated HR filters too... I just wonder if that is connected ?
: ) A friend and I were co-workers in a company that went bust .
We had almost the same job and almost the same experience .
We both applied at the same company , and I got a call back and a job .
He never got a call back .
My new boss asked if I knew anyone else .
I said , " Uh , Yes ?
" and told him about my friend .
He never saw the resume .
I got it for him and he hired my friend as well .
HR was pissed at him for at least 2 years .
: ) He is still there , and I have long since left .
HR is worthless.. .</tokentext>
<sentencetext>I have not had a 1 page resume in 20 years.
I seem to make all the automated HR filters too...  I just wonder if that is connected?
:) 
A friend and I were co-workers in a company that went bust.
We had almost the same job and almost the same experience.
We both applied at the same company, and I got a call back and a job.
He never got a call back.
My new boss asked if I knew anyone else.
I said, "Uh, Yes?
" and told him about my friend.
He never saw the resume.
I got it for him and he hired my friend as well.
HR was pissed at him for at least 2 years.
:)  He is still there, and I have long since left.
HR is worthless...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783771</id>
	<title>Mistake in his resume</title>
	<author>MobyDisk</author>
	<datestamp>1255876620000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I think he didn't list his FOSS experience very well.  It says:</p><p><div class="quote"><p>Sole engineer for the GoTD program (http://sourceforge.net/projects/mgatdirector), an open source program for directing Go tournaments. GoTD integrates registration, player pairing, handicapping,<br>conict resolution, and results reporting into one easy-to-use interface.  GoTD is the rst and only open source program available for managing Go tournaments.</p></div><p>It sounds like he is selling the project, not himself.  In my experience, you don't say what the project did, you say the technologies it uses and what YOU did.  I might write:</p><p><div class="quote"><p>Sole engineer for the GoTD program (http://sourceforge.net/projects/mgatdirector), an open source program for directing Go tournaments written in C++/Qt. Ran on Linux, Windows, and Commodore 64.  Maintained project in source control via sourceforge.  Prioritized bug reports, applied fixes, and determined new features.  A forum was established to solicit feedback from customers.</p></div></div>
	</htmltext>
<tokenext>I think he did n't list his FOSS experience very well .
It says : Sole engineer for the GoTD program ( http : //sourceforge.net/projects/mgatdirector ) , an open source program for directing Go tournaments .
GoTD integrates registration , player pairing , handicapping,conict resolution , and results reporting into one easy-to-use interface .
GoTD is the rst and only open source program available for managing Go tournaments.It sounds like he is selling the project , not himself .
In my experience , you do n't say what the project did , you say the technologies it uses and what YOU did .
I might write : Sole engineer for the GoTD program ( http : //sourceforge.net/projects/mgatdirector ) , an open source program for directing Go tournaments written in C + + /Qt .
Ran on Linux , Windows , and Commodore 64 .
Maintained project in source control via sourceforge .
Prioritized bug reports , applied fixes , and determined new features .
A forum was established to solicit feedback from customers .</tokentext>
<sentencetext>I think he didn't list his FOSS experience very well.
It says:Sole engineer for the GoTD program (http://sourceforge.net/projects/mgatdirector), an open source program for directing Go tournaments.
GoTD integrates registration, player pairing, handicapping,conict resolution, and results reporting into one easy-to-use interface.
GoTD is the rst and only open source program available for managing Go tournaments.It sounds like he is selling the project, not himself.
In my experience, you don't say what the project did, you say the technologies it uses and what YOU did.
I might write:Sole engineer for the GoTD program (http://sourceforge.net/projects/mgatdirector), an open source program for directing Go tournaments written in C++/Qt.
Ran on Linux, Windows, and Commodore 64.
Maintained project in source control via sourceforge.
Prioritized bug reports, applied fixes, and determined new features.
A forum was established to solicit feedback from customers.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781055</id>
	<title>profit !</title>
	<author>Anonymous</author>
	<datestamp>1255786200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>step 1: get your resume posted on<nobr> <wbr></nobr>/. front page<br>step 2: ???<br>step 3: PROFIT !!!</p></htmltext>
<tokenext>step 1 : get your resume posted on / .
front pagestep 2 : ? ?
? step 3 : PROFIT ! !
!</tokentext>
<sentencetext>step 1: get your resume posted on /.
front pagestep 2: ??
?step 3: PROFIT !!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781789</id>
	<title>Re:Make a portfolio</title>
	<author>screeble</author>
	<datestamp>1255798080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's a really decent idea. I work for an ILEC. Technically, I'm in translations design but as a matter of need I've been hacking Asterisk code and building really locked-down carrier-grade debian and Ubuntu internal versions. Everything I do is completely outside of my job description and I've been trying to figure out a way to document my experience when my manager doesn't even really understand what it is that I actually do anymore.</p></htmltext>
<tokenext>That 's a really decent idea .
I work for an ILEC .
Technically , I 'm in translations design but as a matter of need I 've been hacking Asterisk code and building really locked-down carrier-grade debian and Ubuntu internal versions .
Everything I do is completely outside of my job description and I 've been trying to figure out a way to document my experience when my manager does n't even really understand what it is that I actually do anymore .</tokentext>
<sentencetext>That's a really decent idea.
I work for an ILEC.
Technically, I'm in translations design but as a matter of need I've been hacking Asterisk code and building really locked-down carrier-grade debian and Ubuntu internal versions.
Everything I do is completely outside of my job description and I've been trying to figure out a way to document my experience when my manager doesn't even really understand what it is that I actually do anymore.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781185</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783597</id>
	<title>Creator: Adobe InDesign CS4</title>
	<author>janwedekind</author>
	<datestamp>1255874580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sorry, but this is <b>not</b> the right tool to list FOSS experience. Next!</p></htmltext>
<tokenext>Sorry , but this is not the right tool to list FOSS experience .
Next !</tokentext>
<sentencetext>Sorry, but this is not the right tool to list FOSS experience.
Next!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781245</id>
	<title>Use big names</title>
	<author>Darkness404</author>
	<datestamp>1255789080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Depends which jobs you are applying for, but if you aren't going into a super technology-based field (such as if you are applying to be a sysadmin at a local business, not applying for Google, MS or IBM) use big recognizable names. Even if you only submitted a small patch for the Linux kernel, saying that you have developed part of the Linux kernel might just be what is needed on your resume. Other large projects such as Firefox, Open Office, and other things that the people in HR recognize might just make them think you are great at your job even if its only tiny patches you submitted.</htmltext>
<tokenext>Depends which jobs you are applying for , but if you are n't going into a super technology-based field ( such as if you are applying to be a sysadmin at a local business , not applying for Google , MS or IBM ) use big recognizable names .
Even if you only submitted a small patch for the Linux kernel , saying that you have developed part of the Linux kernel might just be what is needed on your resume .
Other large projects such as Firefox , Open Office , and other things that the people in HR recognize might just make them think you are great at your job even if its only tiny patches you submitted .</tokentext>
<sentencetext>Depends which jobs you are applying for, but if you aren't going into a super technology-based field (such as if you are applying to be a sysadmin at a local business, not applying for Google, MS or IBM) use big recognizable names.
Even if you only submitted a small patch for the Linux kernel, saying that you have developed part of the Linux kernel might just be what is needed on your resume.
Other large projects such as Firefox, Open Office, and other things that the people in HR recognize might just make them think you are great at your job even if its only tiny patches you submitted.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783233</id>
	<title>DON'T!</title>
	<author>Anonymous</author>
	<datestamp>1255869360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>do not mention any FOSS activities to anybody! i mean it! also try making money with something that pays, like e.g. drug dealing or gun slinging, so that you have enough money and time to develop real cool free software. you could also sneak plutonium into iran or ask The Melvins if they need a new roadie...</p></htmltext>
<tokenext>do not mention any FOSS activities to anybody !
i mean it !
also try making money with something that pays , like e.g .
drug dealing or gun slinging , so that you have enough money and time to develop real cool free software .
you could also sneak plutonium into iran or ask The Melvins if they need a new roadie.. .</tokentext>
<sentencetext>do not mention any FOSS activities to anybody!
i mean it!
also try making money with something that pays, like e.g.
drug dealing or gun slinging, so that you have enough money and time to develop real cool free software.
you could also sneak plutonium into iran or ask The Melvins if they need a new roadie...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29787053</id>
	<title>Re:Mistake in his resume</title>
	<author>zgrossbart</author>
	<datestamp>1255861320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I completely understand what you mean here.  I was really torn about what to say.  I went the way I did because I was the creator of the project.  I wanted to highlight not only programming skills, but organizational and product design skills as well.

Designing an open source project and getting it off the ground takes a different set of skills than contributing to an existing project.  If you're the creator of the project you should highlight that.

Having said all of that, I really like your copy.  It is tight and clear while doing a good job describing what you did.</htmltext>
<tokenext>I completely understand what you mean here .
I was really torn about what to say .
I went the way I did because I was the creator of the project .
I wanted to highlight not only programming skills , but organizational and product design skills as well .
Designing an open source project and getting it off the ground takes a different set of skills than contributing to an existing project .
If you 're the creator of the project you should highlight that .
Having said all of that , I really like your copy .
It is tight and clear while doing a good job describing what you did .</tokentext>
<sentencetext>I completely understand what you mean here.
I was really torn about what to say.
I went the way I did because I was the creator of the project.
I wanted to highlight not only programming skills, but organizational and product design skills as well.
Designing an open source project and getting it off the ground takes a different set of skills than contributing to an existing project.
If you're the creator of the project you should highlight that.
Having said all of that, I really like your copy.
It is tight and clear while doing a good job describing what you did.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29784115</id>
	<title>Put all projects together</title>
	<author>jackhererUK</author>
	<datestamp>1255879920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Most tech cvs/resumes i have seen list the various projects worked on in the career history section.  If you wanted to include open source projects that don't relate to a specific job then you could have a cut down career history section with just an explanation of each job and then split out the projects into a seperate section.  You could then just put a reference with each project to say which job or open source project it related to.  That way your commercial work and open source work get equal precedence and you don't have to relegate your open source projects to their own little ghetto.</htmltext>
<tokenext>Most tech cvs/resumes i have seen list the various projects worked on in the career history section .
If you wanted to include open source projects that do n't relate to a specific job then you could have a cut down career history section with just an explanation of each job and then split out the projects into a seperate section .
You could then just put a reference with each project to say which job or open source project it related to .
That way your commercial work and open source work get equal precedence and you do n't have to relegate your open source projects to their own little ghetto .</tokentext>
<sentencetext>Most tech cvs/resumes i have seen list the various projects worked on in the career history section.
If you wanted to include open source projects that don't relate to a specific job then you could have a cut down career history section with just an explanation of each job and then split out the projects into a seperate section.
You could then just put a reference with each project to say which job or open source project it related to.
That way your commercial work and open source work get equal precedence and you don't have to relegate your open source projects to their own little ghetto.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783381</id>
	<title>Re:"Meetings"?</title>
	<author>mrmeval</author>
	<datestamp>1255871700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They are the holy writ of corprat Amerika. If you don't know what they mean you're a FOSS sideliner who is a marginal twit of no merit or competence. If you are not spending 10 hours out of 40 in meetings you are NOT DOING YOUR CORPRAT duty and need expelled into the sewer of FOSS.</p><p>Scum sucking malcontent!</p></htmltext>
<tokenext>They are the holy writ of corprat Amerika .
If you do n't know what they mean you 're a FOSS sideliner who is a marginal twit of no merit or competence .
If you are not spending 10 hours out of 40 in meetings you are NOT DOING YOUR CORPRAT duty and need expelled into the sewer of FOSS.Scum sucking malcontent !</tokentext>
<sentencetext>They are the holy writ of corprat Amerika.
If you don't know what they mean you're a FOSS sideliner who is a marginal twit of no merit or competence.
If you are not spending 10 hours out of 40 in meetings you are NOT DOING YOUR CORPRAT duty and need expelled into the sewer of FOSS.Scum sucking malcontent!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781253</id>
	<title>Uh easy...</title>
	<author>Blakey Rat</author>
	<datestamp>1255789140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Press "enter" after one of your job bulletpoints to make a new list items. Type in your role on the project, the name of the project, then the dates during which you worked on it. Provide a short description of the work you did, and how it impacted the success of the project.</p><p>Done.</p></htmltext>
<tokenext>Press " enter " after one of your job bulletpoints to make a new list items .
Type in your role on the project , the name of the project , then the dates during which you worked on it .
Provide a short description of the work you did , and how it impacted the success of the project.Done .</tokentext>
<sentencetext>Press "enter" after one of your job bulletpoints to make a new list items.
Type in your role on the project, the name of the project, then the dates during which you worked on it.
Provide a short description of the work you did, and how it impacted the success of the project.Done.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065</id>
	<title>His formatting article might be interesting,</title>
	<author>adonoman</author>
	<datestamp>1255786320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>except that that resume looks like crap.  He spends all this time worrying about serifs and ligatures, when as a whole it's nearly illegible.  It's all crowded into the page in what seems to the eye like one big chunk of prose.  It hurts my eyes just trying to read the text.  There are places for bullets - and lists of things is a good place for them.  A separating space or line here or there isn't going to kill anyone.  Also, it's not a sin to use two pages so that you don't have to pack everything in.</htmltext>
<tokenext>except that that resume looks like crap .
He spends all this time worrying about serifs and ligatures , when as a whole it 's nearly illegible .
It 's all crowded into the page in what seems to the eye like one big chunk of prose .
It hurts my eyes just trying to read the text .
There are places for bullets - and lists of things is a good place for them .
A separating space or line here or there is n't going to kill anyone .
Also , it 's not a sin to use two pages so that you do n't have to pack everything in .</tokentext>
<sentencetext>except that that resume looks like crap.
He spends all this time worrying about serifs and ligatures, when as a whole it's nearly illegible.
It's all crowded into the page in what seems to the eye like one big chunk of prose.
It hurts my eyes just trying to read the text.
There are places for bullets - and lists of things is a good place for them.
A separating space or line here or there isn't going to kill anyone.
Also, it's not a sin to use two pages so that you don't have to pack everything in.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781047</id>
	<title>Open source.</title>
	<author>Anonymous</author>
	<datestamp>1255786080000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Why not just show them what you did?</htmltext>
<tokenext>Why not just show them what you did ?</tokentext>
<sentencetext>Why not just show them what you did?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781931</id>
	<title>as someone who does hiring...</title>
	<author>timmarhy</author>
	<datestamp>1255800420000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>... let me give you 3 rules.<p>
1. only list relevant experience, if your applying for a DBA position i don't want to waste time reading about how you enjoy cake decorating.</p><p>
2. put the good stuff first, i need to skim 100's of these resumes so having to read till page 10 isn't helping your chances that'll see your skills.</p><p>
3. keep the format clean and easy to read, don't make my eye's bleed because your going in the bin after page one with pink curly fonts.</p></htmltext>
<tokenext>... let me give you 3 rules .
1. only list relevant experience , if your applying for a DBA position i do n't want to waste time reading about how you enjoy cake decorating .
2. put the good stuff first , i need to skim 100 's of these resumes so having to read till page 10 is n't helping your chances that 'll see your skills .
3. keep the format clean and easy to read , do n't make my eye 's bleed because your going in the bin after page one with pink curly fonts .</tokentext>
<sentencetext>... let me give you 3 rules.
1. only list relevant experience, if your applying for a DBA position i don't want to waste time reading about how you enjoy cake decorating.
2. put the good stuff first, i need to skim 100's of these resumes so having to read till page 10 isn't helping your chances that'll see your skills.
3. keep the format clean and easy to read, don't make my eye's bleed because your going in the bin after page one with pink curly fonts.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783167</id>
	<title>Not important</title>
	<author>obarthelemy</author>
	<datestamp>1255868100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Whether a project you worked on was open source or not is of no great importance. Treat it as you would any work experience: emphasize the skills used and learned, technically and socially, the tools, environment, and technologies you worked with.. You don't want to look like a commie zealot, anyway, so don't rant about FOSS on your r&#233;sum&#233;.</p><p>Aside form the "like a job" experience, the best selling point of voluntary FOSS involvement is that it shows you like your work.</p></htmltext>
<tokenext>Whether a project you worked on was open source or not is of no great importance .
Treat it as you would any work experience : emphasize the skills used and learned , technically and socially , the tools , environment , and technologies you worked with.. You do n't want to look like a commie zealot , anyway , so do n't rant about FOSS on your r   sum   .Aside form the " like a job " experience , the best selling point of voluntary FOSS involvement is that it shows you like your work .</tokentext>
<sentencetext>Whether a project you worked on was open source or not is of no great importance.
Treat it as you would any work experience: emphasize the skills used and learned, technically and socially, the tools, environment, and technologies you worked with.. You don't want to look like a commie zealot, anyway, so don't rant about FOSS on your résumé.Aside form the "like a job" experience, the best selling point of voluntary FOSS involvement is that it shows you like your work.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783081</id>
	<title>On that note...</title>
	<author>puroresu</author>
	<datestamp>1255865520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>...if you have what would be termed an "unconventional" appearance by more narrow minded employers, consider the kind of companies which are more likely to hire you.
<br> <br>
I have long hair, facial hair and tattoos. I recently took a temp contract with a publishing company. They didn't have a "dress code" as such and the atmosphere was pretty relaxed. A few weeks later they asked if I'd run the department. Plenty of businesses operate under similar conditions, and unlike places which mandate a particular look, they tend not to treat employees like shit.
<br> <br>
Will you alienate some employers by not having a short back and sides and a clean shave? Yes.<br>Are they worth working for? Not in my opinion.</htmltext>
<tokenext>...if you have what would be termed an " unconventional " appearance by more narrow minded employers , consider the kind of companies which are more likely to hire you .
I have long hair , facial hair and tattoos .
I recently took a temp contract with a publishing company .
They did n't have a " dress code " as such and the atmosphere was pretty relaxed .
A few weeks later they asked if I 'd run the department .
Plenty of businesses operate under similar conditions , and unlike places which mandate a particular look , they tend not to treat employees like shit .
Will you alienate some employers by not having a short back and sides and a clean shave ?
Yes.Are they worth working for ?
Not in my opinion .</tokentext>
<sentencetext>...if you have what would be termed an "unconventional" appearance by more narrow minded employers, consider the kind of companies which are more likely to hire you.
I have long hair, facial hair and tattoos.
I recently took a temp contract with a publishing company.
They didn't have a "dress code" as such and the atmosphere was pretty relaxed.
A few weeks later they asked if I'd run the department.
Plenty of businesses operate under similar conditions, and unlike places which mandate a particular look, they tend not to treat employees like shit.
Will you alienate some employers by not having a short back and sides and a clean shave?
Yes.Are they worth working for?
Not in my opinion.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781711</id>
	<title>Stretching it</title>
	<author>dirkdodgers</author>
	<datestamp>1255796460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Listing FOSS contributions outside of Other Experience can look like stretching, and is stretching unless it's either something you're spending, say, 20+ hours/week on, or you're applying for your first position out of school. If you're not, it's not really the kind of professional experience you want to showcase, is it?</p><p>Even if you're spending substantial time on a FOSS project, you still may not want to list it outside of Other Experience other than to explain what you have been doing in the time since your most recent employment.</p><p>What you don't want to do is give the impression that you're trying to cover up for being under-qualified, for lacking in professional experience, or that you're not employable in a traditional position.</p></htmltext>
<tokenext>Listing FOSS contributions outside of Other Experience can look like stretching , and is stretching unless it 's either something you 're spending , say , 20 + hours/week on , or you 're applying for your first position out of school .
If you 're not , it 's not really the kind of professional experience you want to showcase , is it ? Even if you 're spending substantial time on a FOSS project , you still may not want to list it outside of Other Experience other than to explain what you have been doing in the time since your most recent employment.What you do n't want to do is give the impression that you 're trying to cover up for being under-qualified , for lacking in professional experience , or that you 're not employable in a traditional position .</tokentext>
<sentencetext>Listing FOSS contributions outside of Other Experience can look like stretching, and is stretching unless it's either something you're spending, say, 20+ hours/week on, or you're applying for your first position out of school.
If you're not, it's not really the kind of professional experience you want to showcase, is it?Even if you're spending substantial time on a FOSS project, you still may not want to list it outside of Other Experience other than to explain what you have been doing in the time since your most recent employment.What you don't want to do is give the impression that you're trying to cover up for being under-qualified, for lacking in professional experience, or that you're not employable in a traditional position.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782661</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>houghi</author>
	<datestamp>1255857060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>HR is not worthless, it is just that they should not do the shifting of the jobs. They think it is a service and an obligation to do this for the rest of the company.</p><p>The ideal solution is:<br>1) selection by the department. Get down to e.g. 10 people you want to see)<br>2) First interview by the department and somebody from HR.</p><p>HR do have people (or should have people) who can ask better questions about personality and notice often better if that are any holes in their story. They do not know what kind of skills that person needs and won't know what kind of person you are looking for. No matter how often you explain it to them. Not their fold they can not look into your head.</p><p>It is as if you say that you like blondes and the one you marry is a brunette. Sometimes you see a combination of things that makes it overrule the things you said before and it would be a pitty if that one you would never meet, because somebody says "he does not like brunettes".</p><p>Same with the shifting by HR. You might find the ideal person in the pile that they trow away.</p><p>Sell this to HR as doing them a favour by taking some workload of their back without costing them money or budget.</p></htmltext>
<tokenext>HR is not worthless , it is just that they should not do the shifting of the jobs .
They think it is a service and an obligation to do this for the rest of the company.The ideal solution is : 1 ) selection by the department .
Get down to e.g .
10 people you want to see ) 2 ) First interview by the department and somebody from HR.HR do have people ( or should have people ) who can ask better questions about personality and notice often better if that are any holes in their story .
They do not know what kind of skills that person needs and wo n't know what kind of person you are looking for .
No matter how often you explain it to them .
Not their fold they can not look into your head.It is as if you say that you like blondes and the one you marry is a brunette .
Sometimes you see a combination of things that makes it overrule the things you said before and it would be a pitty if that one you would never meet , because somebody says " he does not like brunettes " .Same with the shifting by HR .
You might find the ideal person in the pile that they trow away.Sell this to HR as doing them a favour by taking some workload of their back without costing them money or budget .</tokentext>
<sentencetext>HR is not worthless, it is just that they should not do the shifting of the jobs.
They think it is a service and an obligation to do this for the rest of the company.The ideal solution is:1) selection by the department.
Get down to e.g.
10 people you want to see)2) First interview by the department and somebody from HR.HR do have people (or should have people) who can ask better questions about personality and notice often better if that are any holes in their story.
They do not know what kind of skills that person needs and won't know what kind of person you are looking for.
No matter how often you explain it to them.
Not their fold they can not look into your head.It is as if you say that you like blondes and the one you marry is a brunette.
Sometimes you see a combination of things that makes it overrule the things you said before and it would be a pitty if that one you would never meet, because somebody says "he does not like brunettes".Same with the shifting by HR.
You might find the ideal person in the pile that they trow away.Sell this to HR as doing them a favour by taking some workload of their back without costing them money or budget.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781125</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063</id>
	<title>"Meetings"?</title>
	<author>John Hasler</author>
	<datestamp>1255786320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>&gt; Did you lead meetings?</p><p>What are these "meetings" you speak of?</p></htmltext>
<tokenext>&gt; Did you lead meetings ? What are these " meetings " you speak of ?</tokentext>
<sentencetext>&gt; Did you lead meetings?What are these "meetings" you speak of?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29784443</id>
	<title>Re:How to format? Is not it about CONTENT?</title>
	<author>he-sk</author>
	<datestamp>1255882740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Worry about the content, not the presentation" is probably the reason why most programs (FOSS and commercial) suck donkey ass.</p><p>Ome of the most important thing about any tool is the workflow it supports and encourages.  Presentation is a critical part of the picture.</p></htmltext>
<tokenext>" Worry about the content , not the presentation " is probably the reason why most programs ( FOSS and commercial ) suck donkey ass.Ome of the most important thing about any tool is the workflow it supports and encourages .
Presentation is a critical part of the picture .</tokentext>
<sentencetext>"Worry about the content, not the presentation" is probably the reason why most programs (FOSS and commercial) suck donkey ass.Ome of the most important thing about any tool is the workflow it supports and encourages.
Presentation is a critical part of the picture.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783287</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>l3v1</author>
	<datestamp>1255870020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>This guy is so good at writing resumes that he tells the rest of us how to write them as a job</i> <br> <br>
Life can be a weird place. Like where someone having the guts stands up and says "I know stuff", then people around him who either don't know stuff or are just numb or shy or unexperienced say "look, he knows stuff", and after a while a lot of people will know that there's a guy who knows stuff. At that point, that fella doesn't even need to know anything anymore.</htmltext>
<tokenext>This guy is so good at writing resumes that he tells the rest of us how to write them as a job Life can be a weird place .
Like where someone having the guts stands up and says " I know stuff " , then people around him who either do n't know stuff or are just numb or shy or unexperienced say " look , he knows stuff " , and after a while a lot of people will know that there 's a guy who knows stuff .
At that point , that fella does n't even need to know anything anymore .</tokentext>
<sentencetext>This guy is so good at writing resumes that he tells the rest of us how to write them as a job  
Life can be a weird place.
Like where someone having the guts stands up and says "I know stuff", then people around him who either don't know stuff or are just numb or shy or unexperienced say "look, he knows stuff", and after a while a lot of people will know that there's a guy who knows stuff.
At that point, that fella doesn't even need to know anything anymore.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781431</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29785979</id>
	<title>Re:Why should I care about this douchebag's</title>
	<author>noidentity</author>
	<datestamp>1255896420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Blah blah blah, try 30 different fonts. Blah blah blah, try 20 different text editors. And HR will still want a copy in word format or plain text format, ignore any formatting, and keyword scan.

</p><p>My resume is done in latex.</p></div>
</blockquote><p>Oh my. What kind of job were we discussing again?</p></div>
	</htmltext>
<tokenext>Blah blah blah , try 30 different fonts .
Blah blah blah , try 20 different text editors .
And HR will still want a copy in word format or plain text format , ignore any formatting , and keyword scan .
My resume is done in latex .
Oh my .
What kind of job were we discussing again ?</tokentext>
<sentencetext>Blah blah blah, try 30 different fonts.
Blah blah blah, try 20 different text editors.
And HR will still want a copy in word format or plain text format, ignore any formatting, and keyword scan.
My resume is done in latex.
Oh my.
What kind of job were we discussing again?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781397</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781017</id>
	<title>FOSSt post!</title>
	<author>Anonymous</author>
	<datestamp>1255785540000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext>FOSSt post, biyatches!</htmltext>
<tokenext>FOSSt post , biyatches !</tokentext>
<sentencetext>FOSSt post, biyatches!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781431</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>kestasjk</author>
	<datestamp>1255791420000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>This guy is so good at writing resumes that he tells the rest of us how to write them as a job; what more proof do you need that he must have an excellent resume?</htmltext>
<tokenext>This guy is so good at writing resumes that he tells the rest of us how to write them as a job ; what more proof do you need that he must have an excellent resume ?</tokentext>
<sentencetext>This guy is so good at writing resumes that he tells the rest of us how to write them as a job; what more proof do you need that he must have an excellent resume?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781185</id>
	<title>Make a portfolio</title>
	<author>wrook</author>
	<datestamp>1255788060000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>Make a portfolio of open source work you've done.  Go in and extract code that you've written.  Annotate it explaining what problem you were solving and why you chose the design you did, etc.  Keep each section fairly short (a few hundred lines of code) and write an overall document linking up the various code excerpts, creating a narrative for them to follow.  If you have planning/design documentation, etc feel free to show excerpts of that too.  Even emails from mailing lists where you defused a potentially difficult situation is good.  Finally, provide links to all the original projects that you've contributed to so they can see  your contribution first hand.</p><p>After you have organized all that, put it up on a web page somewhere and put a link on your resume.  Burn a few business card sized CDs and hand them out at interviews.  Make sure to bring a few to each interview.  I've found they are popular.</p><p>This has gotten me more than one job.  I used to maintain my portfolio continuously on my web page, but I'm teaching now and have let it lapse.  However, it's sometimes useful even outside the job searching venue.</p></htmltext>
<tokenext>Make a portfolio of open source work you 've done .
Go in and extract code that you 've written .
Annotate it explaining what problem you were solving and why you chose the design you did , etc .
Keep each section fairly short ( a few hundred lines of code ) and write an overall document linking up the various code excerpts , creating a narrative for them to follow .
If you have planning/design documentation , etc feel free to show excerpts of that too .
Even emails from mailing lists where you defused a potentially difficult situation is good .
Finally , provide links to all the original projects that you 've contributed to so they can see your contribution first hand.After you have organized all that , put it up on a web page somewhere and put a link on your resume .
Burn a few business card sized CDs and hand them out at interviews .
Make sure to bring a few to each interview .
I 've found they are popular.This has gotten me more than one job .
I used to maintain my portfolio continuously on my web page , but I 'm teaching now and have let it lapse .
However , it 's sometimes useful even outside the job searching venue .</tokentext>
<sentencetext>Make a portfolio of open source work you've done.
Go in and extract code that you've written.
Annotate it explaining what problem you were solving and why you chose the design you did, etc.
Keep each section fairly short (a few hundred lines of code) and write an overall document linking up the various code excerpts, creating a narrative for them to follow.
If you have planning/design documentation, etc feel free to show excerpts of that too.
Even emails from mailing lists where you defused a potentially difficult situation is good.
Finally, provide links to all the original projects that you've contributed to so they can see  your contribution first hand.After you have organized all that, put it up on a web page somewhere and put a link on your resume.
Burn a few business card sized CDs and hand them out at interviews.
Make sure to bring a few to each interview.
I've found they are popular.This has gotten me more than one job.
I used to maintain my portfolio continuously on my web page, but I'm teaching now and have let it lapse.
However, it's sometimes useful even outside the job searching venue.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781211</id>
	<title>Re:"Meetings"?</title>
	<author>Threni</author>
	<datestamp>1255788600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>If you're putting together a resume then you're looking for a job, and if you get a job, you're going to have to endure brain numbing meetings where your boss will ask you the same question you've answered at least 3 times that much, knowing full well that he won't understand and will ask you again in a few days.  The meeting will waste your time, and not express any information you couldn't have committed to writing in an email.  But it will pass an hour of your - and more importantly, your bosses - time, and given that bosses don't work but instead just attend meetings and try and make comments to suggest that they in some way add value to the company they work for, you'd better get used to it sooner rather than later.</p></htmltext>
<tokenext>If you 're putting together a resume then you 're looking for a job , and if you get a job , you 're going to have to endure brain numbing meetings where your boss will ask you the same question you 've answered at least 3 times that much , knowing full well that he wo n't understand and will ask you again in a few days .
The meeting will waste your time , and not express any information you could n't have committed to writing in an email .
But it will pass an hour of your - and more importantly , your bosses - time , and given that bosses do n't work but instead just attend meetings and try and make comments to suggest that they in some way add value to the company they work for , you 'd better get used to it sooner rather than later .</tokentext>
<sentencetext>If you're putting together a resume then you're looking for a job, and if you get a job, you're going to have to endure brain numbing meetings where your boss will ask you the same question you've answered at least 3 times that much, knowing full well that he won't understand and will ask you again in a few days.
The meeting will waste your time, and not express any information you couldn't have committed to writing in an email.
But it will pass an hour of your - and more importantly, your bosses - time, and given that bosses don't work but instead just attend meetings and try and make comments to suggest that they in some way add value to the company they work for, you'd better get used to it sooner rather than later.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781785</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>Eskarel</author>
	<datestamp>1255797900000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>He's actually a pretty good example of everything you shouldn't do with your Resume.</p><p>There's a lot to be said for being concise in your resume, and the first page is the one which gets the most attention. The problem is that this doesn't mean you should cram everything you have onto one page, since one unreadable page is worse than 20 you can actually parse properly.</p><p>The reason for a one page resume is that your resume will appear in a gigantic stack of other resumes. If you're really lucky it might be being looked at by someone who actually understands the field, but that person is likely to be busy. They're not going to spend an hour carefully reading each resume, they're going to try to cull that gigantic pile down to a short list as quickly as possible. I can honestly say that, as someone who has been asked for a technical opinion on resumes for the area this guy works in, I'd have binned it because there would almost certainly have been someone(possibly someone with far less experience) whose resume showed me that experience in a more meaningful manner.</p><p>This is all a bit sad since I happen to have worked with a lot of the stuff he's apparently actually written, and they're not my favorite examples of the product line, they were well coded and not particularly buggy or difficult to work with. The guy has a lot of years of very solid experience, but he has no idea how to actually apply for a job. This isn't all that surprising since from the looks of his resume, he started off as a consultant, got hired onto one of the firms he was consulting with, which then got bought by Novell, and he hasn't actually gone job hunting in more than a decade. Depending on his age(and whether there's any additional experience he's left off), he may have only ever actually gone job hunting once in his entire life</p></htmltext>
<tokenext>He 's actually a pretty good example of everything you should n't do with your Resume.There 's a lot to be said for being concise in your resume , and the first page is the one which gets the most attention .
The problem is that this does n't mean you should cram everything you have onto one page , since one unreadable page is worse than 20 you can actually parse properly.The reason for a one page resume is that your resume will appear in a gigantic stack of other resumes .
If you 're really lucky it might be being looked at by someone who actually understands the field , but that person is likely to be busy .
They 're not going to spend an hour carefully reading each resume , they 're going to try to cull that gigantic pile down to a short list as quickly as possible .
I can honestly say that , as someone who has been asked for a technical opinion on resumes for the area this guy works in , I 'd have binned it because there would almost certainly have been someone ( possibly someone with far less experience ) whose resume showed me that experience in a more meaningful manner.This is all a bit sad since I happen to have worked with a lot of the stuff he 's apparently actually written , and they 're not my favorite examples of the product line , they were well coded and not particularly buggy or difficult to work with .
The guy has a lot of years of very solid experience , but he has no idea how to actually apply for a job .
This is n't all that surprising since from the looks of his resume , he started off as a consultant , got hired onto one of the firms he was consulting with , which then got bought by Novell , and he has n't actually gone job hunting in more than a decade .
Depending on his age ( and whether there 's any additional experience he 's left off ) , he may have only ever actually gone job hunting once in his entire life</tokentext>
<sentencetext>He's actually a pretty good example of everything you shouldn't do with your Resume.There's a lot to be said for being concise in your resume, and the first page is the one which gets the most attention.
The problem is that this doesn't mean you should cram everything you have onto one page, since one unreadable page is worse than 20 you can actually parse properly.The reason for a one page resume is that your resume will appear in a gigantic stack of other resumes.
If you're really lucky it might be being looked at by someone who actually understands the field, but that person is likely to be busy.
They're not going to spend an hour carefully reading each resume, they're going to try to cull that gigantic pile down to a short list as quickly as possible.
I can honestly say that, as someone who has been asked for a technical opinion on resumes for the area this guy works in, I'd have binned it because there would almost certainly have been someone(possibly someone with far less experience) whose resume showed me that experience in a more meaningful manner.This is all a bit sad since I happen to have worked with a lot of the stuff he's apparently actually written, and they're not my favorite examples of the product line, they were well coded and not particularly buggy or difficult to work with.
The guy has a lot of years of very solid experience, but he has no idea how to actually apply for a job.
This isn't all that surprising since from the looks of his resume, he started off as a consultant, got hired onto one of the firms he was consulting with, which then got bought by Novell, and he hasn't actually gone job hunting in more than a decade.
Depending on his age(and whether there's any additional experience he's left off), he may have only ever actually gone job hunting once in his entire life</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783265</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>l3v1</author>
	<datestamp>1255869780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>I have not had a 1 page resume in 20 years. I seem to make all the automated HR filters too... I just wonder if that is connected?<nobr> <wbr></nobr>:)</i> <br> <br>
The one-page resume was invented by people who don't have anything meaningful to fill more than a page with, and by idiot HR people who are lazy to carefully evaluate CVs.<br> <br>
That said, when I see someone fill a page with stuff that for me and my colleagues is a nornal daily routine trying to sell it as something exceptional (well, age can become an issue here), now that's when I know someone's full of crap.<br> <br>
Also, those HR people who only hunt for buzzwords... wake up and smell the coffee. Wait, you don't have to, you already have the job you wanted, right?</htmltext>
<tokenext>I have not had a 1 page resume in 20 years .
I seem to make all the automated HR filters too... I just wonder if that is connected ?
: ) The one-page resume was invented by people who do n't have anything meaningful to fill more than a page with , and by idiot HR people who are lazy to carefully evaluate CVs .
That said , when I see someone fill a page with stuff that for me and my colleagues is a nornal daily routine trying to sell it as something exceptional ( well , age can become an issue here ) , now that 's when I know someone 's full of crap .
Also , those HR people who only hunt for buzzwords... wake up and smell the coffee .
Wait , you do n't have to , you already have the job you wanted , right ?</tokentext>
<sentencetext>I have not had a 1 page resume in 20 years.
I seem to make all the automated HR filters too... I just wonder if that is connected?
:)  
The one-page resume was invented by people who don't have anything meaningful to fill more than a page with, and by idiot HR people who are lazy to carefully evaluate CVs.
That said, when I see someone fill a page with stuff that for me and my colleagues is a nornal daily routine trying to sell it as something exceptional (well, age can become an issue here), now that's when I know someone's full of crap.
Also, those HR people who only hunt for buzzwords... wake up and smell the coffee.
Wait, you don't have to, you already have the job you wanted, right?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781125</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29788755</id>
	<title>There are other issues</title>
	<author>Anonymous</author>
	<datestamp>1255877040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>To answer the main question, say what you did. If it's minor (like mine), just put it under "other experience." If your resume makes it up past HR to a techie, he will notice it. Unlike HR most technically-competent interviewers have fewer resumes to process and are detail-oriented. Most have asked about my OSS experience even though its only a couple of sentences under "other experience". OSS experience rarely counts for anything to a HR person, unless they are specifically looking for an OSS package or technology.</p><p>Zack's resume fails in certain regards:<br>- too damn squeezed<br>- bullet points and keywords<br>- what are your achievements? Quantify them<br>- keyword spam like "technical skills" belong at the end. on a second page if necessary (only bots and crawlers go there. humans from HR stop at the first page)<br>- "references available" and your snail mail address are redundant and should be reserved for when you have space to spare<br>- with &gt;10 years of experience, you deserve a second page. But do prepare a short 1-pager for the HR drones.</p></htmltext>
<tokenext>To answer the main question , say what you did .
If it 's minor ( like mine ) , just put it under " other experience .
" If your resume makes it up past HR to a techie , he will notice it .
Unlike HR most technically-competent interviewers have fewer resumes to process and are detail-oriented .
Most have asked about my OSS experience even though its only a couple of sentences under " other experience " .
OSS experience rarely counts for anything to a HR person , unless they are specifically looking for an OSS package or technology.Zack 's resume fails in certain regards : - too damn squeezed- bullet points and keywords- what are your achievements ?
Quantify them- keyword spam like " technical skills " belong at the end .
on a second page if necessary ( only bots and crawlers go there .
humans from HR stop at the first page ) - " references available " and your snail mail address are redundant and should be reserved for when you have space to spare- with &gt; 10 years of experience , you deserve a second page .
But do prepare a short 1-pager for the HR drones .</tokentext>
<sentencetext>To answer the main question, say what you did.
If it's minor (like mine), just put it under "other experience.
" If your resume makes it up past HR to a techie, he will notice it.
Unlike HR most technically-competent interviewers have fewer resumes to process and are detail-oriented.
Most have asked about my OSS experience even though its only a couple of sentences under "other experience".
OSS experience rarely counts for anything to a HR person, unless they are specifically looking for an OSS package or technology.Zack's resume fails in certain regards:- too damn squeezed- bullet points and keywords- what are your achievements?
Quantify them- keyword spam like "technical skills" belong at the end.
on a second page if necessary (only bots and crawlers go there.
humans from HR stop at the first page)- "references available" and your snail mail address are redundant and should be reserved for when you have space to spare- with &gt;10 years of experience, you deserve a second page.
But do prepare a short 1-pager for the HR drones.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781453</id>
	<title>Re:How to format? Is not it about CONTENT?</title>
	<author>buchner.johannes</author>
	<datestamp>1255791840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yes, knowledge ontologies are the new hype in companies anyway</p></htmltext>
<tokenext>Yes , knowledge ontologies are the new hype in companies anyway</tokentext>
<sentencetext>Yes, knowledge ontologies are the new hype in companies anyway</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183</id>
	<title>How to format? Is not it about CONTENT?</title>
	<author>Anonymous</author>
	<datestamp>1255788060000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>Is not "worry about the content, not the presentation" the mantra around here? If we are supposed to follow that for the web-pages we produce, why should the resumes be different?

</p><p>One's resume should be in <a href="http://xmlresume.sourceforge.net/" title="sourceforge.net" rel="nofollow">XML</a> [sourceforge.net], from which various other formats can be produced automatically (and consistently)...</p></htmltext>
<tokenext>Is not " worry about the content , not the presentation " the mantra around here ?
If we are supposed to follow that for the web-pages we produce , why should the resumes be different ?
One 's resume should be in XML [ sourceforge.net ] , from which various other formats can be produced automatically ( and consistently ) .. .</tokentext>
<sentencetext>Is not "worry about the content, not the presentation" the mantra around here?
If we are supposed to follow that for the web-pages we produce, why should the resumes be different?
One's resume should be in XML [sourceforge.net], from which various other formats can be produced automatically (and consistently)...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783879</id>
	<title>Re:Stretching it</title>
	<author>panthrkub</author>
	<datestamp>1255877580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'll give you that HR in a typical corporate environment that doesn't leverage FOSS might not appreciate even a significant contribution to an open source project.

However, even the summary of this article mentions that this is for "the reader who is selling skills gained in an open source project".  So, uh...yeah.  Way to miss the point.</htmltext>
<tokenext>I 'll give you that HR in a typical corporate environment that does n't leverage FOSS might not appreciate even a significant contribution to an open source project .
However , even the summary of this article mentions that this is for " the reader who is selling skills gained in an open source project " .
So , uh...yeah .
Way to miss the point .</tokentext>
<sentencetext>I'll give you that HR in a typical corporate environment that doesn't leverage FOSS might not appreciate even a significant contribution to an open source project.
However, even the summary of this article mentions that this is for "the reader who is selling skills gained in an open source project".
So, uh...yeah.
Way to miss the point.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781711</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782425</id>
	<title>Why make this dificult?  K.I.S.S.</title>
	<author>Anonymous</author>
	<datestamp>1255896360000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Why would FOSS or volunteer work be any different than work you did for a pay check?</p><p>It goes on the Resume same as any other job.  I treat them with the exactly the same.</p><p>I read about data miners and other such rubbish filtering out FOSS and such type work.  Well that is complete and total non-sense.  Your resume is a record of your experience and accomplishments plain and simple.</p><p>Hear is some advice.</p><p>DO NOT MAKE YOUR RESUME OVERLY COMPLICATED.   You do not need 20 headings highlighting the different views of your career.  K.I.S.S.  Keep It Simple Stupid is the rule to follow.  Spend your effort on making sure that each piece of experience is effectively presented through a well written resume.</p><p>I use this rule of thumb.  I treat my resume/CV as a full time job for 1 week.  I spend no less than 40 hours working on it before any potential employer will see it. That's nto for every employer.  That's for each time I'm on the job market.  In North America no more than 4 pages EVER.  In other parts of the world they like to see as much as a page per year experience ( I know ridiculous ). So what if the agency filters it and puts into their format.  Let them.  You're bring fresh copies on PLAIN WHITE PAPER in B/W to the interview? Cause you should be slapped if you don't.  Oh gee all of a sudden your resume stands out in the pile of identical resumes in the stack.  Why? Because it is well formatted on quality WHITE paper.</p><p>I read a lot of resumes.  A LOT.  I toss almost all of the resumes that have pictures / fancy paper / more heft than a phone book into the bin before turning the first page.</p><p>------<br>Do NOT's<br>- Put your picture on the resume.  You are not that good looking.<br>- Use colored paper.  What are you 12?<br>- Use textured paper.  Again are you 12?<br>- Use multiple fonts.  Only use Helvetica. Why all printers have it and it looks clean and is easy to read.<br>- Leave half empty pages.  All pages should have a solid balance of text.  Half pages are tossed pages.<br>- Only use one recruiter.  Where is there a law that states you can only use one recruiter?<br>- Forget to shave.  Guys Gals,  it applies to both of you.  Clean looks get the jobs and more money.  Don't care if it's racist / prejudice or what ever complaint you have.  Clean looks always win.  Grow the pRon mustache after you get the job OK.</p></htmltext>
<tokenext>Why would FOSS or volunteer work be any different than work you did for a pay check ? It goes on the Resume same as any other job .
I treat them with the exactly the same.I read about data miners and other such rubbish filtering out FOSS and such type work .
Well that is complete and total non-sense .
Your resume is a record of your experience and accomplishments plain and simple.Hear is some advice.DO NOT MAKE YOUR RESUME OVERLY COMPLICATED .
You do not need 20 headings highlighting the different views of your career .
K.I.S.S. Keep It Simple Stupid is the rule to follow .
Spend your effort on making sure that each piece of experience is effectively presented through a well written resume.I use this rule of thumb .
I treat my resume/CV as a full time job for 1 week .
I spend no less than 40 hours working on it before any potential employer will see it .
That 's nto for every employer .
That 's for each time I 'm on the job market .
In North America no more than 4 pages EVER .
In other parts of the world they like to see as much as a page per year experience ( I know ridiculous ) .
So what if the agency filters it and puts into their format .
Let them .
You 're bring fresh copies on PLAIN WHITE PAPER in B/W to the interview ?
Cause you should be slapped if you do n't .
Oh gee all of a sudden your resume stands out in the pile of identical resumes in the stack .
Why ? Because it is well formatted on quality WHITE paper.I read a lot of resumes .
A LOT .
I toss almost all of the resumes that have pictures / fancy paper / more heft than a phone book into the bin before turning the first page.------Do NOT 's- Put your picture on the resume .
You are not that good looking.- Use colored paper .
What are you 12 ? - Use textured paper .
Again are you 12 ? - Use multiple fonts .
Only use Helvetica .
Why all printers have it and it looks clean and is easy to read.- Leave half empty pages .
All pages should have a solid balance of text .
Half pages are tossed pages.- Only use one recruiter .
Where is there a law that states you can only use one recruiter ? - Forget to shave .
Guys Gals , it applies to both of you .
Clean looks get the jobs and more money .
Do n't care if it 's racist / prejudice or what ever complaint you have .
Clean looks always win .
Grow the pRon mustache after you get the job OK .</tokentext>
<sentencetext>Why would FOSS or volunteer work be any different than work you did for a pay check?It goes on the Resume same as any other job.
I treat them with the exactly the same.I read about data miners and other such rubbish filtering out FOSS and such type work.
Well that is complete and total non-sense.
Your resume is a record of your experience and accomplishments plain and simple.Hear is some advice.DO NOT MAKE YOUR RESUME OVERLY COMPLICATED.
You do not need 20 headings highlighting the different views of your career.
K.I.S.S.  Keep It Simple Stupid is the rule to follow.
Spend your effort on making sure that each piece of experience is effectively presented through a well written resume.I use this rule of thumb.
I treat my resume/CV as a full time job for 1 week.
I spend no less than 40 hours working on it before any potential employer will see it.
That's nto for every employer.
That's for each time I'm on the job market.
In North America no more than 4 pages EVER.
In other parts of the world they like to see as much as a page per year experience ( I know ridiculous ).
So what if the agency filters it and puts into their format.
Let them.
You're bring fresh copies on PLAIN WHITE PAPER in B/W to the interview?
Cause you should be slapped if you don't.
Oh gee all of a sudden your resume stands out in the pile of identical resumes in the stack.
Why? Because it is well formatted on quality WHITE paper.I read a lot of resumes.
A LOT.
I toss almost all of the resumes that have pictures / fancy paper / more heft than a phone book into the bin before turning the first page.------Do NOT's- Put your picture on the resume.
You are not that good looking.- Use colored paper.
What are you 12?- Use textured paper.
Again are you 12?- Use multiple fonts.
Only use Helvetica.
Why all printers have it and it looks clean and is easy to read.- Leave half empty pages.
All pages should have a solid balance of text.
Half pages are tossed pages.- Only use one recruiter.
Where is there a law that states you can only use one recruiter?- Forget to shave.
Guys Gals,  it applies to both of you.
Clean looks get the jobs and more money.
Don't care if it's racist / prejudice or what ever complaint you have.
Clean looks always win.
Grow the pRon mustache after you get the job OK.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782453</id>
	<title>Re:How to format? Is not it about CONTENT?</title>
	<author>upuv</author>
	<datestamp>1255896840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>.doc MS word only still people.</p><p>The HR department can only open word 97 files.  Don't care how nerdy the job is.  HR is still in the stone age.</p><p>( Yes I took the bait )</p></htmltext>
<tokenext>.doc MS word only still people.The HR department can only open word 97 files .
Do n't care how nerdy the job is .
HR is still in the stone age .
( Yes I took the bait )</tokentext>
<sentencetext>.doc MS word only still people.The HR department can only open word 97 files.
Don't care how nerdy the job is.
HR is still in the stone age.
( Yes I took the bait )</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781397</id>
	<title>Why should I care about this douchebag's</title>
	<author>Anonymous</author>
	<datestamp>1255790880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>
opinion?  Blah blah blah, try 30 different fonts.  Blah blah blah, try 20 different text editors. And HR will still want a copy in word format or plain text format, ignore any formatting, and keyword scan.
</p><p>
My resume is done in latex.  Better font, better justification, better appearance.</p></htmltext>
<tokenext>opinion ?
Blah blah blah , try 30 different fonts .
Blah blah blah , try 20 different text editors .
And HR will still want a copy in word format or plain text format , ignore any formatting , and keyword scan .
My resume is done in latex .
Better font , better justification , better appearance .</tokentext>
<sentencetext>
opinion?
Blah blah blah, try 30 different fonts.
Blah blah blah, try 20 different text editors.
And HR will still want a copy in word format or plain text format, ignore any formatting, and keyword scan.
My resume is done in latex.
Better font, better justification, better appearance.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781127</id>
	<title>Re:His formatting article might be interesting,</title>
	<author>Z8</author>
	<datestamp>1255787160000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><blockquote><div><p>It's all crowded into the page in what seems to the eye like one big chunk of prose. It hurts my eyes just trying to read the text.</p></div></blockquote><p>

I hope you never accidentally open a book, you might go blind.</p></div>
	</htmltext>
<tokenext>It 's all crowded into the page in what seems to the eye like one big chunk of prose .
It hurts my eyes just trying to read the text .
I hope you never accidentally open a book , you might go blind .</tokentext>
<sentencetext>It's all crowded into the page in what seems to the eye like one big chunk of prose.
It hurts my eyes just trying to read the text.
I hope you never accidentally open a book, you might go blind.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781837</id>
	<title>Re:Open source.</title>
	<author>rubi</author>
	<datestamp>1255798980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Because HR is usually the one that is doing the initial interviews or creating the pool of candidates. So, showing what you have done is contingent in passing this initial filter or bypassing it somehow.</htmltext>
<tokenext>Because HR is usually the one that is doing the initial interviews or creating the pool of candidates .
So , showing what you have done is contingent in passing this initial filter or bypassing it somehow .</tokentext>
<sentencetext>Because HR is usually the one that is doing the initial interviews or creating the pool of candidates.
So, showing what you have done is contingent in passing this initial filter or bypassing it somehow.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781047</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781195</id>
	<title>Format your resume in raw LaTex</title>
	<author>Anonymous</author>
	<datestamp>1255788180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Anyone worth working for will be able to compose the document in their head.</p></htmltext>
<tokenext>Anyone worth working for will be able to compose the document in their head .</tokentext>
<sentencetext>Anyone worth working for will be able to compose the document in their head.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781915</id>
	<title>It's easy, but</title>
	<author>Anonymous</author>
	<datestamp>1255800060000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>You are forced to put the GNU notice in your resume and provide a blood sample in a test tube so they can sequence your ADN.</p></htmltext>
<tokenext>You are forced to put the GNU notice in your resume and provide a blood sample in a test tube so they can sequence your ADN .</tokentext>
<sentencetext>You are forced to put the GNU notice in your resume and provide a blood sample in a test tube so they can sequence your ADN.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29786061</id>
	<title>Re:as someone who does hiring...</title>
	<author>noidentity</author>
	<datestamp>1255896960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>...those rules coming from someone who doesn't capitalize anything, puts two sentences together with a comma, and pluralizes with an apostrophe.</htmltext>
<tokenext>...those rules coming from someone who does n't capitalize anything , puts two sentences together with a comma , and pluralizes with an apostrophe .</tokentext>
<sentencetext>...those rules coming from someone who doesn't capitalize anything, puts two sentences together with a comma, and pluralizes with an apostrophe.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781931</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781335</id>
	<title>Re:How to format? Is not it about CONTENT?</title>
	<author>khallow</author>
	<datestamp>1255789980000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>One's resume should be in XML, from which various other formats can be produced automatically (and consistently)...</p></div><p>It's an interesting gimmick, but not sure what purpose it'd have for anyone other than XML monkeys. The problem is that a resume is about presentation as much as it is about content.</p></div>
	</htmltext>
<tokenext>One 's resume should be in XML , from which various other formats can be produced automatically ( and consistently ) ...It 's an interesting gimmick , but not sure what purpose it 'd have for anyone other than XML monkeys .
The problem is that a resume is about presentation as much as it is about content .</tokentext>
<sentencetext>One's resume should be in XML, from which various other formats can be produced automatically (and consistently)...It's an interesting gimmick, but not sure what purpose it'd have for anyone other than XML monkeys.
The problem is that a resume is about presentation as much as it is about content.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781561</id>
	<title>Re:"Meetings"?</title>
	<author>Anonymous</author>
	<datestamp>1255793820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>Some FOSS projects (especially those sponsored by a company, like Red Hat's Archer project) have regular meetings via phone calls in order to discuss the status of the activities, decide about new features, etc.  As a positive side effect, it makes the developers interact more with each other and create a stronger connection between them.</htmltext>
<tokenext>Some FOSS projects ( especially those sponsored by a company , like Red Hat 's Archer project ) have regular meetings via phone calls in order to discuss the status of the activities , decide about new features , etc .
As a positive side effect , it makes the developers interact more with each other and create a stronger connection between them .</tokentext>
<sentencetext>Some FOSS projects (especially those sponsored by a company, like Red Hat's Archer project) have regular meetings via phone calls in order to discuss the status of the activities, decide about new features, etc.
As a positive side effect, it makes the developers interact more with each other and create a stronger connection between them.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29791413
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781335
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781561
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781837
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781047
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29786061
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781931
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783265
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781125
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781047
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29785979
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781397
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781127
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781785
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782661
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781125
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783381
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29784443
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783879
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781711
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29787053
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783287
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781431
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781211
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781789
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781185
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782453
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_17_182238_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781453
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783771
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29787053
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782425
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783081
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781711
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783879
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781397
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29785979
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781931
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29786061
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781915
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781055
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781065
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781785
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781127
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781431
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783287
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781125
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782661
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783265
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781183
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781335
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29791413
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29784443
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29782453
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781453
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781047
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781081
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781837
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781063
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781561
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781211
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29783381
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_17_182238.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781185
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_17_182238.29781789
</commentlist>
</conversation>
