Full text search for "ci"


Search BackLinks only
Display context of search results
Case-sensitive searching
  • OurSoftwareDependencyProblem . . . . 81 matches
         #keywords translation, dependencies
         developers reuse software written by others every day, in the form of software dependencies, and the situation goes mostly unexamined.
         My own background includes a decade of working with Google’s internal source code system, which treats software dependencies as a first-class concept,1 and also developing support for dependencies in the Go programming language.2
         Software dependencies carry with them serious risks that are too often overlooked.
         The shift to easy, fine-grained software reuse has happened so quickly that we do not yet understand the best practices for choosing and using dependencies effectively, or even for deciding when they are appropriate and when not.
         designing, writing, testing, debugging, and maintaining a specific unit of code.
         Taking on externally-written dependencies is an old practice:
         Before dependency managers, publishing an eight-line code library would have been unthinkable: too much overhead for too little benefit. But NPM has driven the overhead approximately to zero, with the result that nearly-trivial functionality can be packaged and reused. In late January 2019, the escape-string-regexp package is explicitly depended upon by almost a thousand other NPM packages, not to mention all the packages developers write for their own use and don’t share.
         Decades ago, most developers already trusted others to write software they depended on, such as operating systems and compilers. That software was bought from known sources, often with some kind of support agreement. There was still a potential for bugs or outright mischief,3 but at least we knew who we were dealing with and usually had commercial or legal recourses available.
         The phenomenon of open-source software, distributed at no cost over the internet, has displaced many of those earlier software purchases. When reuse was difficult, there were fewer projects publishing reusable code packages. Even though their licenses typically disclaimed, among other things, any “implied warranties of merchantability and fitness for a particular purpose,” the projects built up well-known reputations that often factored heavily into people’s decisions about which to use. The commercial and legal support for trusting our software sources was replaced by reputational support. Many common early packages still enjoy good reputations: consider BLAS (published 1979), Netlib (1987), libjpeg (1991), LAPACK (1992), HP STL (1994), and zlib (1995).
         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.
         No matter what the expected cost, experiences with larger dependencies suggest some approaches for estimating and reducing the risks of adding a software dependency. It is likely that better tooling is needed to help reduce the costs of these approaches, much as dependency managers have focused to date on reducing the costs of download and installation.
         A basic inspection can give you a sense of how likely you are to run into problems trying to use this code. If the inspection reveals likely minor problems, you can take steps to prepare for or maybe avoid them. If the inspection reveals major problems, it may be best not to use the package: maybe you’ll find a more suitable one, or maybe you need to develop one yourself. Remember that open-source packages are published by their authors in the hope that they will be useful but with no guarantee of usability or support. In the middle of a production outage, you’ll be the one debugging it. As the original GNU General Public License warned, “The entire risk as to the quality and performance of the program is with you. Should the program prove defective, you assume the cost of all necessary servicing, repair or correction.”4
         The rest of this section outlines some considerations when inspecting a package and deciding whether to depend on it.
         Is the code well-written? Read some of it. Does it look like the authors have been careful, conscientious, and consistent? Does it look like code you’d want to debug? You may need to.
         Keep an open mind to development practices you may not be familiar with. For example, the SQLite library ships as a single 200,000-line C source file and a single 11,000-line header, the “amalgamation.” The sheer size of these files should raise an initial red flag, but closer investigation would turn up the actual development source code, a traditional file tree with over a hundred C source files, tests, and support scripts. It turns out that the single-file distribution is built automatically from the original sources and is easier for end users, especially those without dependency managers. (The compiled code also runs faster, because the compiler can see more optimization opportunities.)
         Find the package’s issue tracker. Are there many open bug reports? How long have they been open? Are there many fixed bugs? Have any bugs been fixed recently? If you see lots of open issues about what look like real bugs, especially if they have been open for a long time, that’s not a good sign. On the other hand, if the closed issues show that bugs are rarely found and promptly fixed, that’s great.
         Will you be processing untrusted inputs with the package? If so, does it seem to be robust against malicious inputs? Does it have a history of security problems listed in the National Vulnerability Database (NVD)?11
         For example, when Jeff Dean and I started work on Google Code Search12—grep over public source code—in 2006, the popular PCRE regular expression library seemed like an obvious choice. In an early discussion with Google’s security team, however, we learned that PCRE had a history of problems like buffer overflows, especially in its parser. We could have learned the same by searching for PCRE in the NVD. That discovery didn’t immediately cause us to abandon PCRE, but it did make us think more carefully about testing and isolation.
         Is the code properly licensed? Does it have a license at all? Is the license acceptable for your project or company? A surprising fraction of projects on GitHub have no clear license. Your project or company may impose further restrictions on the allowed licenses of dependencies. For example, Google disallows the use of code licensed under AGPL-like licenses (too onerous) as well as WTFPL-like licenses (too vague).13
  • CleanArchitecture-2020 . . . . 47 matches
         Structured programming imposes discipline on direct transfer of control.
         OOP imposes discipline on indirect transfer of control.
         Functional programming imposes discipline upon assignment.
         2) We use functional programming to impose descipline on the location of and access to data.
          * Science to the Rescue
         At every level, from the smallest function to the largest component, software is like a science and, therefore, si diven by falsifiability.
         To do so, they employ restrictive disciplines similar to structured programming, albeit at a much higher level.
         In a calling tree, source code dependencies followed the flow of control.
         It allows the architect to create a plugin architecture, in which modules that contain high-level policies are independent of modules that contain low-level details.
         This kind of segregation is supported by the use of appropriate disciplines to protect those mutated variables.
          * Event Sourcing
         = PART 3. Design Principles =
          * SRP: The Single Responsibililty Principle
          * OCP: The Open-Closed Principle
          * LSP: The Liskov Substitution Principle
          * ISP: The Inteface Segregation Principle
          * DIP: The Dependency Inversion Principle
         == Ch7. SRP: The Single Responsibility Principle ==
          * Symptom 1: Accidental Duplication
         At the level of components, it becomes the Common Closure Principle.
  • JavaListSystem.properties() . . . . 16 matches
         java.vm.specification.name=Java Virtual Machine Specification
         java.vm.specification.vendor=Sun Microsystems Inc.
         java.specification.name=Java Platform API Specification
         java.specification.version=1.6
         java.vm.specification.version=1.0
         java.specification.vendor=Sun Microsystems Inc.
         java.vm.specification.name=Java Virtual Machine Specification
         java.vm.specification.vendor=Sun Microsystems Inc.
         java.specification.name=Java Platform API Specification
         java.specification.version=1.4
         java.vm.specification.version=1.0
         java.specification.vendor=Sun Microsystems Inc.
  • AwsGlacier . . . . 12 matches
         #keywords aws, clacier
         $ aws glacier initiate-job --account-id - --vault-name photos --job-parameters '{"Type": "inventory-retrieval"}' --region ap-northeast-1
         $ aws glacier list-jobs --account-id - --vault-name photos --region ap-northeast-1
          "VaultARN": "arn:aws:glacier:ap-northeast-1:8888:vaults/photos",
         $ aws glacier describe-job --region ap-northeast-1 --account-id - --vault-name photos --job-id "d-DvEvVqAJmrvcqlgx5UbyFlo6RV6LQiCHQH-g91PRIpHy2DCUQc7OtsyvfuU3lpl6SMqkwx4cRIl91KQL2WWzNL79GH"
          "VaultARN": "arn:aws:glacier:ap-northeast-1:8888:vaults/photos",
         $ aws glacier describe-job --account-id - --vault-name photos --job-id nadKuO4U3YzkqONz-elqIHJfuqdcNiUJG0pdHPFCgbFGGJGJ0Y4C4UOt_DIzoziJHSF627OHluLjY7n_gEZqRXcy_aLB
          "VaultARN": "arn:aws:glacier:ap-northeast-1:8888:vaults/photos",
         aws glacier get-job-output --account-id - --vault-name photos --job-id nadKuO4U3YzkqONz-elqIHJfuqdcNiUJG0pdHPFCgbFGGJGJ0Y4C4UOt_DIzoziJHSF627OHluLjY7n_gEZqRXcy_aLB out.json
         aws glacier delete-archive --account-id - --vault-name photos --archive-id IubxeMR4pYpP6I7KfLejxEpYLKXK8RDnCQgyezviFE7d0anX01aiLybs9ZJyNxBDiS7lBoT0Hlbh0NZhkieehivfee8PUSV9UzD197sTQVFhpB6TWMqaHILLKZ7msJR4qmRFKxHQoA
         $ aws glacier describe-vault --account-id - --vault-name photos
          "VaultARN": "arn:aws:glacier:ap-northeast-1:8888:vaults/photos",
  • (번역)PleaseStopCallingDatabasesCPOrAP . . . . 9 matches
         Instead, we should use more precise terminology to reason about our trade-offs.
         If you want to refer to CAP as a theorem (as opposed to a vague hand-wavy concept in your database’s marketing materials), you have to be precise.
         Mathematics requires precision.
          * Consistency in CAP actually means linearizability, which is a very specific (and very strong) notion of consistency.
          In particular it has got nothing to do with the C in ACID, even though that C also stands for “consistency”.
          특히 ACID에서 C와는 전혀 관련이 없습니다.
          It’s not sufficient for some node to be able to handle the request: any non-failing node needs to be able to handle it.
         Also note that the CAP theorem doesn’t just describe any old system, but a very specific model of a system:
         If your use of words matches the precise definitions of the proof, then the CAP theorem applies to you.
         Just after the final score is announced, Alice refreshes the page, sees the winner announced, and excitedly tells Bob about it.
         This is a fairly expensive guarantee to provide, because it requires a lot of coordination. Even the CPU in your computer doesn’t provide linearizable access to your local RAM! On modern CPUs, you need to use an explicit memory barrier instruction in order to get linearizability. And even testing whether a system provides linearizability is tricky.
  • FortuneCookies . . . . 9 matches
          * "Heck, I'm having a hard time imagining the DOM as civilized!" -- Fred L. Drake, Jr.
          * You will overcome the attacks of jealous associates.
          * It's not reality that's important, but how you percieve things.
          * Today is a good day to bribe a high ranking public official.
          * To criticize the incompetent is easy; it is more difficult to criticize the competent.
          * You have a deep appreciation of the arts and music.
          * Don't be overly suspicious where it's not warranted.
          * Your temporary financial embarassment will be relieved in a surprising manner.
  • Decision Tree Regressor Model Sample . . . . 6 matches
         from https://www.kaggle.com/code/gimslabgimslab/exercise-underfitting-and-overfitting/
         from sklearn.tree import DecisionTreeRegressor
         # Specify Model
         iowa_model = DecisionTreeRegressor(random_state=1)
          model = DecisionTreeRegressor(max_leaf_nodes=max_leaf_nodes, random_state=0)
         final_model = DecisionTreeRegressor(max_leaf_nodes=best_tree_size, random_state=1)
  • WikiSlide . . . . 6 matches
         == Principles ==
         To add special formatting to text, just enclose it within markup. There are special notations which are automatically recognized as internal or external links or as embedded pictures.
         Basic principle: ''Anybody logged in can edit anything.''
         == Exercises ==
         For the exercises we use your own Wiki-homepage which is usually based on a WikiName `FirstnameLastname`:
  • SOLID . . . . 5 matches
         = Single Responsibility Principle =
         = Open/Closed Principle =
         = Liskov Substitution Principle =
         = Interface Segregation Principle =
         = Dependency Inversion Principle =
  • Spring3.0특징요약 . . . . 5 matches
         Scope/Context-specific...
          Referencing bean properties
          Referencing system properties
          public class KiteEatingTree implements DeciduousTree {
          Embracing Java 5 (generics, autoboxing, annotations, etc).
  • Web2.0을활용한사이트 . . . . 5 matches
          * Socialtext
          * Socialtext
          * Del.icio.us
          * Socialmarks
          * Performancing Metrics
  • ProcMailSample1 . . . . 4 matches
         * ^To:.*undisclosed-recipients:;
         * ^Subject:.*[Ss]ummer.*[Ss]pecials
         * ^Subject:.*A (new|funny|nice|humor|excite|good|powerful|WinXP|(IE 6.0)) (game|tool|website|patch)$
         # CIH 바이러스
         * ^Subject: Check ur friends Circle$
         * ^Subject: excite$
  • awk . . . . 4 matches
          format specification, the results are
          unspecified.
          floating-point format specification, the
          results are unspecified.
  • css . . . . 4 matches
         a, abbr, acronym, address, big, cite, code,
         /* tables still need 'cellspacing="0"' in the markup */
          border-spacing: 0;
         letter-spacing:5pt
  • html5_book_원철연 . . . . 4 matches
          5.6 var, cite 요소(Element) http://fromyou.tistory.com/435
         == 7. 텍스트(Text), 7.1 대소문자로 변형(Transforming)하기, 7.2 문장 내 간격(Spacing) 처리하기 http://fromyou.tistory.com/515 ==
         7.5 문장 내 간격(Spacing) 처리하기 http://fromyou.tistory.com/518
         == 5. 호(arc), 원(circle) 그리고 곡선 그리기 http://fromyou.tistory.com/561 ==
  • jEdit . . . . 4 matches
         options.pmd.rules.SuspiciousHashcodeMethodName=true
         options.pmd.rules.EmptyStaticInitializer=true
         encoding.opt-out.x-ISCII91=true
         encoding.opt-out.US-ASCII=true
         xml.cache.public-id.14=-//NetBeans//DTD Module Automatic Dependencies 1.0//EN
         encoding.opt-out.x-MacIceland=true
         options.pmd.rules.ExplicitCallToFinalize=true
         options.pmd.rules.SuspiciousOctalEscapeRule=true
         options.pmd.rules.NonStaticInitializer=true
  • jcifs . . . . 4 matches
         * jcifs를 이용해 Windows 파일공유서버에서 파일 읽어와 콘솔에 뿌리기 예제
         import jcifs.smb.NtlmPasswordAuthentication;
         import jcifs.smb.SmbFile;
         import jcifs.smb.SmbFileInputStream;
         public class JCIFS_Test {
  • EclipseJavaCodeStyleFormatter . . . . 3 matches
         <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_explicit_constructor_call" value="16"/>
         <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_explicitconstructorcall_arguments" value="insert"/>
         <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_explicitconstructorcall_arguments" value="do not insert"/>
  • HelpOnTables . . . . 3 matches
         In addition to these, you can add some of the traditional, more long-winded HTML attributes (note that only certain HTML attributes are allowed). By specifying attributes this way, it is also possible to set properties of the table rows and of the table itself, especially you can set the table width using {{{||<tablewidth="100%">...||}}} in the very first row of your table, and the color of a full row by {{{||<rowbgcolor="#FFFFE0">...||}}} in the first cell of a row. As you can see, you have to prefix the name of the HTML attribute with {{{table}}} or {{{row}}}.
         more cleaner representation is following: "space" character has special meaning.
  • JavaMailSendExam . . . . 3 matches
         message.setRecipient(Message.RecipientType.TO, new InternetAddress(toAddr, toName, "EUC-KR"));
         transport.sendMessage(message, message.getAllRecipients());
  • OsxKeychain . . . . 3 matches
         # -s specify service
         # -a specify account
         # -w specify password
  • SmbMountOnUbuntu . . . . 3 matches
         #keywords smb, samba, cifs, mount, smbclient
         $ sudo mount -t cifs //rtac68p/pds /mnt/rtac68p -o user=ftp
         sudo mount -t cifs //YOUR_SERVER_NAME/SHARE_NAME /mnt/smb -o user=USERNAME,password=PASSWORD,workgroup=WORKGROUP_NAME,ip=1.2.3.4,iocharset=utf8
  • Useful Software . . . . 3 matches
          * Audacity : 오픈소스, 크로스 플랫폼 sound editor
          * MagicDisc : virtual cd/dvd-rom, make cd/dvd image http://www.magiciso.com/tutorials/miso-magicdisc-overview.htm
          * TClockEx : 윈도우트레이에 날짜 표시 등 달력관련 유틸 http://www.rcis.co.za/dale/tclockex/
  • Web2.0이란 . . . . 3 matches
         물론 상대적인 개념이겠지만 기존의 웹들에 비해 웹2.0 사이트라 불리는 것들의 특징은 확실히 사용자들의 적극적인 참여를 필요로한다. 브리태니커 백과사전에 맞먹는 방대한 데이터를 자랑하는 WikiPedia는 누군가 고용되어 작성한 내용이 아니다. 위키라는 기술을 이용하여 전세계의 컨텐츠 이용자가 곧 컨텐츠 작성자가 되어 구축되어진 사이트이다. 또한 del.icio.us 라는 사이트에서는 수많은 사용자들이 자신의 인터넷 즐겨찾기를 저장시켜놓고 또한 다른 사용자들과 공유한다. 그리고 다른 사용자들의 즐겨찾기를 검색한다.
         집단지성을 활용하는 웹2.0의 특징을 얘기할때면 폭소노미(Folksonomy)라는 말이 나온다. 사람들에 의한 분류법이라고 간단히 말할 수 있는 이 개념의 대표적인 예가 바로 태깅이라고 할 수 있다. 앞에서 말한 del.icio.us 도 물론 이러한 기능이 있으며 사진공유 사이트로 유명한 플릭커(Flickr)도 바로 이 태깅을 지원한다. 기존의 일반적인 자료 분류방법(taxonomy)이 디렉토리라면 웹2.0은 태그를 사용한다. 물론 사용자의 참여가 필요하고 그들의 집단 지성이 필요하다. 디렉토리를 이용한 분류방법은 컨텐츠 관리자가 디렉토리를 정의하고 사용자들이 그 구조에 맞게 컨텐츠를 추가하는 형식인다. 하지만 태그를 이용하는 방식은 좀 다르다. 일단 컨텐츠가 작성되고 그 컨텐츠에 관심이 있는 사용자들이 그 컨텐츠에 태그를 붙인다. 물론 붙이는 사람들의 성향에 따라 다른 태그가 붙을 수 있다. 이러한 방법으로 많은 사용자들에 의해 완만하게 데이터를 분류해나가는 방법이다. 기존의 일반적인 웹메일에서 폴더 방식의 메일 저장구조를 가지는 반면 웹2.0의 대표 서비스인 gmail은 바로 이 태그기능(라벨)을 이용하여 메일을 분류할 수 있는 기능을 제공한다.
         기존의 몇개월주기 몇년주기의 일반적인 s/w 릴리즈 형태와는 다르게 웹2.0에 속하는 서비스들은 매일매일 데이터와 프로그램이 업데이트되고 업그레이드된다. 이러한 이유로 펄, 파이썬, php, 루비 등의 스크립트 언어들이 중요한 역할을 수행하여 쉽고 빠른 업그레이를 돕게 된다. web2.0에서의 사용자는 개발자그룹에 포함시켜 취급되어 진다. 즉 사용자들의 답변과 행동의 모니터링 등을 통해 새로운 기능과 서비스를 항상 반영하고 있다. Gmail, 구글 맵스, 플리커(Flickr), 딜리셔스(del.icio.us) 같은 서비스들이 수년째 "베타" 로고를 가지고 운영되고 있다.
  • XubuntuNewInstall . . . . 3 matches
          1. fcitx, fcitx-hangul, fcitx-config(add Input Method -> Hangul, uncheck "only show current language") (or ibus)
  • docs . . . . 3 matches
         http://www.rgoarchitects.com/Files/fallacies.pdf | I heard about the 8 fallacies of distributed computing few years ago - fallacies.pdf
  • rcs . . . . 3 matches
         ci myfile
         ci -l myfile
          ci
  • totalcommander-wincmd.ini . . . . 3 matches
         IconsSpecialFolders=3
         SpecialView=0
         SpecialView=0
  • BuildingMicroservices;마이크로서비스아키텍처구축-샘뉴먼지음,정성권옮김 . . . . 2 matches
          * 원칙(principle) : 목표를 위해 해야할 일을 정렬하는 규칙, 변경될수 있다.(ex: 신제품 출시기간 단축이라는 전략목표를 위해 SW수명주기 전반에 대한 통제권을 가지고, 제품준비완료시마다 타팀과 독록적으로 출시하는 원칙을 정하기)
          - Circuit Breaker
          - 격벽(bulkhead) : Circuit Breaker는 격벽 자동 차단기, Netflix의 Hystrix
          * CQRS(Command-Query Responsibility Segregation) Pattern, Event Sourcing
  • CopyingOffsetsOfAConsumerGroupToAnotherConsumerGroupInKafka0.10WithPythonScript . . . . 2 matches
         Consumer group `grp1` is rebalancing.
          * STOP above script(poll-without-commit.py) with Ctrl+C and WAIT for grp2 to go into REBALANCING state.
         Consumer group `grp2` is rebalancing.
  • CssStyle . . . . 2 matches
         = 적용순위 (specificity) =
  • CutFixedLengthData . . . . 2 matches
         partnerName varchar(100) utf8_general_ci NO MUL (NULL) select 거래처명
         bizNum varchar(12) utf8_general_ci NO (NULL) select 사업자번호
  • HelpOnLinking . . . . 2 matches
         If you enclose a sequence of characters in square brackets and double quotes {{{["like this"]}}}, that makes it a page name. That can be used for specific uses of MoinMoin (like organizing a list of items, e.g. your CD collection, by their "natural" name), or if you want to create a wiki with a non-western character encoding.
         In addition to the standard schemas, there are MoinMoin-specific ones: `wiki:`, `attachment:`. "`wiki:`" indicates an InterWiki link, so `MoniWiki:FrontPage` and `wiki:MoniWiki:FrontPage` are equivalent; you will normally prefer the shorter form, the "`wiki`" scheme becomes important when you use bracketed links, since there you always need a scheme. The other three schemes are related to file attachments and are explained on HelpOnActions/AttachFile.
  • HelpOnNavigation . . . . 2 matches
          * [[Icon(info)]] shows meta information about the page, especially the full version history
         Clicking on the Page Title link located in the header above will show every page that references this page. A sample use of this back-referencing, inverted-links feature is the categorization of pages, i.e. CategoryHomepage.
  • InterMap . . . . 2 matches
         Delicious http://del.icio.us/tag/
  • MoniWikiPo . . . . 2 matches
         msgid "Use more specific text"
         msgid "QucikLinks are updated."
  • PatternTemplate . . . . 2 matches
         The forces influencing the problem and solution. This can be represented as a list.
         '''References:''' References cited in the pattern.
  • SAGA Pattern . . . . 2 matches
         분산 환경에서의 트랜잭션을 구현하는 방법으로 SAGA Pattern이라는 것이 있다. SAGA pattern이란 마이크로서비스들끼리 이벤트를 주고받아 특정 마이크로서비스에서의 작업이 실패하면 이전까지 작업이 완료된 마이크로서비스들에게 보상 (complementary) 이벤를 소싱함으로써 분산 환경에서 atomicity를 보장하는 패턴이다. SATA pattern에서의 핵심은 마이크로서비스들끼리 이벤트를 주고 받는다는 것이기 때문에, 이 패턴은 기본적으로 event sourcing 패턴 위에 적용되는 패턴이다.
  • UML에대한이해 . . . . 2 matches
          * 명세화(specifying)
          * Association : 구조적 관계로써 Link의 집합을 나타냄
  • WebWork . . . . 2 matches
         WebWork is a Java web-application development framework. It is built specifically with developer productivity and code simplicity in mind, providing robust support for building reusable UI templates, such as form controls, UI themes, internationalization, dynamic form parameter mapping to JavaBeans, robust client and server side validation, and much more.
  • cifs . . . . 2 matches
         [jcifs]
         apt-get install cifs-utils
  • classloader.jsp . . . . 2 matches
          String uriStr = uri.getSchemeSpecificPart();
          String uriStr = uri.getSchemeSpecificPart();
  • eclipse-keys . . . . 2 matches
         "Source","Mock Dependencies in Test Case...","Shift+Ctrl+Alt+M","Editing Java Source"
         "Source","Mock Dependencies in Test Case...","Ctrl+Alt+Shift+M","Editing Java Source"
  • fcitx . . . . 2 matches
         #keywords fcitx, Ctrl+Alt+H, Spell Hint, shortcuts, ubuntu, xubuntu
         fcitx-config-gtk3
  • samba . . . . 2 matches
         [cifs]
         [jcifs] - java에서 삼바 서버 접근하기
  • ASR . . . . 1 match
          * PALM (Pedigreed Attribute eLicitationMethod)
  • AppleMagicTrackpad2ForUbuntu20.04.1 . . . . 1 match
          Device Accel Velocity Scaling (299): 12.500000
  • BusinessRuleEngine . . . . 1 match
         [Some Guidelines For Deciding Whether To Use A Rules Engine]
  • CI . . . . 1 match
         = CI, [CITP] 개념도 =
         = CI의 이점 =
         2008년 JOLT 상을 수상한 책인 Continuous Integration: Improving Software Quality and Reducing Risk 에서...
         = 성공적인 CI 수행의 요건 =
         = [CI 도구] =
  • CSSTools . . . . 1 match
          * Style Master - http://www.westciv.com
  • CapslockKeyToVimLikeHJKLArrowKeyAndESCKey . . . . 1 match
          key <TLDE> { [ grave, asciitilde ] };
  • Css관련사이트 . . . . 1 match
         [^http://thenoodleincident.com/tutorials/box_lesson/boxes.html]
  • EclipseGradlePlugin . . . . 1 match
          * specify java home into ~/.gradle/gradle.properties
  • FirefoxTips . . . . 1 match
         http://www.google.co.kr/search?ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:ko:official&client=firefox&q=
  • HelpOnEditing . . . . 1 match
         The following pages describe the elements (wiki markup) you can use to get special formatting effects:
  • HelpOnMacros . . . . 1 match
         Macros allow the insertion of system features into normal wiki pages; the only thing that makes those pages special is that they contain macros. If you edit pages like RecentChanges or SystemInfo, you'll see what that means.
  • HelpOnPageCreation . . . . 1 match
         Note that saving template or form definition pages and using preview does ''not'' expand variables. Other than that, variable expansion is very global and happens anywhere on the page, including code displays, comments, processing instructions and other "special" areas of a page you might think are excluded.
  • HelpOnProcessingInstructions . . . . 1 match
          * {{{#FORMAT}}} ''format-specifier'': defines the input format for this page, known formats are:
  • HelpOnProcessors . . . . 1 match
         Processors work on the data in a code display. You specify which processor to call by using a ''bang path''-like construct in the first line. A bang path is a concept known from Unix command line scripts, where they serve the exact same purpose: the first line tells the shell what program to start to process the remaining lines of the script.
  • HelpOnSubPages . . . . 1 match
         Thus, by using "/" to concatenate several WikiName''''''s, you can create arbitrarily deep hierarchies (within limits, especially the length of filenames on your system). In reality, subpages are normal pages that contain a "/" in their name, and thus they are stored besides all other pages in the file system.
  • HelpOnUserPreferences . . . . 1 match
          * '''[[GetText(Preferred language)]]''': The default is taken from your browser setting. It is advisable to set this to a specific language anyway, since then you get notification mails in your native tongue, too.
  • HelpOnXmlPages . . . . 1 match
         If you have Python4Suite installed in your system, it is possible to save XML documents as pages. It's important to start those pages with an XML declaration "{{{<?xml ...>}}}" in the very first line. Also, you have to specify the stylesheet that is to be used to process the XML document to HTML. This is done using a [http://www.w3.org/TR/xml-stylesheet/ standard "xml-stylesheet" processing instruction], with the name of a page containing the stylesheet as the "{{{href}}}" parameter.
  • Hudson . . . . 1 match
         [CI도구] >
         http://hudson-ci.org/
  • JDepend . . . . 1 match
         JDepend traverses Java class file directories and generates design quality metrics for each Java package. JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to manage package dependencies effectively.
  • JWSDP . . . . 1 match
         java.math : BigDecimal, BigInteger
  • JpaJodaTimeAutoConverter . . . . 1 match
         dependencies {
  • JpaTips . . . . 1 match
         When the repository package is different to @SpringBootApplication/@EnableAutoConfiguration, @EnableJpaRepositories is required to be defined explicitly.
  • LinuxH/w정보알아내기 . . . . 1 match
         PCI정보 : cat /proc/pci
  • MD5SUM.java . . . . 1 match
          System.err.println("no buffer size specified.");
  • ML Study . . . . 1 match
         ["Decision Tree Regressor Model Sample"]
  • Meaning of INVERSION from SOLID DIP . . . . 1 match
         from wikipeda: https://en.wikipedia.org/wiki/Dependency_inversion_principle
  • Module04.S/WArchitecture . . . . 1 match
          * Early Design Decisions
  • OurLastSummer . . . . 1 match
         Like we were dancing
  • ProcMail . . . . 1 match
         = 처방(recipes)의 형식 =
  • PulseSecureUIFor64bitLinux . . . . 1 match
         https://cis.technion.ac.il/en/central-services/communication/install-juniper-ubuntu/
  • Random Forests . . . . 1 match
         하나의 트리만 사용하는 Decision Tree Regressor의 경우 하나의 관점만 존재, 정밀성이 떨어진다.
  • SlippingThroughMyFingers . . . . 1 match
         Barely awake, I let precious time go by
  • Spring2.0특징요약 . . . . 1 match
         Problem-specific XML
  • SwaggerSettingOnSpringBootWithNewServletContext . . . . 1 match
         1. add dependencies
  • SystemRebuilding-201912 . . . . 1 match
         Kafka Consuming을 이벤트 처리의 시작점으로 하는 팀의 입장에서 고충과 노하우?도 따로 정리해보자. 아.. rebalancing..
  • TamarinProject . . . . 1 match
         The goal of the "Tamarin" project is to implement a high-performance, open source implementation of the [ECMAScript] 4th edition (ES4) language specification. The Tamarin virtual machine will be used by Mozilla within SpiderMonkey, the core JavaScript engine embedded in [Firefox]®, and other products based on Mozilla technology. The code will continue to be used by Adobe as part of the ActionScript™ Virtual Machine within Adobe® Flash® Player.
  • TheIdealWayToUseJUnit . . . . 1 match
          * Decide what methods will be in your class, then write them as stubs — for example,
  • TheWinnerTakesItAll . . . . 1 match
         The judges will decide
  • UML관계 . . . . 1 match
          * 연관(Association) : 깊은 의존성으로 항상 가지고 있다.(has a ~ 관계, Member Field, 속성), 실선, 실선과 꺽쇠괄호 등
  • WebBrowserPlugins . . . . 1 match
          Vimperator: is a Firefox browser extension with strong inspiration from the Vim text editor, with a mind towards faster and more efficient browsing.
  • Well-FormedXML . . . . 1 match
          *[XML] Specification 1.0의 기본 문법 준수 문서
  • WikiKeyword . . . . 1 match
          * http://search.wikicities.com/wiki/Help:Keyword
  • WikiMarkup . . . . 1 match
         The special characters or character sequences used in a WikiWikiWeb to indicate the desired formatting. Like duplicate single-quote for ''emphasis''.
  • WikiSandBox . . . . 1 match
         And here is another line of text. Incidentally, you might want to do one
  • XML . . . . 1 match
          *[Well-Formed XML] : XML Specification 1.0의 기본 문법 준수 문서
  • aws . . . . 1 match
         see also : [aws glacier] [aws s3]
  • chrome . . . . 1 match
         chrome.exe --explicitly-allowed-ports=6000,95
  • drools . . . . 1 match
         cf. [Some Guidelines For Deciding Whether To Use A Rules Engine]
  • fonera . . . . 1 match
          * If you need special configuration settings (like static IP's or PPPoE settings) please change these settings now.
  • http response code . . . . 1 match
         Response code decision tree : http://i.stack.imgur.com/whhD1.png
  • jni . . . . 1 match
          * Java2COM (commercial): is a bi-directional Java-COM bridging tool that enables Java applications to use COM objects and makes possible to expose Java objects as if they were COM objects. 유료
  • procmail . . . . 1 match
         = 처방(recipes)의 형식 =
  • reading . . . . 1 match
          * Mastering Jboss Drools 6 for Developers - Mauricio Salatino, Esteban Aliverti, Mariano Nicolas De Maio - 2017
  • saas . . . . 1 match
         Software as a service (SaaS) is a software application delivery model where a software vendor develops a web-native software application and hosts and operates (either independently or through a third-party) the application for use by its customers over the Internet. Customers do not pay for owning the software itself but rather for using it. They use it through an API accessible over the Web and often written using Web Services or REST. The term SaaS has become the industry preferred term, generally replacing the earlier terms Application Service Provider (ASP) and On-Demand.
  • 보안관련용어 . . . . 1 match
         컴퓨팅에서, 피싱은, 전자우편 또는 메신저를 사용해서 신뢰할 수 있는 사람 또는 기업이 보낸 메시지인 것처럼 가장함으로써, 비밀번호 및 신용카드 정보와 같이 기밀을 요하는 정보를 부정하게 얻으려는 social engineering의 한 종류이다. ‘피싱’이란 용어는 점점 더 복잡한 미끼들을 사용해서 사용자의 금융 정보와 패스워드를 ‘낚는’다는 데서 유래되었다.
  • 웹표준-기본다지기 . . . . 1 match
         blockquote, cite : 따온글
  • 일단오늘한줄써봅시다-김민태 . . . . 1 match
         ㅎㅎ markdown을 좀 더 알아보던 과정에서 AsciiDoc 이란 것과 이러한 lightweight markup 포맷들의 그 철학에대해 읽게되고 공감하게 되었다.
  • 집단지능 . . . . 1 match
         [^http://del.icio.us] - 웹페이지 즐겨찾기 공유
Found 103 matching pages out of 1798 total pages

You can also click here to search title.

Valid XHTML 1.0! Valid CSS! powered by MoniWiki
last modified 2010-03-18 21:31:54
Processing time 0.5643 sec