Difference between revisions of "Software Development"

From The Thinkulum
Jump to navigation Jump to search
(Added subheadings to the introduction. Added a purpose section. Updated some language to match the current project state.)
(Added "Introduction to the Guide" to the topic outline.)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Introduction ==
== Introduction ==


=== Purpose ===
This is a collection of notes on software development. Its main purpose is to help me raise my development's level of professionalism. It also gives me a place to air an opinion or two.


This project is a growing set of notes on various aspects of software development. Its purpose is to define a set of standard operating procedures for my programming projects.
To give you an idea of my background, after some BASIC programming in my childhood and a break of many years for other interests, I returned to hobby programming just after undergrad and was able to make it my living several years later in 2006. That phase of my developer life started with Perl, and since then I've moved on to Python and XSLT. I've worked mainly in the area of text processing. JavaScript and PHP have played intermittent supporting roles for occasional web development or InDesign scripting. My projects have all been either solo or with a very small team. It's all been on Windows and mostly for the command line.


=== Background ===
== Topics ==


For most of my coding life, I have been the only user of my programs. I wrote them to aid my work or personal life, and only rarely did anyone else even see my code or watch it run. This wasn't on purpose. It just turned out that way. In my current job I do belong to a small development team, but our programs are still only for in-house use, so the only needs we have to consider are our own.
As a way to organize my notes and make sure I don't miss anything important, I'll use the structure of IEEE's ''Guide to the Software Engineering Body of Knowledge'' (SWEBOK). It's a standard that overviews the entire field and forms the basis for creating things like curricula and certifications. You can [https://www.computer.org/education/bodies-of-knowledge/software-engineering/v3 download the PDF] for free.


This situation is starting to change. My programming projects are becoming more relevant to the outside world, and I want to share some of them as open source. This means I'm needing to reshape some of my programming practices and learn some areas of software development I've had the luxury of ignoring all these years.
The items under the SWEBOK knowledge areas in the first level link to my notes on each topic. I've sorted the knowledge areas to approximate my preferred order, though I'll address them more haphazardly.


I haven't completely ignored these areas, though. I pick up on them here and there as I read about how other people code or as I see them in the software I use. Knowing that I'll probably need to know about them someday, I've kept a list. And now the time has come for me to fill in the details.
* '''Introduction to the Guide'''
 
* '''Ch. 12: Software engineering economics'''
I'm filling in the details here in this project for two reasons. First, as I learn, writing helps me clarify my thoughts and keep them flowing. And second, posting my writing might help other people. So if you're like me and you've programmed mainly for yourself--what I call private coding--and you're starting to share your work with others--public coding--then maybe what I've learned so far can grease some of your own planning.
* '''Ch. 11: Software engineering professional practice'''
 
** [[/License/]]
=== Method ===
* '''Ch. 14: Mathematical foundations'''
 
* '''Ch. 13: Computing foundations'''
This project consists of my reading other developers' advice, examining their code, deciding what to adopt and how to adapt it to my needs and preferences, and creating templates, procedures, reference materials, and anything else that might help me code well for a public user base.
* '''Ch. 15: Engineering foundations'''
 
* '''Ch. 9: Software engineering models and methods'''
=== Limitations ===
* '''Ch. 7: Software engineering management'''
 
* '''Ch. 10: Software quality'''
To give you an idea of my background, I've worked for the past 15 or so years in the publishing industry doing mostly text processing and some web development. The languages I'm most familiar with are Perl, Python, XSLT, and some JavaScript, with a smattering of PHP and VBA. I've spent almost all my time in Windows. I hope to branch out into at least Linux in the future, if only to expand my mind.
* '''Ch. 6: Software configuration management'''
 
** [[/Version Control/]]
This project will be oriented toward Python for now, but I imagine a lot of its suggestions apply to other languages too. At this point it also centers around desktop command-line programs, but I'm hoping to expand it into other interfaces and environments.
** [[/Version Numbers/]]
 
** [[/Distribution/]]
=== Feedback ===
* '''Ch. 8: Software engineering process'''
 
** [[/Software Development Methodology/]]
Since this project is a place for me to learn, I welcome feedback, and I'm always open to arguments that my choices could be improved or suggestions for things I've missed.
*** [[/Iterative and Incremental Development/]]
 
* '''Ch. 1: Software requirements'''
== Topics ==
** Requirements
 
* '''Ch. 4: Software testing'''
* [[/Software Development Methodology/]]
** [[/Testing/]]
** [[/Iterative and Incremental Development/]]
* '''Ch. 2: Software design'''
** Design
** Architecture
** UX and UI
* '''Ch. 3: Software construction'''
** [[/Code Style/]]
** [[/Project Structure/]]
** [[/Installation/]]
** [[/Metadata/]]
** [[/Command Line Interface/]]
** [[/Documentation/]]
*** [[/Comments/]]
*** [[/Literate Programming/]]
*** [[/Docstrings/]]
*** [[/Project Documentation/]]
*** [[/READMEs/]]
*** [[/Command Line Help/]]
** [[/Application Configuration/]]
** [[/Logging/]]
** [[/Test-First Programming/]]
** [[/Test-First Programming/]]
* '''Ch. 5: Software maintenance'''
** [[/Refactoring/]]
** [[/Refactoring/]]
* [[/Version Control/]]
* [[/Code Style/]]
* [[/Project Structure/]]
* [[/Distribution/]]
* [[/Installation/]]
* [[/Metadata/]]
** [[/Version Numbers/]]
** [[/License/]]
* [[/Testing/]]
* User Interface
** [[/Command Line Interface/]]
* [[/Documentation/]]
** [[/READMEs/]]
** [[/Docstrings/]]
** [[/Command Line Help/]]
** [[/Comments/]]
** [[/Project Documentation/]]
** [[/Literate Programming/]]
* [[/Application Configuration/]]
* [[/Logging/]]
== Code examples ==
To show how I'm implementing these ideas in my own code, I'll refer to [https://github.com/thinkulum my GitHub repositories] throughout the project, mainly my templates for [https://github.com/audreyr/cookiecutter cookiecutter], a Python app that creates project skeletons for any language, and my snippets for [https://www.sublimetext.com/ Sublime Text 2], the text editor I use. Snippets are templates Sublime inserts wherever you type the corresponding trigger strings.
Here are projects that show up in lists of high quality code, so I'll examine some of them and include any relevant discoveries in the project. All the projects I'm listing for now are in Python.
* [https://launchpad.net/bzr Bazaar]
* [https://github.com/boto/boto3 boto3]
* [https://github.com/django/django Django]
* [https://github.com/pallets/flask Flask]
* [https://github.com/gevent/gevent gevent]
* [https://www.mercurial-scm.org/downloads Mercurial]
* [https://github.com/nltk/nltk NLTK]
* [https://github.com/Pylons/pyramid Pyramid]
* [https://github.com/reddit/reddit reddit]
* [https://github.com/kennethreitz/requests Requests]
* [https://github.com/zzzeek/sqlalchemy SQLAlchemy]
* [https://github.com/kennethreitz/tablib Tablib]
* [https://github.com/tornadoweb/tornado Tornado]
* [http://trac.edgewall.org/browser/trunk/trac trac]
* [https://github.com/twisted/twisted Twisted]
* [https://github.com/rg3/youtube-dl youtube-dl]
In addition to these, I keep a mental list of software with features I might want to emulate, even if I don't plan to study their code very thoroughly:
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code Firefox] - automatic updating; possibly its add-on architecture, if it ever settles down
* [https://wordpress.org/download/source/ WordPress] - plugin hooks
== Bibliography ==
=== Architecture ===
Buschmann, Frank, ed. ''Pattern-Oriented Software Architecture: A System of Patterns''. Chichester ; New York: Wiley, 1996.
Fowler, Martin. ''Patterns of Enterprise Application Architecture''. The Addison-Wesley Signature Series. Boston: Addison-Wesley, 2003.
Martin, Robert C. ''Clean Architecture: A Craftsman’s Guide to Software Structure and Design''. Boston: Prentice Hall, 2018.
=== Continuous delivery ===
Humble, Jez, and David Farley. ''Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation''. Upper Saddle River, NJ: Addison-Wesley, 2010.
=== Debugging ===
Agans, David J. ''Debugging: The Nine Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems''. New York: Amacom, 2002.
=== Design ===
Evans, Eric. ''Domain-Driven Design: Tackling Complexity in the Heart of Software''. Boston: Addison-Wesley, 2004.
Gamma, Erich, ed. ''Design Patterns: Elements of Reusable Object-Oriented Software''. Addison-Wesley Professional Computing Series. Reading, Mass: Addison-Wesley, 1995.
Martin, Robert C., ed. ''Clean Code: A Handbook of Agile Software Craftsmanship''. Upper Saddle River, NJ: Prentice Hall, 2009.
McConnell, Steve. ''Code Complete''. 2nd ed. Redmond, Wash: Microsoft Press, 2004.
Raymond, Eric S. ''The Art of UNIX Programming: With Contributions from Thirteen UNIX Pioneers, Including Its Inventor, Ken Thompson''. Nachdr. Addison-Wesley Professional Computing Series. Boston: Addison-Wesley, 2008.
=== Privacy ===
Bowman, Courtney, Ari Gesher, John K. Grant, Daniel Slate, and Elissa Lerner. ''The Architecture of Privacy: On Engineering Technologies That Can Deliver Trustworthy Safeguards''. First edition. Sebastopol, CA: O’Reilly Media, 2015.
=== Project management ===
Fogel, Karl. ''Producing Open Source Software: How to Run a Successful Free Software Project''. Version 2.3106., 2018. https://producingoss.com/.
McConnell, Steve. ''Rapid Development: Taming Wild Software Schedules''. Redmond, Wash: Microsoft Press, 1996.
Stellman, Andrew, and Jennifer Greene. ''Learning Agile''. First edition. Beijing: O’Reilly, 2014.
=== Refactoring ===
Fowler, Martin, and Kent Beck. ''Refactoring: Improving the Design of Existing Code''. The Addison-Wesley Object Technology Series. Reading, MA: Addison-Wesley, 1999.
=== Requirements ===
McDonald, Kent J. ''Beyond Requirements: Analysis with an Agile Mindset''. New York: Addison-Wesley, 2016.
Patton, Jeff. ''User Story Mapping: Discover the Whole Story, Build the Right Product''. First edition. Beijing ; Sebastopol, CA: O’Reilly, 2014.
=== Security ===
Howard, Michael, David LeBlanc, and John Viega. ''24 Deadly Sins of Software Security: Programming Flaws and How to Fix Them''. New York: McGraw-Hill, 2010.
=== Stability ===
Nygard, Michael T. ''Release It! Design and Deploy Production-Ready Software''. Second edition. The Pragmatic Programmers. Raleigh, North Carolina: The Pragmatic Bookshelf, 2018.
=== Testing ===
Beck, Kent. ''Test-Driven Development: By Example''. The Addison-Wesley Signature Series. Boston: Addison-Wesley, 2003.
Feathers, Michael C., and Robert C. Martin. ''Working Effectively with Legacy Code''. Robert C. Martin Series. Upper Saddle River, NJ: Prentice Hall Professional Technical Reference, 2005.
Freeman, Steve, and Nat Pryce. ''Growing Object-Oriented Software, Guided by Tests''. The Addison-Wesley Signature Series. Upper Saddle River, NJ: Addison Wesley, 2010.
Meszaros, Gerard, and Martin Fowler. ''XUnit Test Patterns: Refactoring Test Code''. Upper Saddle River, New Jersey: Addison-Wesley, 2007.
=== User interface ===


Cooper, Alan. ''About Face: The Essentials of Interaction Design''. 4th edition. Indianapolis, IN: John Wiley and Sons, 2014.
== [[/Sources/]] ==


Rosenfeld, Louis, Peter Morville, and Jorge Arango. ''Information Architecture: For the Web and Beyond''. Fourth edition. Sebastopol, CA: O’Reilly Media, Inc, 2015.
See the article linked in the heading for a list of code examples and other sources I'm drawing from.


<disqus/>
<disqus/>

Latest revision as of 15:32, 10 May 2023

Introduction

This is a collection of notes on software development. Its main purpose is to help me raise my development's level of professionalism. It also gives me a place to air an opinion or two.

To give you an idea of my background, after some BASIC programming in my childhood and a break of many years for other interests, I returned to hobby programming just after undergrad and was able to make it my living several years later in 2006. That phase of my developer life started with Perl, and since then I've moved on to Python and XSLT. I've worked mainly in the area of text processing. JavaScript and PHP have played intermittent supporting roles for occasional web development or InDesign scripting. My projects have all been either solo or with a very small team. It's all been on Windows and mostly for the command line.

Topics

As a way to organize my notes and make sure I don't miss anything important, I'll use the structure of IEEE's Guide to the Software Engineering Body of Knowledge (SWEBOK). It's a standard that overviews the entire field and forms the basis for creating things like curricula and certifications. You can download the PDF for free.

The items under the SWEBOK knowledge areas in the first level link to my notes on each topic. I've sorted the knowledge areas to approximate my preferred order, though I'll address them more haphazardly.

Sources

See the article linked in the heading for a list of code examples and other sources I'm drawing from.

<disqus/>

Retrieved from "https://www.thinkulum.net/w/index.php?title=Software_Development&oldid=459"