구글 엔지니어는 이렇게 일한다 - 타이터스 위터스 외 - 202206 › HelpOnXmlPages › WSDL문서의구조 › SEED › CategoryEmpty › writing

• (번역)PleaseStopCallingDatabasesCPOrAP . . . . 4 matches
       #keywords docs, translation, database, nosql, cap, writing
       [writing] >
       (Yes, I realize the irony of writing a blog post about the very topic that I am asking people to stop writing about.
• OurSoftwareDependencyProblem . . . . 4 matches
       My purpose in writing this article is to raise awareness of the risks and encourage more investigation of solutions.
       designing, writing, testing, debugging, and maintaining a specific unit of code.
       A package, for this discussion, is code you download from the internet. Adding a package as a dependency outsources the work of developing that code—designing, writing, testing, debugging, and maintaining—to someone else on the internet, someone you often don’t know. By using that code, you are exposing your own program to all the failures and flaws in the dependency. Your program’s execution now literally depends on code downloaded from this stranger on the internet. Presented this way, it sounds incredibly unsafe. Why would anyone do this?
       Dependency managers have scaled this open-source code reuse model down: now, developers can share code at the granularity of individual functions of tens of lines. This is a major technical accomplishment. There are myriad available packages, and writing code can involve such a large number of them, but the commercial, legal, and reputational support mechanisms for trusting the code have not carried over. We are trusting more code with less justification for doing so.
       Is package’s documentation clear? Does the API have a clear design? If the authors can explain the package’s API and its design well to you, the user, in the documentation, that increases the likelihood they have explained the implementation well to the computer, in the source code. Writing code for a clear, well-designed API is also easier, faster, and hopefully less error-prone. Have the authors documented what they expect from client code in order to make future upgrades compatible? (Examples include the C++5 and Go6 compatibility documents.)
• SystemRebuilding-201912 . . . . 2 matches
       #keywords writing
       [writing] >
• 아들아설악산케이블카에서할머니를만나면...-20180815 . . . . 2 matches
       #keywords writing
       [writing] >
• MD5SUM.java . . . . 1 match
        System.err.println("I/O Exception : while writing");
• PairingSamsungBluetoothKeyboardTrio500OnXubuntu . . . . 1 match
       But now that I'm writing this article using that keyboard, can you tell that I've succeeded?
• WikiNature . . . . 1 match
       Writing on Wiki is like regular writing, except I get to write so much more than I write, and I get to think thoughts I never thought (like being on a really good Free Software project, where you wake up the next morning to find your bugs fixed and ideas improved).
• writing . . . . 1 match
       #keywords writing
• 일단오늘한줄써봅시다-김민태 . . . . 1 match
       #keywords reading, writing,

You can also click here to search title.