Add a toolsUsed under work properties about resume-schema

[vote539]

+1

[ocram]

I would say it's too tech-specific, as you already suggested. Why not just include the tools in your "skills" section? That's what it is: skills.

[osg]

Arguably, writing is a skill. I use tools, such as, DocBook, HTML, Markdown, nanoc, GitHub, and more to write documentation.

In the same light, vim is not a skill, it's a tool.

[thomasdavis]

I think if you want to showcase which skills you used for different employers you could just mention them in your work summary and highlights e.g

• Used Node.js and Bootstrap to build a modern web app

Otherwise we will get quite a bit of duplicate between work skills and the main skills object

[DonDebonair]

As someone who's done a lot of job interviews from the interviewer side, I wonder if the tools someone uses are ever seriously looked at. When I'm interviewing someone for a Java position, I don't care if they used Java EE 7 or Spring, as long as they understand the principles behind Dependency Injection ;)
I don't want to dismiss the tools someone knows entirely, but I think those can easily be mentioned in the descriptions of the relevant work-entries.

edit: @thomasdavis seems to be a lot quicker than me this morning ;)

[olivif]

There doesn't seem to be much support for this currently. I propose we add the revisit tag and close for now.

[aloisdg]

I am against for the original reason. It is a bit too "tech specific". By the way, I used python 4 years ago. I dont think It is relevant to write it. Tools will rise in the project section: "I made a tools to create themes with nodejs, nunjucks, ava and babel. I also used some bash scripts to build it."

[olivif]

@aloisdg I agree, it seems very tech specific. I am not saying I don't want people to have it in their resumes if they want to, but I don't think we need a special field for it. As @thomasdavis mentions, this can easily be done in the work description section. Or the future projects section.

[aloisdg]

@olivif Yes! I agree to close it for now.

[stp-ip]

I'm with the reasoning here. Tell the story via projects and work sections instead of having tools as a non usable keyword list.