Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/664#discussion_r30391850
--- Diff: docs/apis/best_practices.md ---
@@ -0,0 +1,155 @@
+---
+title: "Best Practices"
+---
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<a href="#top"></a>
+
+
+This page contains a collection of best practices for Flink programmers on
how to solve frequently encountered problems.
+
+
+* This will be replaced by the TOC
+{:toc}
+
+## Parsing command line arguments and passing them around in your Flink
application
+
+
+Almost all Flink applications, both batch and streaming rely on external
configuration parameters.
+For example for specifying input and output sources (like paths or
addresses), also system parameters (parallelism, runtime configuration) and
application specific parameters (often used within the user functions).
+
+Since version 0.9 we are providing a simple called `ParameterTool` to
provide at least some basic tooling for solving these problems.
+
+As you'll see Flink is very flexible when it comes to parsing input
parameters. You are free to choose any other framework, like [Commons
CLI](https://commons.apache.org/proper/commons-cli/),
[argparse4j](http://argparse4j.sourceforge.net/), or others.
--- End diff --
I think this paragraph is confusing. I would remove it
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
