davetron5000-daves-resume 0.1.1 → 0.1.2
Sign up to get free protection for your applications and to get access to all the features.
- data/lib/README.rdoc +25 -2
- metadata +1 -1
data/lib/README.rdoc
CHANGED
@@ -4,22 +4,38 @@ This is a set of small tools that allow you to manage your resume as a "database
|
|
4
4
|
|
5
5
|
= Quick Start
|
6
6
|
|
7
|
+
gem sources -a http://gems.github.com
|
8
|
+
sudo gem install davetron5000-daves-resume
|
7
9
|
dr-scaffold -r my_resume_dir
|
8
10
|
dr-format -r my_resume_dir -f HTML
|
9
11
|
|
10
12
|
<tt>resume.html</tt> now contains the resume generated by the scaffold. To create you resume, you need to:
|
11
13
|
|
12
|
-
1. Modify <tt>resume.yaml</tt> with your information
|
14
|
+
1. Modify <tt>resume.yaml</tt> with your information (or create multiple for managing resumes of different focus)
|
13
15
|
2. Modify <tt>skills.yaml</tt> with your skillset (see below)
|
14
16
|
3. Duplicate <tt>experience_Initech.yaml</tt> for each job you've held; this contains all the positions you held at that job, plus other information
|
15
17
|
4. Duplicate <tt>education_Degree_Mill_U.yaml</tt> for each degree/education you wish to appear
|
16
18
|
5. Duplicate (or delete) <tt>samples_Name_of_this_work_sample.yaml</tt> with any work samples
|
17
19
|
|
18
20
|
You can generate in one of three formats:
|
21
|
+
|
19
22
|
<tt>RTF</tt>:: - Rich Text which can be read by Word
|
20
23
|
<tt>HTML</tt>:: - A basic HTML version
|
21
24
|
<tt>Markdown</tt>:: - a Markdown[http://www.daringfireball.com/projects/markdown] version
|
22
25
|
|
26
|
+
=Features
|
27
|
+
|
28
|
+
==Manage your resume in a format-agnostic database of YAML-based files
|
29
|
+
|
30
|
+
Your resume can be version-controlled and edited in the editor of your choice; no more dealing with Word and why the bullet-lists don't work. Your work experience and other CV-related data are realy data and deserve to be persisted in something more usable than a proprietary Microsoft format.
|
31
|
+
|
32
|
+
==Generate your resume as RTF, HTML, or Markdown
|
33
|
+
|
34
|
+
Of course, no one is gonna take a resume in YAML (though if they do, you should probably go work there). As such, you can generate a nice, clean RTF format readable by monster.com, dice.com and HR generalists the world over.
|
35
|
+
|
36
|
+
==Manage multiple resumes from the same set of employment/education history
|
37
|
+
|
38
|
+
Ever needed to tweak your resume for a particular job? The second you copy your Word doc and tweak it, you have a version control problem and you now have to fix typos in both documents. Here, you can create different headlines/summaries for different focusses and you can tag your "Key Achievements" in each position you've held to allow for conditional generation of multiple resumes. When you change common information, you change it once, the way you would with code.
|
23
39
|
|
24
40
|
= YAML format
|
25
41
|
|
@@ -31,18 +47,25 @@ Basically, the resume is:
|
|
31
47
|
|
32
48
|
Core:: (in <tt>resume.yaml</tt>) - This has stuff like your name, address, summary, etc. If you wish to have multiple resumes, you will duplicate this file naming it <tt>resume_NAME.yaml</tt> where _NAME_ is the "core name" you can specify on the command-linen to <tt>dr-format</tt>
|
33
49
|
Skill Set:: (in <tt>skills.yaml</tt>) - This is a database of your skills, with an experience level and a number of years experience. These determine the sort order in your resume output. Basically, skills with which you are an <tt>:expert</tt> are shown first, sorted by years of experience. This is followed by skills where you are <tt>:intermediate</tt>. <tt>:novice</tt> skills show up in their own category called "Some Experience With". This allows you to include skills you've used, but be clear where your strengths lie.
|
50
|
+
|
34
51
|
* The accepted levels currently are:
|
52
|
+
|
35
53
|
<tt>:novice</tt>:: skills show up in "Some Experience With"
|
36
54
|
<tt>:intermediate</tt>:: skills show up last in their category
|
37
55
|
<tt>:expert</tt>:: skills show up first in their category
|
56
|
+
|
38
57
|
* The categories are currently hard-coded (sorry) and any skill not in a category won't show up (this is on my todo list). The categories are:
|
58
|
+
|
39
59
|
<tt>:languages</tt>:: Programming languages, e.g.
|
40
60
|
<tt>:apis</tt>:: APIs, standards, etc.
|
41
61
|
<tt>:tools</tt>:: Specific technology tools
|
42
62
|
<tt>:databases</tt>:: Relational databases
|
43
63
|
<tt>:operating_systems</tt>:: Specific operating systems
|
64
|
+
|
44
65
|
Experience:: any file that starts with <tt>experience_</tt> and ends in <tt>.yaml</tt> will get picked up. Things will be sorted properly (in reverse chronological order) for you. A Job consists of one or more positions, and the formatter should be smart about handling jobs with only one position.
|
66
|
+
|
45
67
|
* Acheivements can be tagged and you can use these tags to control your output (see below)
|
68
|
+
|
46
69
|
Education:: works like Experience files starting with <tt>education_</tt> will get picked up and sorted reverse chronologically
|
47
70
|
Samples:: this is just a name and a link, and only shows up in the Markdown and HTML version (though you are free to modify the RTF version).
|
48
71
|
References:: this isn't used anywhere right now, but any file starting with <tt>reference_</tt> and ending with <tt>.yaml</tt> will get picked up.
|
@@ -75,7 +98,7 @@ There is a default filter available that might do what you need
|
|
75
98
|
The included filter works as follows:
|
76
99
|
|
77
100
|
1. Create a core for the job (e.g. <tt>techlead_resume.yaml</tt>)
|
78
|
-
|
101
|
+
2. Create a config file in your resume dir named <tt>config_techlead.yaml</tt> (e.g.) that looks like so:
|
79
102
|
--- !ruby/object:Resume::ResumeConfig
|
80
103
|
achievement_tags:
|
81
104
|
- :lead
|