Skip to content

Commit a40231f

Browse files
authored
Merge pull request #4184 from kevin8999/patch-1
docs(part 1d): Revise Web Programmer's Oath to improve clarity
2 parents 3d54771 + 1fdadfa commit a40231f

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

src/content/1/en/part1d.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1125,15 +1125,15 @@ You may find the following links useful:
11251125
- The [official React documentation](https://react.dev/learn) is worth checking out at some point, although most of it will become relevant only later on in the course. Also, everything related to class-based components is irrelevant to us;
11261126
- Some courses on [Egghead.io](https://egghead.io) like [Start learning React](https://egghead.io/courses/start-learning-react) are of high quality, and the recently updated [Beginner's Guide to React](https://egghead.io/courses/the-beginner-s-guide-to-reactjs) is also relatively good; both courses introduce concepts that will also be introduced later on in this course. **NB** The first one uses class components but the latter uses the new functional ones.
11271127

1128-
### Web programmers oath
1128+
### Web Programmer's Oath
11291129

1130-
Programming is hard, that is why I will use all the possible means to make it easier
1130+
Programming is hard. That is why, as a developer, I will use all possible means to make it easier.
11311131

1132-
- I will have my browser developer console open all the time
1133-
- I progress with small steps
1134-
- I will write lots of _console.log_ statements to make sure I understand how the code behaves and to help pinpointing problems
1135-
- If my code does not work, I will not write more code. Instead I will start deleting the code until it works or just return to a state when everything was still working
1136-
- When I ask for help in the course Discord channel or elsewhere I formulate my questions properly, see [here](http://fullstackopen.com/en/part0/general_info#how-to-get-help-in-discord) how to ask for help
1132+
- I will have my browser's developer console open at all times.
1133+
- I will progress in small steps, making sure that my code is working at each step.
1134+
- I will write many _console.log_ statements to make sure I understand how the code behaves and to help pinpointing problems.
1135+
- If my code does not work, I will not write more code. Instead, I will either start deleting the code until it works or return to a state where my program was working.
1136+
- When I ask for help in the course Discord channel or elsewhere, I will formulate my questions properly. See [this section](http://fullstackopen.com/en/part0/general_info#how-to-get-help-in-discord) to learn how to ask for help.
11371137

11381138
### Utilization of Large language models
11391139

0 commit comments

Comments
 (0)