@niranjandb
Problem Solver | Front-end Engineer | Netflix Addict
Hi there! I'm a software professional with over 13 years of experience in developing software products. My passion lies in web development, and I specialize in using React to create engaging and user-friendly websites. Recently, I've embarked on an exciting journey into the world of machine learning, eager to explore its endless possibilities. Join me as I share my experiences, insights, and discoveries through my blog, where we can dive into the fascinating realm of software development, web development with React, and the exciting field of machine learning. Let's learn and grow together!
Nothing here yet.
Hello Curtis Einsmann and Tiger Abrodi , Interesting topic and discussion. I think the code review is indeed a very important topic along with unit tests. IMO, code review has more todo with people than actual code 😆 and hence some of the examples shared above become crucial. I had put my thoughts on similar lines a while back - https://blog.niranjanborawake.in/make-yourself-proud-by-reviewing-pull-requests
Nicely explained. As a team we need to understand that in a sprint we deliver a set of stories as a team which is Devs + QAs. Also, I don't recall if any team gives away Man/Woman of the Sprint award for an exceptional individual performance in a sprint.
Good points. Would like to add that on #2 one should be aware about clickbaiting and yes, maintaining quality of the content would help too 🙂. Congratulations on your progress 👍.