You add a feature allowing one to schedule when the writing becomes publicly available. But, you forgot to notify the daily entry police. The user is in doubt as to whether they have written yet. They publish. They now see they have already written.
Writing code requires thinking about the systems and interactions involved.
Software development is systems thinking.
You're thinking about how things interact. Inputs and outputs. Flows and stores.
You're looking for the edge cases.
What happens when a person clicks this button?
What state of affairs are you changing and updating or removing?
Does the software monitor events based on time or user input?
Is the timing important? Do you need to consider timezones and daylight savings time and the twenty-four hour clock?
What about human error? When they submit their words, should I let them edit?
Twitter does not. However, you can allow them to delete the words and re-write them.
How do I make decisions?
What is my process?
Who do I consult?
How do I recover from errors?
How do I handle embarrassment?
Is there any legal risk to making something available?
What is the agreement I'm entering into by allowing people to write their words into my database?
Do I need to consider privacy issues?
What if I get sued?
What if I forget my login credentials?
What if I get hacked?
How transparent do I need to be?
Where do I collect the bugs? Are they public or private?
We still call them bugs.