@JasonDJudge@PovilasKorop Comments are good when your function has complex code. In that case, it saves a lot of time, but if your func also does multiple things, it fails on single responsibility. Therefore should be broken down in smaller pieces for better readability
@Justificer885@PovilasKorop I should rephrase it, comments are not bad. It’s good to leave comments where you need them or where your code won’t make sense for co workers that stop by. If it’s a side project, leave all comments you need 😂
@PovilasKorop I’d recommend to read “Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C Martin aka Uncle bob.
Can’t tell you how much this man brought to the table in our day session with him, but it was an enlightenment.
@PovilasKorop The company I work for had Uncle bob as a guest speaker for all developers for a whole day. Here’s what I got:
- single responsibility
- a func should do 1 thing
- if u leave comments, you have failed to make your code understandable
- comments are good only when needed
@PovilasKorop We have a book club and we’re currently reading about design patterns and I can tell you that it has broaden my perspective on problem solving
@PovilasKorop I actually had the same issue when using it with Inertia Js. I ended up not declaring the responde type on my method to keep building. Is there a response type for Inertia renders?
@PovilasKorop I personally like to throw myself into the wolves. Meaning, if I don’t know it, I’ll learn it as there must be some docs I could read to understand how to make this happen. Because of this, I now have 3 clients that keep me busy besides my S.E FT job 🤩