New blog: Why we should write tests for our production code #246
Conversation
| @@ -0,0 +1,108 @@ | |||
| +++ | |||
| title = "Why We Should Write Tests for Our Production Code" | |||
There was a problem hiding this comment.
Can we change the blog title a bit
Here are some suggestions from gpt
There was a problem hiding this comment.
Yes sure we can change it, what about the last one Testing Production Code: Why It's Essential?
There was a problem hiding this comment.
To make it a bit more engaging: "Its 2025 and you should not write code without tests", goes with the suggestion in my previous comment
| type = "" | ||
| +++ | ||
|
|
||
| _(Insights from Clean Code by Robert C. Martin, Chapter 9: Unit Tests)_ |
There was a problem hiding this comment.
Lets link the book / chapter here
There was a problem hiding this comment.
@tilak-patidar the content looks good, I think it might be worthwhile to have a separate intro and conclusion
The intro can be along the lines of why shipping code without tests should be a total no in 2025, expand on that on a bit and then give a bit of context about the book and then go in
on the conclusion front you can mention things like what other benefits can come out of this, e.g mention how CI/CD can be brought in with automation testing
Ideas you can look into
Co-authored-by: Abhishek Keshri <iam2kabhishek@gmail.com>
Co-authored-by: Abhishek Keshri <iam2kabhishek@gmail.com>
Co-authored-by: Abhishek Keshri <iam2kabhishek@gmail.com>
Co-authored-by: Abhishek Keshri <iam2kabhishek@gmail.com>
Thank you for suggesting more improvements, I'll look into it and will add something. |
What did you do?
Please include a summary of the changes.
Why did you do it?
Why were these changes made?
Screenshots (Please include if anything visual)
Include any relevant screenshots that may help explain the change.