A lot of us will get the concept in place and see that we have success before paying more attention to the abstraction of the code and following design principles.
Or, as Donald Knuth so famously put it...
Premature optimization is the root of all evil.
You can't optimize something that isn't working yet. There are a lot of perspectives on this, but in my experience, "build first, refactor next" is by and away the most reliable approach. You may eventually form some habits and instincts regarding good and bad practice that affects your first attempt, but these are merely personal habits and conventions. You'll always need to refactor later for it to be truly good code.
Side Note: As an author, never apologize for "verbosity". Use as many words as you need to express your idea. William Strunk Jr. was right when he said "omit unnecessary words", but that's something you (or an editor) catch in revision. **Don't apologize to the reader for it.* If it matters, edit; if editing isn't a prioritization, just let it slide.
And, by the way, this article far from long-winded. If you want to see "verbose", I have a few rather long articles on this platform, although I'm not "sorry" for them. They're as long as it needed to be. TL;DR is the apathy-rooted enemy of learning.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Or, as Donald Knuth so famously put it...
You can't optimize something that isn't working yet. There are a lot of perspectives on this, but in my experience, "build first, refactor next" is by and away the most reliable approach. You may eventually form some habits and instincts regarding good and bad practice that affects your first attempt, but these are merely personal habits and conventions. You'll always need to refactor later for it to be truly good code.
Side Note: As an author, never apologize for "verbosity". Use as many words as you need to express your idea. William Strunk Jr. was right when he said "omit unnecessary words", but that's something you (or an editor) catch in revision. **Don't apologize to the reader for it.* If it matters, edit; if editing isn't a prioritization, just let it slide.
And, by the way, this article far from long-winded. If you want to see "verbose", I have a few rather long articles on this platform, although I'm not "sorry" for them. They're as long as it needed to be.
TL;DRis the apathy-rooted enemy of learning.