-
Notifications
You must be signed in to change notification settings - Fork 43
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
base: master
Are you sure you want to change the base?
Conversation
@@ -90,9 +90,12 @@ English | Japanese | Kana | Notes | |||
--------|----------|------|------ | |||
Development | 開発 | かいはつ | | |||
Developer | 開発者 | かいはつしゃ | | |||
Engineer | PG (プログラマ) | ぷろぐらまー | |
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
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 | インフラ | |
There was a problem hiding this comment.
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)
システム管理者
サーバ管理者
サーバアドミン
サーバオペレータ
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 👍
There was a problem hiding this comment.
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 | 外注先 | がいちゅうさき | |
There was a problem hiding this comment.
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 派遣.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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)
LGTM 👍 |
Development department | 開発部 | かいはつぶ | | ||
Research and development, R&D | 開発研究 | けんきゅうかいはつ | ||
Implementation | 実装 | じっそう | | ||
Not implemented | 未実装 | みじっそう | | ||
Not implemented (Should have been implemebted) | 実装漏れ | じっそうもれ | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
implemebted -> implemented
There was a problem hiding this comment.
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 | ぷろぐらまー | |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 | エンジニア | |
@voltrue2 Hi, is this still going places? :) |
Hello
I thought you guys are still discussing on some issues with it. If there are changes need to be made to this PR, let me know ;) I'll be happy to make the changes.
…Sent from my iPhone
On Nov 29, 2016, at 17:14, Ron Korving ***@***.***> wrote:
@ronkorving commented on this pull request.
In ReadMe.md:
> @@ -90,9 +90,13 @@ English | Japanese | Kana | Notes
--------|----------|------|------
Development | $B3+H/(B | $B$+$$$O$D(B |
Developer | $B3+H/<T(B | $B$+$$$O$D$7$c(B |
+Programmer | PG/$B%(%s%8%K%"(B | $B%(%s%8%K%"(B |
+Engineer | PG | $B$W$m$0$i$^!<(B |
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 | $B%W%m%0%i%^!<(B | |
Engineer | $B%(%s%8%K%"(B | |
$B!=(B
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
No description provided.