Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!feeder1.xsusenet.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.018 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'subject:Python': 0.05; 'url:github': 0.09; 'cc:addr:python-list': 0.10; 'thu,': 0.15; 'between.': 0.16; 'code),': 0.16; 'fits': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'massively': 0.16; 'proceeding': 0.16; 'repo,': 0.16; 'subject:OOP': 0.16; 'wrote:': 0.16; 'cc:2**0': 0.21; 'cc:addr:python.org': 0.21; 'trying': 0.22; 'fairly': 0.22; "aren't": 0.22; 'am,': 0.23; 'code.': 0.23; '2015': 0.23; 'tables': 0.23; "i've": 0.24; 'header:In-Reply-To:1': 0.24; 'somewhere': 0.24; 'developers': 0.24; 'testing': 0.25; 'idea': 0.26; 'required.': 0.26; 'message-id:@mail.gmail.com': 0.28; 'actual': 0.29; "i'm": 0.29; '(which': 0.29; "i'd": 0.31; 'creating': 0.32; 'point': 0.33; 'another': 0.34; 'received:google.com': 0.34; "i'll": 0.34; 'done': 0.35; 'but': 0.36; 'project': 0.36; 'there': 0.36; 'basic': 0.36; 'notes': 0.36; 'quite': 0.37; 'should': 0.37; 'subject:: ': 0.37; 'starting': 0.38; 'manual': 0.38; 'skip:p 20': 0.38; 'files': 0.38; 'test': 0.39; 'build': 0.40; 'well.': 0.40; 'some': 0.40; 'times': 0.61; 'building,': 0.72; 'now:': 0.72; 'worth': 0.73; 'captures': 0.84; 'chrisa': 0.84; 'exceeding': 0.84; 'seldom': 0.84; 'subject:Classic': 0.84; 'to:none': 0.90 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=iTWM0Y5RbqrScSQs+tIqA4ijYPyfW1HY9exq75I73k8=; b=QSWEKTkUu8/ymlKZi9hOI8EPLSZlR8hd0TCc63lvJcPuwwDnMTNSfcYZBwGcC+T73N 1lPTRk2XcBjllCfJAF4uW1q6+++Vs6s5Pbxl1dzxGmEYfAiMsmt5HG7K57c3oixWSPlB 6Vdrwxg7At2ooGzctth83R4BfDhtZu3o98Ls9fLvT+YgvCtLBZ/m/CFq+WT1g9AuodXR ABaCJmYxjg9DYVeJs4VT5ddKllBAcaBQNGyXj9Yjy1k50nWD/zsSZfHy9q1HLwmmvDZc IjZxwzMBw/PLKTak3jDTaIUKjBlBEEB55cw9MUZWzcbqTHmU5v70dm+WDS6ZuKTFUt/D c/gg== MIME-Version: 1.0 X-Received: by 10.50.176.228 with SMTP id cl4mr14729972igc.2.1434586041989; Wed, 17 Jun 2015 17:07:21 -0700 (PDT) In-Reply-To: <87eglaqdca.fsf@elektro.pacujo.net> References: <23b2fae3-91d5-486b-9898-78b34bee486f@googlegroups.com> <16dc8c92-50e3-4fc8-ae25-cbc5b13e8971@googlegroups.com> <87eglaqdca.fsf@elektro.pacujo.net> Date: Thu, 18 Jun 2015 10:07:21 +1000 Subject: Re: Classic OOP in Python From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 24 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1434586050 news.xs4all.nl 2888 [2001:888:2000:d::a6]:34345 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:92794 On Thu, Jun 18, 2015 at 6:39 AM, Marko Rauhamaa wrote: > Another interesting ism I have read about is the idea that the starting > point of any software project should be the user manual. The developers > should then go and build the product that fits the manual. I've seldom met a *user* manual that's truly the right way to start building, but there have been times when I've built *API* documentation prior to the code. That can work fairly well. I'll also often start a project with a copious set of notes that aren't quite user-facing, aren't quite programmer-friendly, but are somewhere in between. Here's a new project I'm starting now: https://github.com/Rosuav/ThirdSquare Prior to actually creating that repo, I'd done some thrash testing of the basic concepts (which is how I know that the basic idea will work - my thrash test achieved 100tps, massively exceeding the 40tps that I need, ergo it's worth proceeding to code), but the project itself started with the README, then the .sql files giving a basic run-down of the tables required. Now, and only now, I'm starting to look at actual code. Is that starting with the user manual? Not quite, but I think it captures the same concept that that's trying to capture. ChrisA