Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added some more words #11

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Added some more words #11

wants to merge 4 commits into from

Conversation

voltrue2
Copy link

No description provided.

@@ -90,9 +90,12 @@ English | Japanese | Kana | Notes
--------|----------|------|------
Development | 開発 | かいはつ |
Developer | 開発者 | かいはつしゃ |
Engineer | PG (プログラマ) | ぷろぐらまー |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't the English for this be Programmer
Also wouldn't Engineer be a separate word エンジニア
(or at least it is what I have heard)

Copy link
Author

@voltrue2 voltrue2 Nov 24, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I simply chose Engineer there because some people prefer the word Engineer over Programmer.
It seemed that more people prefer Engineer.

By the way, it seems that Japanese engineers are usually called programmers.

Anyways, I can separate them like so:

| Programmer | PG | プログラマー |
| Engineer | PG/エンジニア | エンジニア |

Let me know what you think of it.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK PR updated.

@@ -166,6 +169,7 @@ Front-end | フロントエンド | |
Management | 管理 | かんり | Of people, software, etc
Manager | 管理者 | かんりしゃ |
Infrastructure | インフラ | |
System administrator | インフラ |
Copy link
Collaborator

@AlmirKadric AlmirKadric Nov 24, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo?
Though this one I have heard a few different variations and not sure which is the most preferred:
システムアドミン (my preference atm)
システム管理者
サーバ管理者
サーバアドミン
サーバオペレータ

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my experience with Japanese companies, the term "インフラ" is used for both Infrastructure and Sysadmins.

I just thought that adding this might help others with the confusion of using the same word "インフラ".
Maybe add some comments to this?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh never heard that use before. I see why you structured it the way you did. let me double check with another source first before I get back to you on this one

Copy link
Collaborator

@AlmirKadric AlmirKadric Nov 25, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After checking this with a few sources, it seems that this is not incorrect, but not a super popular term currently. The currently trending term apparently is "シスアド". However the other truth is that "インフラ" was popular at one point making this a very much an issue of eras.

As such this word should be listed and at some point we should list the alternatives with possible notes as to which era they belong to (e.g. as of 2015). Though that is not required for this PR.

LGMT 👍

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome

@@ -180,4 +184,5 @@ Your company | 御社 | おんしゃ |
Office | 事務所 | じむしょ |
In-house | 社内 | しゃない |
External / 3rd party | 外部 | がいぶ |
Contractor | 外注先 | がいちゅうさき |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

外注先 is more in the context of a company you contract
however if we're talking about an individual (公人的に) the more correct term would be I think 契約社員. Also if we're talking about an individual who is coming to your office from a contracted company (外注先) then the more correct term to describe that person would be 派遣.

Copy link
Author

@voltrue2 voltrue2 Nov 24, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"外注" is specifically used for contractors as in outsourced, so we cannot use "契約社員" or "派遣". This is usually used in B2B situation by the way.

Copy link
Collaborator

@AlmirKadric AlmirKadric Nov 25, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double checked this with a few sources LGTM 👍
勉強になりました、ありがとうございます
For clarification, in case anyone might read this, "契約社員" is similar to a full time employee in terms of benefits (insurances, pension etc), however their employment contract is conditional (time period etc). However "外注" is specifically someone you have contracted from the outside (outsourced) to do work for you, in other words they are not tied to any of the company benefits. (feel free to correct me if you think this explanation is still wrong)

@AlmirKadric
Copy link
Collaborator

LGTM 👍

Development department | 開発部 | かいはつぶ |
Research and development, R&D | 開発研究 | けんきゅうかいはつ
Implementation | 実装 | じっそう |
Not implemented | 未実装 | みじっそう |
Not implemented (Should have been implemebted) | 実装漏れ | じっそうもれ |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

implemebted -> implemented

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops... Updated.

@@ -90,9 +90,13 @@ English | Japanese | Kana | Notes
--------|----------|------|------
Development | 開発 | かいはつ |
Developer | 開発者 | かいはつしゃ |
Programmer | PG/エンジニア | エンジニア |
Engineer | PG | ぷろぐらまー |
Copy link
Collaborator

@ronkorving ronkorving Nov 29, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two words seem very debatable. Would love some extra feedback on this from either @AlmirKadric or @endow. At the same time I would argue against the differentiation in English between Developer/Programmer/Engineer (keep in mind also that engineer has a much broader meaning than "software engineer").

The translations here are also directly opposite to the English (programmer -> エンジニア and engineer -> ぷろぐらまー) which seems very confusing. Maybe it's correct, but then I wanna be extra rigorous in confirming this is really correct, and commonly used.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Engineer"("エンジニア") designs the system architecture of the program while "Programmer"("プログラマー") doesn't do that. "プログラマー" is just person who has programming language skill.
But sometimes blur the line between them in Japanese.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait it seems the japanese word for these 2 got mixed up. Read the original comment above (it was the first one). This should have been:

Anyways, I can separate them like so:

| Programmer | PG | プログラマー |
| Engineer | PG/エンジニア | エンジニア |

Let me know what you think of it.

@voltrue2 typo?

Copy link
Collaborator

@ronkorving ronkorving Nov 29, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On top of your comments, @AlmirKadric, I can add that after discussing with @endowt, "PG" is not a good fit for "Engineer". Because "Programmer" really has 2 Japanese words here, I would prefer 2 distinct entries for them, so the result being:

Programmer | PG | |
Programmer | プログラマー | |
Engineer | エンジニア | |

@ronkorving
Copy link
Collaborator

@voltrue2 Hi, is this still going places? :)

@voltrue2
Copy link
Author

voltrue2 commented Dec 19, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants