mirror of
https://github.com/adulau/pmf.git
synced 2024-12-21 16:26:04 +00:00
update: [PMF] clarify that PMF is applicable for open source but also
proprietary software
This commit is contained in:
parent
a756bac046
commit
f94580f3e9
GPG key ID:
09E2CD4944E6CBCD
5 changed files with 1364 additions and 764 deletions
2
Makefile
2
Makefile
|
|
@ -1,4 +1,4 @@
|
|||
MMARK:=/home/adulau/git/mmark/mmark/mmark -xml2 -page
|
||||
MMARK:=mmark
|
||||
|
||||
docs = $(wildcard raw.md)
|
||||
|
||||
|
|
|
|||
87
raw.md
87
raw.md
|
|
@ -1,41 +1,49 @@
|
|||
% Title = "Programming Methodology Framework aka PMF"
|
||||
% abbrev = "PMF - Programming Methodology Framework"
|
||||
% category = "info"
|
||||
% docName = "draft-dulaunoy-programming-methodology-framework"
|
||||
% ipr= "trust200902"
|
||||
% area = "Internet"
|
||||
% keyword = ["software engineering", "engineering", "pmf", "programming"]
|
||||
%
|
||||
% date = 2019-04-11T00:00:00Z
|
||||
%
|
||||
% [[author]]
|
||||
% initials="A."
|
||||
% surname="Dulaunoy"
|
||||
% fullname="Alexandre Dulaunoy"
|
||||
% abbrev="CIRCL"
|
||||
% organization = "Computer Incident Response Center Luxembourg"
|
||||
% [author.address]
|
||||
% email = "alexandre.dulaunoy@circl.lu"
|
||||
% phone = "+352 247 88444"
|
||||
% [author.address.postal]
|
||||
% street = "16, bd d'Avranches"
|
||||
% city = "Luxembourg"
|
||||
% code = "L-1160"
|
||||
% country = "Luxembourg"
|
||||
% [[author]]
|
||||
% initials="A."
|
||||
% surname="Iklody"
|
||||
% fullname="Andras Iklody"
|
||||
% abbrev="CIRCL"
|
||||
% organization = "Computer Incident Response Center Luxembourg"
|
||||
% [author.address]
|
||||
% email = "andras.iklody@circl.lu"
|
||||
% phone = "+352 247 88444"
|
||||
% [author.address.postal]
|
||||
% street = "16, bd d'Avranches"
|
||||
% city = "Luxembourg"
|
||||
% code = "L-1160"
|
||||
% country = "Luxembourg"
|
||||
%%%
|
||||
Title = "Programming Methodology Framework aka PMF"
|
||||
abbrev = "PMF - Programming Methodology Framework"
|
||||
category = "info"
|
||||
docName = "draft-dulaunoy-programming-methodology-framework"
|
||||
ipr= "trust200902"
|
||||
area = "Internet"
|
||||
keyword = ["software engineering", "engineering", "pmf", "programming"]
|
||||
|
||||
date = 2021-10-01T00:00:00Z
|
||||
|
||||
[seriesInfo]
|
||||
name = "Internet-Draft"
|
||||
value = "draft-01"
|
||||
stream = "independent"
|
||||
status = "informational"
|
||||
|
||||
[[author]]
|
||||
initials="A."
|
||||
surname="Dulaunoy"
|
||||
fullname="Alexandre Dulaunoy"
|
||||
abbrev="CIRCL"
|
||||
organization = "Computer Incident Response Center Luxembourg"
|
||||
[author.address]
|
||||
email = "alexandre.dulaunoy@circl.lu"
|
||||
phone = "+352 247 88444"
|
||||
[author.address.postal]
|
||||
street = "16, bd d'Avranches"
|
||||
city = "Luxembourg"
|
||||
code = "L-1160"
|
||||
country = "Luxembourg"
|
||||
[[author]]
|
||||
initials="A."
|
||||
surname="Iklody"
|
||||
fullname="Andras Iklody"
|
||||
abbrev="CIRCL"
|
||||
organization = "Computer Incident Response Center Luxembourg"
|
||||
[author.address]
|
||||
email = "andras.iklody@circl.lu"
|
||||
phone = "+352 247 88444"
|
||||
[author.address.postal]
|
||||
street = "16, bd d'Avranches"
|
||||
city = "Luxembourg"
|
||||
code = "L-1160"
|
||||
country = "Luxembourg"
|
||||
%%%
|
||||
|
||||
.# Abstract
|
||||
|
||||
|
|
@ -85,6 +93,9 @@ A simplified overview of the process can be described as follow:
|
|||
+----------+
|
||||
~~~~~
|
||||
|
||||
|
||||
The PMF methodology covers open source software along with proprietary software and can be used interchangeably in both.
|
||||
|
||||
## Management and PMF methodology
|
||||
|
||||
A simple management process is a requirement of the PMF methodology.
|
||||
|
|
|
|||
1751
raw.md.html
1751
raw.md.html
File diff suppressed because it is too large
Load diff
132
raw.md.txt
132
raw.md.txt
|
|
@ -5,11 +5,11 @@
|
|||
Network Working Group A. Dulaunoy
|
||||
Internet-Draft A. Iklody
|
||||
Intended status: Informational CIRCL
|
||||
Expires: October 13, 2019 April 11, 2019
|
||||
Expires: 4 April 2022 1 October 2021
|
||||
|
||||
|
||||
Programming Methodology Framework aka PMF
|
||||
draft-dulaunoy-programming-methodology-framework
|
||||
draft-01
|
||||
|
||||
Abstract
|
||||
|
||||
|
|
@ -37,30 +37,29 @@ Status of This Memo
|
|||
time. It is inappropriate to use Internet-Drafts as reference
|
||||
material or to cite them other than as "work in progress."
|
||||
|
||||
This Internet-Draft will expire on October 13, 2019.
|
||||
This Internet-Draft will expire on 4 April 2022.
|
||||
|
||||
Copyright Notice
|
||||
|
||||
Copyright (c) 2019 IETF Trust and the persons identified as the
|
||||
Copyright (c) 2021 IETF Trust and the persons identified as the
|
||||
document authors. All rights reserved.
|
||||
|
||||
This document is subject to BCP 78 and the IETF Trust's Legal
|
||||
Provisions Relating to IETF Documents
|
||||
(https://trustee.ietf.org/license-info) in effect on the date of
|
||||
publication of this document. Please review these documents
|
||||
carefully, as they describe your rights and restrictions with respect
|
||||
to this document. Code Components extracted from this document must
|
||||
Provisions Relating to IETF Documents (https://trustee.ietf.org/
|
||||
license-info) in effect on the date of publication of this document.
|
||||
Please review these documents carefully, as they describe your rights
|
||||
and restrictions with respect to this document. Code Components
|
||||
extracted from this document must include Simplified BSD License text
|
||||
|
||||
|
||||
|
||||
Dulaunoy & Iklody Expires October 13, 2019 [Page 1]
|
||||
Dulaunoy & Iklody Expires 4 April 2022 [Page 1]
|
||||
|
||||
Internet-Draft PMF - Programming Methodology Framework April 2019
|
||||
Internet-Draft PMF - Programming Methodology Framework October 2021
|
||||
|
||||
|
||||
include Simplified BSD License text as described in Section 4.e of
|
||||
the Trust Legal Provisions and are provided without warranty as
|
||||
described in the Simplified BSD License.
|
||||
as described in Section 4.e of the Trust Legal Provisions and are
|
||||
provided without warranty as described in the Simplified BSD License.
|
||||
|
||||
Table of Contents
|
||||
|
||||
|
|
@ -69,20 +68,19 @@ Table of Contents
|
|||
1.2. Conventions and Terminology . . . . . . . . . . . . . . . 3
|
||||
2. Security Considerations . . . . . . . . . . . . . . . . . . . 3
|
||||
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
|
||||
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
|
||||
4.1. Normative References . . . . . . . . . . . . . . . . . . 4
|
||||
4.2. Informative References . . . . . . . . . . . . . . . . . 4
|
||||
4. Normative References . . . . . . . . . . . . . . . . . . . . 4
|
||||
5. Informative References . . . . . . . . . . . . . . . . . . . 4
|
||||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
|
||||
|
||||
1. Introduction
|
||||
|
||||
In 2011, Zed A. Shaw published a blog post which describes:
|
||||
|
||||
I think I'm going to create the ultimate software development
|
||||
methodology. It'll be revolutionary compared to others because it
|
||||
will focus on the one thing that gets software done. Its entire
|
||||
focus will be this one, glorious, completely useful activity for
|
||||
writing software. It's name even embodies the perfection of this
|
||||
{align="left"} I think I'm going to create the ultimate software
|
||||
development methodology. It'll be revolutionary compared to others
|
||||
because it will focus on the one thing that gets software done. Its
|
||||
entire focus will be this one, glorious, completely useful activity
|
||||
for writing software. It's name even embodies the perfection of this
|
||||
programming methodology.
|
||||
|
||||
The PMF methodology was published as a manifesto later
|
||||
|
|
@ -94,12 +92,12 @@ Table of Contents
|
|||
|
||||
The overall concept of PMF methodology follows the following process:
|
||||
|
||||
o Compose a list of features to be implemented and use an iterative
|
||||
* Compose a list of features to be implemented and use an iterative
|
||||
programming process.
|
||||
|
||||
o Enhance said features using trial and error programming.
|
||||
* Enhance said features using trial and error programming.
|
||||
|
||||
o Orchestrate your testing and integration processes using pragmatic
|
||||
* Orchestrate your testing and integration processes using pragmatic
|
||||
programming.
|
||||
|
||||
Repeat the above process until the software is delivered.
|
||||
|
|
@ -109,30 +107,35 @@ Table of Contents
|
|||
|
||||
|
||||
|
||||
Dulaunoy & Iklody Expires October 13, 2019 [Page 2]
|
||||
|
||||
|
||||
Dulaunoy & Iklody Expires 4 April 2022 [Page 2]
|
||||
|
||||
Internet-Draft PMF - Programming Methodology Framework April 2019
|
||||
Internet-Draft PMF - Programming Methodology Framework October 2021
|
||||
|
||||
|
||||
+----------+
|
||||
| |
|
||||
| idea <------+
|
||||
| | |
|
||||
+----+-----+ |
|
||||
| |
|
||||
| |
|
||||
+----v-----+ |
|
||||
| | | it doesn't work
|
||||
| code | |
|
||||
| | |
|
||||
+----+-----+ |
|
||||
| |
|
||||
| |
|
||||
+----v-----+ |
|
||||
| | |
|
||||
| release +------+
|
||||
| |
|
||||
+----------+
|
||||
+----------+
|
||||
| |
|
||||
| idea <------+
|
||||
| | |
|
||||
+----+-----+ |
|
||||
| |
|
||||
| |
|
||||
+----v-----+ |
|
||||
| | | it doesn't work
|
||||
| code | |
|
||||
| | |
|
||||
+----+-----+ |
|
||||
| |
|
||||
| |
|
||||
+----v-----+ |
|
||||
| | |
|
||||
| release +------+
|
||||
| |
|
||||
+----------+
|
||||
|
||||
The PMF methodology covers open source software along with
|
||||
proprietary software and can be used interchangeably in both.
|
||||
|
||||
1.1. Management and PMF methodology
|
||||
|
||||
|
|
@ -141,11 +144,11 @@ Internet-Draft PMF - Programming Methodology Framework April 2019
|
|||
interfering with the programming aspect and solely serves to support
|
||||
the PMF methodology.
|
||||
|
||||
o Collect requirements of the users/customers.
|
||||
* Collect requirements of the users/customers.
|
||||
|
||||
o Provide programmers with the desired requirements.
|
||||
* Provide programmers with the desired requirements.
|
||||
|
||||
o Review whether the software to be delivered matches the
|
||||
* Review whether the software to be delivered matches the
|
||||
requirements.
|
||||
|
||||
1.2. Conventions and Terminology
|
||||
|
|
@ -162,53 +165,48 @@ Internet-Draft PMF - Programming Methodology Framework April 2019
|
|||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Dulaunoy & Iklody Expires October 13, 2019 [Page 3]
|
||||
Dulaunoy & Iklody Expires 4 April 2022 [Page 3]
|
||||
|
||||
Internet-Draft PMF - Programming Methodology Framework April 2019
|
||||
Internet-Draft PMF - Programming Methodology Framework October 2021
|
||||
|
||||
|
||||
3. Acknowledgements
|
||||
|
||||
The authors wish to thank all the programmers who program.
|
||||
|
||||
4. References
|
||||
|
||||
4.1. Normative References
|
||||
4. Normative References
|
||||
|
||||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
|
||||
Requirement Levels", BCP 14, RFC 2119,
|
||||
DOI 10.17487/RFC2119, March 1997,
|
||||
<https://www.rfc-editor.org/info/rfc2119>.
|
||||
|
||||
4.2. Informative References
|
||||
5. Informative References
|
||||
|
||||
[PROGRAMMING-MF-MANIFESTO]
|
||||
Shaw, "Programming Motherfucker, do you speak it?",
|
||||
<http://programming-motherfucker.com>.
|
||||
Shaw, Z. A., "Programming Motherfucker, do you speak it?",
|
||||
, October 2021, <http://programming-motherfucker.com>.
|
||||
|
||||
[THE-TAO-OF-PROGRAMMING]
|
||||
James, "The Tao of Programming",
|
||||
James, G., "The Tao of Programming", , October 2021,
|
||||
<http://www.mit.edu/~xela/tao.html>.
|
||||
|
||||
Authors' Addresses
|
||||
|
||||
Alexandre Dulaunoy
|
||||
Computer Incident Response Center Luxembourg
|
||||
Alexandre Dulaunoy
|
||||
16, bd d'Avranches
|
||||
Luxembourg L-1160
|
||||
L-L-1160 Luxembourg
|
||||
Luxembourg
|
||||
|
||||
Phone: +352 247 88444
|
||||
Email: alexandre.dulaunoy@circl.lu
|
||||
|
||||
|
||||
Andras Iklody
|
||||
Computer Incident Response Center Luxembourg
|
||||
Andras Iklody
|
||||
16, bd d'Avranches
|
||||
Luxembourg L-1160
|
||||
L-L-1160 Luxembourg
|
||||
Luxembourg
|
||||
|
||||
Phone: +352 247 88444
|
||||
|
|
@ -221,4 +219,6 @@ Authors' Addresses
|
|||
|
||||
|
||||
|
||||
Dulaunoy & Iklody Expires October 13, 2019 [Page 4]
|
||||
|
||||
|
||||
Dulaunoy & Iklody Expires 4 April 2022 [Page 4]
|
||||
|
|
|
|||
156
raw.md.xml
156
raw.md.xml
|
|
@ -1,49 +1,22 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' []>
|
||||
<rfc ipr="trust200902" category="info" docName="draft-dulaunoy-programming-methodology-framework">
|
||||
<?rfc toc="yes"?>
|
||||
<?rfc symrefs="yes"?>
|
||||
<?rfc sortrefs="yes"?>
|
||||
<?rfc compact="yes"?>
|
||||
<?rfc subcompact="no"?>
|
||||
<?rfc private=""?>
|
||||
<?rfc topblock="yes"?>
|
||||
<?rfc comments="no"?>
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
|
||||
<rfc version="3" ipr="trust200902" docName="draft-01" submissionType="IETF" category="info" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="false" consensus="true">
|
||||
|
||||
<front>
|
||||
<title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title>
|
||||
|
||||
<author initials="A." surname="Dulaunoy" fullname="Alexandre Dulaunoy">
|
||||
<organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization>
|
||||
<address>
|
||||
<postal>
|
||||
<street>16, bd d'Avranches</street>
|
||||
<title abbrev="PMF - Programming Methodology Framework">Programming Methodology Framework aka PMF</title><seriesInfo value="draft-01" stream="independent" status="informational" name="Internet-Draft"></seriesInfo>
|
||||
<author initials="A." surname="Dulaunoy" fullname="Alexandre Dulaunoy"><organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization><address><postal><street>16, bd d'Avranches</street>
|
||||
<city>Luxembourg</city>
|
||||
<code>L-1160</code>
|
||||
<country>Luxembourg</country>
|
||||
<region></region>
|
||||
</postal>
|
||||
<phone>+352 247 88444</phone>
|
||||
</postal><phone>+352 247 88444</phone>
|
||||
<email>alexandre.dulaunoy@circl.lu</email>
|
||||
<uri></uri>
|
||||
</address>
|
||||
</author>
|
||||
<author initials="A." surname="Iklody" fullname="Andras Iklody">
|
||||
<organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization>
|
||||
<address>
|
||||
<postal>
|
||||
<street>16, bd d'Avranches</street>
|
||||
</address></author><author initials="A." surname="Iklody" fullname="Andras Iklody"><organization abbrev="CIRCL">Computer Incident Response Center Luxembourg</organization><address><postal><street>16, bd d'Avranches</street>
|
||||
<city>Luxembourg</city>
|
||||
<code>L-1160</code>
|
||||
<country>Luxembourg</country>
|
||||
<region></region>
|
||||
</postal>
|
||||
<phone>+352 247 88444</phone>
|
||||
</postal><phone>+352 247 88444</phone>
|
||||
<email>andras.iklody@circl.lu</email>
|
||||
<uri></uri>
|
||||
</address>
|
||||
</author>
|
||||
<date year="2019" month="April" day="11"/>
|
||||
|
||||
</address></author><date year="2021" month="October" day="1"></date>
|
||||
<area>Internet</area>
|
||||
<workgroup></workgroup>
|
||||
<keyword>software engineering</keyword>
|
||||
|
|
@ -51,42 +24,31 @@
|
|||
<keyword>pmf</keyword>
|
||||
<keyword>programming</keyword>
|
||||
|
||||
|
||||
<abstract>
|
||||
<t>This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw <xref target="PROGRAMMING-MF-MANIFESTO"/> which
|
||||
<t>This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw <xref target="PROGRAMMING-MF-MANIFESTO"></xref> which
|
||||
describes a natural approach to software engineering with a strong focus on the act of programming. The PMF methodology uses a soft naming to allow for a non-partisan reference
|
||||
to official engineering or project documents describing one of the most used software engineering methodologies.
|
||||
</t>
|
||||
to official engineering or project documents describing one of the most used software engineering methodologies.</t>
|
||||
</abstract>
|
||||
|
||||
|
||||
</front>
|
||||
|
||||
<middle>
|
||||
|
||||
<section anchor="introduction" title="Introduction">
|
||||
<t>In 2011, Zed A. Shaw published a blog post which describes:
|
||||
</t>
|
||||
<t>I think I'm going to create the ultimate software development methodology. It'll be revolutionary compared to others because it will focus on the one thing that gets software done. Its entire focus will be this one, glorious, completely useful activity for writing software. It's name even embodies the perfection of this programming methodology.
|
||||
</t>
|
||||
<t>The PMF methodology was published as a manifesto later <xref target="PROGRAMMING-MF-MANIFESTO"/>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <xref target="THE-TAO-OF-PROGRAMMING"/> describes similar methodologies which strongly focus on coding, scripting and programming.
|
||||
</t>
|
||||
<t>The overall concept of PMF methodology follows the following process:
|
||||
</t>
|
||||
<t>
|
||||
<list style="symbols">
|
||||
<t>Compose a list of features to be implemented and use an iterative programming process.</t>
|
||||
<t>Enhance said features using trial and error programming.</t>
|
||||
<t>Orchestrate your testing and integration processes using pragmatic programming.</t>
|
||||
</list>
|
||||
</t>
|
||||
<t>Repeat the above process until the software is delivered.
|
||||
</t>
|
||||
<t>A simplified overview of the process can be described as follow:
|
||||
</t>
|
||||
<section anchor="introduction"><name>Introduction</name>
|
||||
<t>In 2011, Zed A. Shaw published a blog post which describes:</t>
|
||||
<t>{align="left"} I think I'm going to create the ultimate software development methodology. It'll be revolutionary compared to others because it will focus on the one thing that gets software done. Its entire focus will be this one, glorious, completely useful activity for writing software. It's name even embodies the perfection of this programming methodology.</t>
|
||||
<t>The PMF methodology was published as a manifesto later <xref target="PROGRAMMING-MF-MANIFESTO"></xref>. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The <xref target="THE-TAO-OF-PROGRAMMING"></xref> describes similar methodologies which strongly focus on coding, scripting and programming.</t>
|
||||
<t>The overall concept of PMF methodology follows the following process:</t>
|
||||
|
||||
<figure align="center"><artwork align="center" type="ascii-art">
|
||||
+----------+
|
||||
<ul>
|
||||
<li>Compose a list of features to be implemented and use an iterative programming process.</li>
|
||||
<li>Enhance said features using trial and error programming.</li>
|
||||
<li>Orchestrate your testing and integration processes using pragmatic programming.</li>
|
||||
</ul>
|
||||
<t>Repeat the above process until the software is delivered.</t>
|
||||
<t>A simplified overview of the process can be described as follow:</t>
|
||||
|
||||
<sourcecode type="ascii-art">+----------+
|
||||
| |
|
||||
| idea <------+
|
||||
| | |
|
||||
|
|
@ -105,62 +67,62 @@ to official engineering or project documents describing one of the most used sof
|
|||
| release +------+
|
||||
| |
|
||||
+----------+
|
||||
</artwork></figure>
|
||||
</sourcecode>
|
||||
<t>The PMF methodology covers open source software along with proprietary software and can be used interchangeably in both.</t>
|
||||
|
||||
<section anchor="management-and-pmf-methodology" title="Management and PMF methodology">
|
||||
<section anchor="management-and-pmf-methodology"><name>Management and PMF methodology</name>
|
||||
<t>A simple management process is a requirement of the PMF methodology.
|
||||
The management process is meant to be complementary instead of interfering with
|
||||
the programming aspect and solely serves to support the PMF methodology.
|
||||
</t>
|
||||
<t>
|
||||
<list style="symbols">
|
||||
<t>Collect requirements of the users/customers.</t>
|
||||
<t>Provide programmers with the desired requirements.</t>
|
||||
<t>Review whether the software to be delivered matches the requirements.</t>
|
||||
</list>
|
||||
</t>
|
||||
the programming aspect and solely serves to support the PMF methodology.</t>
|
||||
|
||||
<ul>
|
||||
<li>Collect requirements of the users/customers.</li>
|
||||
<li>Provide programmers with the desired requirements.</li>
|
||||
<li>Review whether the software to be delivered matches the requirements.</li>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<section anchor="conventions-and-terminology" title="Conventions and Terminology">
|
||||
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
|
||||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
|
||||
document are to be interpreted as described in RFC 2119 <xref target="RFC2119"/>.
|
||||
</t>
|
||||
<section anchor="conventions-and-terminology"><name>Conventions and Terminology</name>
|
||||
<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
|
||||
"<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this
|
||||
document are to be interpreted as described in RFC 2119 <xref target="RFC2119"></xref>.</t>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section anchor="security-considerations" title="Security Considerations">
|
||||
<section anchor="security-considerations"><name>Security Considerations</name>
|
||||
<t>Secure and defensive programming can only come by practicing programming and this also
|
||||
includes the act of simplifying or removing code to reduce the attack surface.
|
||||
</t>
|
||||
includes the act of simplifying or removing code to reduce the attack surface.</t>
|
||||
</section>
|
||||
|
||||
<section anchor="acknowledgements" title="Acknowledgements">
|
||||
<t>The authors wish to thank all the programmers who program.
|
||||
</t>
|
||||
<section anchor="acknowledgements"><name>Acknowledgements</name>
|
||||
<t>The authors wish to thank all the programmers who program.</t>
|
||||
</section>
|
||||
|
||||
</middle>
|
||||
|
||||
<back>
|
||||
<references title="Normative References">
|
||||
<?rfc include="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
|
||||
<references><name>Normative References</name>
|
||||
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
|
||||
</references>
|
||||
<references title="Informative References">
|
||||
<reference anchor='PROGRAMMING-MF-MANIFESTO' target='http://programming-motherfucker.com'>
|
||||
<references><name>Informative References</name>
|
||||
<reference anchor="PROGRAMMING-MF-MANIFESTO" target="http://programming-motherfucker.com">
|
||||
<front>
|
||||
<title>Programming Motherfucker, do you speak it?</title>
|
||||
<author initials='' surname='Shaw' fullname='Zed A. Shaw'></author>
|
||||
<date></date>
|
||||
<title>Programming Motherfucker, do you speak it?</title>
|
||||
<author fullname="Zed A. Shaw" surname="Shaw"></author>
|
||||
<date></date>
|
||||
</front>
|
||||
<refcontent></refcontent>
|
||||
</reference>
|
||||
<reference anchor='THE-TAO-OF-PROGRAMMING' target='http://www.mit.edu/~xela/tao.html'>
|
||||
<reference anchor="THE-TAO-OF-PROGRAMMING" target="http://www.mit.edu/~xela/tao.html">
|
||||
<front>
|
||||
<title>The Tao of Programming</title>
|
||||
<author initials='' surname='James' fullname='Geoffrey James'></author>
|
||||
<date></date>
|
||||
<title>The Tao of Programming</title>
|
||||
<author fullname="Geoffrey James" surname="James"></author>
|
||||
<date></date>
|
||||
</front>
|
||||
<refcontent></refcontent>
|
||||
</reference>
|
||||
</references>
|
||||
|
||||
</back>
|
||||
|
||||
</rfc>
|
||||
|
|
|
|||
Loading…
Reference in a new issue