Man if you actually use proper http status codes instead of returning 200 to every single request no matter the outcome, you’re already better than a lot of “senior” developers. If you’ve written any amount of half-useful readmes or docs or even comments, you’re well above the average. If you’re aware that git has more than 3 commands, you’re well on your way to godhood.
Man if you actually use proper http status codes instead of returning 200 to every single request no matter the outcome, you’re already better than a lot of “senior” developers. If you’ve written any amount of half-useful readmes or docs or even comments, you’re well above the average. If you’re aware that git has more than 3 commands, you’re well on your way to godhood.
Did you inherit the same project I did?
Did they also not use feature branches, API documentation, or any frontend framework, opting to create one based on jQuery instead?
I dazzle the youngins every time I
git rebaseWhereas I…uh… Give the youngins a memorable story to tell later, when I
git rebase.You mean every error shouldn’t be a 500?
Fantasticly written. I’m going to quote you in my team onboarding documents.