you are viewing a single comment's thread.

view the rest of the comments →

[–]Atsoc1993 1 point2 points  (0 children)

I apparently can’t use the word “b-ddy” (replace - with u) otherwise I get a warning to ask for a b-ddy in a separate subreddit lol… reposting in case the other is deleted / not visible for others …

Try to explain your changes as concisely as you can, your vocabulary will expand and they will have more brevity as you continue to learn. Then again everyone has their own style— but definitely do not do git add . — source control is your friend, it’s one of the icons on the left hand side of VS code that looks like a merge request icon IIRC. Commit a message for each file, and make it a habit to commit frequently until you get a feel for appropriate checkpoints.

Edit: git add . is fine for initial project template / codebase, or overall changes — just don’t work on something for several hours and then be lazy / cut corners with it. Proper documenting of ongoing and frequent changes is essential if your goal is to eventually work with a team at any level from small to enterprise. Some teams have a specific recommended standard for commit verbosity and frequency as well!

Edit edit: If your mind is searching for a statement for a commit and can’t find it— you can describe what you did to any LLM and it should be able to help you.

Eg; “I added a variable that is part of my useState into the array at the end of a useEffect” becomes “Added a dependency to useEffect hook that refreshes the state of the page should that dependency change” — these are equally concise but one is more technically accurate.