From b572f4f0e83fdde981f19a868a094ef638e21b81 Mon Sep 17 00:00:00 2001 From: Viljami Kuosmanen Date: Sat, 30 Nov 2024 09:10:16 +0100 Subject: [PATCH] Remove v2.html, bump pdf version --- README.md | 2 +- index.html | 4 +-- v2.html | 97 ------------------------------------------------------ 3 files changed, 3 insertions(+), 100 deletions(-) delete mode 100644 v2.html diff --git a/README.md b/README.md index be50276..e56e459 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@

Product Engineer Manifesto

- + diff --git a/index.html b/index.html index 6c91d36..6849234 100644 --- a/index.html +++ b/index.html @@ -24,7 +24,7 @@

Product Engineer Manifesto

- @@ -68,7 +68,7 @@

T
  • Product Engineer Checklist (PDF) diff --git a/v2.html b/v2.html deleted file mode 100644 index ce95613..0000000 --- a/v2.html +++ /dev/null @@ -1,97 +0,0 @@ - - - - - - - - Product Engineer Manifesto - - - - - - - - - - -
    -
    -

    Product Engineer Manifesto

    - -
    - - - - - - - - - -
    - -
    - -

    It is our responsibility as builders to first seek to understand the problem, before - diving into solutions.

    - -

    Our craft combines Product Thinking with great technical execution.

    - -

    We concern ourselves with design, technical, and business domains; - taking an active part in each to shape the product and empower others to do the same.

    - -

    We take great professional pride in the products we ship and refuse to - limit ourselves to technical-only roles in our teams.

    - - -

    The Product Engineer Mindset

    - -

    In our work as Product Engineers, we have come to value:

    - -
      -
    • Continuous delivery of working software over promises and estimations
      • - -
    • Asking why to understand the customer problem before diving into code
      • - -
    • Customer collaboration and feedback over tickets and second-hand knowledge
      • - -
    • Teamwork and communication over picking up tasks and working in isolation
      • - -
    • Testing the product ourselves over relying on others (especially our users) to find issues
      • - -
    • Domain knowledge and ownership over outsourcing strategic thinking to someone else
      • -
    - - - - -
    - - - - -