Explicitly facilitate being in the most efficient environment to produce and continuously improve code.
Specific environments (to cycle through)
Clarifying the problem to solve
- what is organization decision will have the biggest impact of the code maintanability and extensibility?
- do I understand the good practice of the language? environment? paradigm?
- periodically compare own produced code to
- beginners, intermediate, veterans
- construct the most likely hypothesis
- check available log to confirm it
- if it is correct, modify the code to fix it
- if it is not, modify the hypothesis and cycle again
See also delta debugging.
- does the code smell?
- does code coverage shows that most of the code is rarely used thus should not be spent so much time on?
- reconsider ArchitectureDesign, now that the code has been used what has changed and consequently how should the code reflect that?
CodeRefactoring displays the RSS to periodically propose refactoring to keep the code clean, yet tools could help for code smell, code coverage and usage.
See also Programming#Refactoring
- how can I make sure that the code does what it should do?
- who will be the persons most interacting with the code?
- by usage? by maintenance? by integration? by extending it?
Clarify the steps required for an efficient workflow and what can support them.
- Programming for general links
- Testbed:. to facilitate tests
- wiki integration
- facilitating following a proposed paradigm by being integrated as the workflow
- e.g. ΦFP (and the recently read WithoutNotesJuly11#GraphsBrainsAndGremlin which seems pretty coherent with it)
- quality checking
- it might be better to do so earlier in the process, e.g. in the IDE like Vi
- on the last commit that is adding lines check against code repositories e.g. Programming#CodeReUse (or directly tools listed there) using language vocabulary (rather than words in texts) and a technique e.g. LDA to suggest similar code to study, ideally labeled as of good quality snippets
- even though it can be done via a hook, this might be problematic in the workflow, consequently this could be updating a document to review later on during a moment more adapted for learning
- automated deployment
post-commit and remote
post-receive hooks which
- rsync the right files to the right locations
- verify that the configuration calling file is ok else update them
- package a content-free self-explanatory structured and configured version
- eventually with a small httpd and an installer
- a nightly package might be more adapted though
- log the result, eventually create an RSS for problems
- maintain the other "distribution channels"
- e.g. PmWiki official list of recipes with for each the page and eventually its attachment
- thus probably requiring a curl post request
- generate screenshots
- (if not working on a library) change in the interface in any way have to generate screenshots and associated thumbnails as people do not judge the result by internal changes or how the code repository is going but by how it looks
- cf TheArtOfLeanSoftwareDevelopment#Chapter2
Methods and techniques
Notes on content
- check Wikipedia:Philippe Kahn#Philippe.27s_3_Rules_of_Software_Craftsmanship
- read Sylvain Ross' Software production heuristics
- consider Vim (or other tools) integration to be part of the workflow
- periodically step back
- e.g. read http://www.antoarts.com/10-ways-to-improve-your-programming-skills/
- reorganize resources on this wiki, in particular Programming
- add LeechBlock sites list URL