sansguidon/bookmarks
1
0
Fork 0
Code Issues 16 Pull Requests 1 Projects 1 Activity

(2021) Think first about what problem this is solving and for whom

Browse Source
This commit is contained in:
Morgan 2021-02-08 18:30:22 +01:00 committed by GitHub
parent e2bbae1671
commit 8f379d7bac
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
sections/programming.md
View File

@ -776,6 +776,11 @@ See also [Calm programming / Slow programming](#calm-programming--slow-programmi
> * Don’t prematurely optimize
* :star: [**Phil Eaton**](https://notes.eatonphil.com/the-case-for-comments-in-code.html) - (2020) The case for comments in code
> More so than all other tools (issue tracker, code management system, etc.) comments in code have the greatest chance of still being around and easily searchable if they haven't been deleted.
* [Dan Moore](https://letterstoanewdeveloper.com/2021/01/18/think-first-about-what-problem-this-is-solving-and-for-whom/) - (2021) Think first about what problem this is solving and for whom
> every time you pick up a new Jira ticket or sit down to complete a new requirement, I suggest that you ask yourself the following questions:
> * Who does this solve a problem for?
> * What is the problem they’re trying to solve?
> * How does this ticket solve it?
## Conferences
> In Belgium