daily-email: add 2023-03-13
This commit is contained in:
parent
c386f4f3c6
commit
4f3570f155
16
website/src/daily-emails/2023-03-13.md
Normal file
16
website/src/daily-emails/2023-03-13.md
Normal file
|
@ -0,0 +1,16 @@
|
||||||
|
---
|
||||||
|
title: >
|
||||||
|
What problem are we trying to solve?
|
||||||
|
pubDate: 2023-03-13
|
||||||
|
permalink: >
|
||||||
|
archive/2023/03/13/what-problem-am-i-trying-to-solve
|
||||||
|
tags: []
|
||||||
|
---
|
||||||
|
|
||||||
|
This is a question that I always ask before starting any development task, and I was very happy to see a slide in one of the keynote sessions at nor(DEV):con asking this question.
|
||||||
|
|
||||||
|
I'd much rather have a collegue or client come to me with a problem that needs solving rather than a self-diagnosis and a decided solution.
|
||||||
|
|
||||||
|
Depending what on the problem is, and other factors like timescales, I may suggest a different solution or approach. This happened recently when I suggested a different approach using Drupal's built-in maintenance mode feature.
|
||||||
|
|
||||||
|
If there's no problem to solve, what's the reason for doing the work?
|
Loading…
Reference in a new issue