Software dev at Netflix | DC techie | Conference speaker | egghead Instructor | TC39 Educators Committee | Girls Who Code Facilitator | Board game geek | @laurieontech on twitter
I think context is important here. I think we should all feel comfortable admitting that we all write terrible code at points!
When we're learning something new
When we're in a rush
When we haven't properly defined the problem
However, that doesn't mean we're satisfied with that code. I'd hope that "terrible code" is our starting point. That we start there and make it better. That we don't put code in production unless we are confident it is reasonably maintainable for others, or even our future selves!
There is no shame in terrible code. We should normalize terrible code writing. But I'd caution us against accepting terrible code as a final solution.
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.
I think context is important here. I think we should all feel comfortable admitting that we all write terrible code at points!
However, that doesn't mean we're satisfied with that code. I'd hope that "terrible code" is our starting point. That we start there and make it better. That we don't put code in production unless we are confident it is reasonably maintainable for others, or even our future selves!
There is no shame in terrible code. We should normalize terrible code writing. But I'd caution us against accepting terrible code as a final solution.