Search results

From CitconWiki
Jump to navigationJump to search
  • Discussed the simple ritual of daily journaling of unpleasant thoughts.
    218 bytes (27 words) - 02:25, 15 October 2022
  • ** simple things are simple * plugins in ruby are really simple
    3 KB (459 words) - 00:28, 1 November 2007
  • ...t using poking. Determine what the functional component does by passing in simple, valid, self-documenting values like 0, 1, "FirstName", "FlightNumber", or ...een extracting functional components by accident - now we can start making simple changes, like extracting parameters previously read from a web request, tha
    2 KB (256 words) - 04:01, 12 September 2015
  • ...that combines a number of my personal interests. Along with building good, simple software we also have misadventures in brewing, gardening and the hackery o
    575 bytes (91 words) - 16:40, 20 February 2014
  • * Try start with simple requirements, drift direction to somethoogin irrelevant is esay * Each story is perf test, simple goals, eg. every single response time must be under 1s
    2 KB (345 words) - 04:58, 6 November 2010
  • Systems are categorized by Interactions that are Simple vs Complex, and Tightly Coupled vs Loosely Coupled. ** Complexity -> Simple
    5 KB (658 words) - 02:00, 21 September 2014
  • * Good for simple configuration
    648 bytes (107 words) - 01:01, 25 May 2024
  • * Making things as simple as possible, but not simpler
    795 bytes (106 words) - 11:26, 18 August 2015
  • Requirements should include a definition of done - which may be simple or refer to manual or auotmated tests being required / defined /referred to
    1 KB (181 words) - 01:14, 27 June 2010
  • ** Manages simple insertion of test data with DBUnit on a test by test basis
    906 bytes (137 words) - 04:06, 6 July 2009
  • ...ot be broken down beyond a unit test. There is no obligation to release a simple open. How do you coach the philosophy change of simple stories?
    3 KB (512 words) - 10:59, 3 October 2015
  • * St. Pauli TDD is outside-in direction, first test case is simple, mocks are avoided, and subproblems are solved with stubs first, and then a 1. The implementation is simple:
    7 KB (1,037 words) - 02:12, 15 October 2023
  • build your architecture that simple to you, maybe could have legacy code but should be killed everytime if you� the cheaping: simple as possible, office shell software
    3 KB (457 words) - 11:32, 22 September 2014
  • ...s talk/presentation "Simple Made Easy": http://www.infoq.com/presentations/Simple-Made-Easy
    1 KB (214 words) - 18:16, 2 March 2014
  • # Simple colour picker dialog, that doesn't actually do anything when user selects a
    1 KB (180 words) - 14:21, 28 September 2025
  • Can be as simple as naming convention to a lot more complicated such as API keys, logging, e
    1 KB (189 words) - 09:22, 4 October 2015
  • * He demonstrated how hard it can be to read even the most simple interactions due to the amount of scaffolding required * The unit tests became so simple that they appeared to simply be duplicating production code
    4 KB (604 words) - 13:17, 22 August 2008
  • | a simple program, without much risk
    2 KB (301 words) - 13:55, 29 June 2008
  • * make a simple scenario free & charge for more complex scenarios
    1 KB (256 words) - 17:46, 4 February 2023
  • ...sure that there is always another solutions for it but we want to keep it simple with one uniform solution using nagios.
    2 KB (320 words) - 23:32, 3 October 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)