Perhaps you should try some spelling variations:
"coder functional implications to programmer" » "coder educational implications to programmer" (Expand search), "coder practical implications to programmer" (Expand search), "modern functional implications to programmer" (Expand search), "border functional implications to programmer" (Expand search), "order functional implications to programmer" (Expand search), "coder functional implications _ programmer" (Expand search), "coder functional implications of programmer" (Expand search), "coder functional implications in programmer" (Expand search), "coder functional implications to programmed" (Expand search), "coder functional implications to programmes" (Expand search), "coder functional implications the programmer" (Expand search)
"using coding python python programming" » "using codigo python python programming" (Expand search), "using codigos python python programming" (Expand search), "using using python python programming" (Expand search), "using coding pythons python programming" (Expand search), "using coding piton python programming" (Expand search), "using coding pitons python programming" (Expand search), "using coping python python programming" (Expand search), "using coating python python programming" (Expand search), "using cooking python python programming" (Expand search)

You may be able to get more results by adjusting your search query.

• Performing a fuzzy search may retrieve terms with similar spellings: (("coder functional implications to programmer") OR ("using coding python python programming"))~.
• The words AND, OR and NOT may confuse the search; try adding quotes: "((\"coder functional implications to programmer\") OR (\"using coding python python programming\"))*".
• Removing quotes may allow a broader search: (( coder functional implications to programmer ) OR ( using coding python python programming ))*.