The Principal Dev

class: middle, center, splash
# The **Principal** Dev
???
- Make some noize!
- Welcome, I will teach you principles (portable across domain). You can figure out practices.
- Split into teams of 4, know each other names, role and background.

---
background-image:url(manif0.png)
background-size: contain

---
background-image:url(manif1.png)
background-size: contain

---
background-image:url(manifesto0.png)
background-size: contain
???
- close as many JIRA issues as possible?
- deliver new features? : )

---
background-image:url(manifesto1.png)
background-size: contain
???
- never ask a barber if you need a haircut (bias.)
- if the only tool you have is a hammer, then every problem look like a nail.

---
class: center, middle
## Customers don't need software and features. *They need cost-effective solutions to their problems.*

---
class: center, middle
![:ribbon Exercise, small]
## Why software is *not* always cost-effective?
???
- hiring.
- motivation.
- well-crafted software is expensive; crappy software even more so.
- manual labour can be cheaper than automation.
- software is always a liability. Sometimes an asset.
- software should be kept up2date (e.g. Node updates etc.)
- software may hinder business agility (software is an artefact that need to be changed).
- softwate teams lose effeciecy as they scale (diseconomies of scale). Minimize output, and maximize outcome and impact.
- more features => higher ToC (including 'invisible parts' like customer service, slower teams)
- more features => worse UX => unhappier users
- opportunity cost.
- data compliance.
- no-code solutions (github.com/kelseyhightower/nocode)

---
class: img50, center
## Our highest priority is to .hide[find **cost-effective** solutions to customers' problems.]

---
class: img50, center
## Our highest priority is to find **cost-effective** solutions to customers' problems.

---
class: center, middle
### 💡 The process of finding the cost-effective solution from a list of alternatives is called *Cost-Benefit Analysis (CBA)*.
#### speed · cost · benefit · risk

---
class: center, middle
![:ribbon Exercise, small]
### Find a cost-effective solution to the following problems:
???
- preferably, without writing much code.

---
class: center, middle
![:ribbon Exercise, small]
### (1/2) Backlog Item #JR-1234:
#### Taxpayers are required to submit tax reports from February 1st to March 31st. Every year, during that period, our system becomes unresponsive, because taxpayers rush to submit documents as soon as they receive email reminders. Solution suggested by the chief architect: make the system auto-scalable by migrating to AWS. 🙈

---
class: center, middle
![:ribbon Exercise, small]
### (2/2) Backlog Item #JR-2345:
#### As a business analyst, I want a UI for complex data querying, filtering, and reporting so that other business analysts and I can query any information from the database, analyze data, and build visual reports. See UX wireframes enclosed. 🙉

---
class: center, middle
### 💡 Don't do what the customer wants. Do what the customer needs.
#### (cost-effectively)

---
class: center, middle
### 💩  Shielding developers from dealing with the business leads to low trust, low motivation, mediocre software solutions (*software is the implementation of the business*), and turns on destructive reinforcing loop.

---
class: center, middle
### ♻️ Less involvement → less understanding → less impact → less involvement.
#### (if devs cannot find meaning in business, they'll find it in tech.)

---
class: center, middle
<video height="500" controls>
 <source src="product_owner_proxy.mp4" type="video/mp4">
</video>

---
background-image:url(manifesto_business.png)
background-size: contain
???
- Like in a startup.

---
#### 1. Job title "**.question[〰️〰️〰️〰️].answer[solution]** developer" better describes our job.