Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/694305e8-d7f8-800e-a8d8-fbf410be6545
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: そう、それがまさに現場の実態だね。 === そう、それがまさに現場の実態だね。 簡単に言うと: ==== | | | | ==== | --- | --- | --- | | | | | | | | | ===== 1. 書く人は展開前を理解できる - COPYも読める - 継続行や桁依存も把握している ===== # レビューだけの人は展開後を見る - ツールで差分をチェックする - 文法は通るが意味は理解しないこともある - 誰でもできる作業 ===== - 見る人全員が展開前を理解するのは効率悪い ===== * 外注・新人・QAは展開後だけでチェックしたほうが早い * 経験者が理解して修正する → 安全 ===== - 勘定系バッチ開発 ===== * 親ソース+COPYで書く * 実装者が展開前でレビュー * 部門QAや外注が展開後でレビュー : ===== : ===== これで、「書くのは展開前だけどレビューは展開後」という矛盾感が解消される。 希望なら次に、自由形式を入れたときにこの二重構造がどう壊れたかを具体例付きで整理できる。 やる?
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)