Sometimes it's easier to try a new idea in a new language (e.g. the borrow checker in Rust) rather than trying to shoehorn it into an existing language.
@programming.dev
I went to a top rated engineering school in the US and found the CS program easy. It helped that I enjoyed most of my classes, and that had been teaching myself for years before I got there. I had plenty of free time to spend with friends or whatever else.
While I've certainly had jobs that demanded long hours, I've had others that are more reasonable, and with good pay. It's more possible now to find a good paying job with good work/life balance than when I started working over 20 years ago.
Don't let the negative people scare you away from school or the industry. Ultimately your experience will be your own. If you find that the path you're on isn't working for you, just do something else!
If you don't feel like you're learning enough in your current role, tell your boss! It helps to be explicit about what your goals are in a conversation like this. Ideally they should be able to steer you towards work that better aligns with what you're looking for, or at least find a mentorship situation for you.
The recommendation to make small, focused changes and commit frequently are good practices for using git as well. Any changes a developer has locally are effectively a branch, so I don't see much of a difference between the two approaches, at least in the context of this article.
Nobody reading about the contest in the linked page should have to rely on Google to fully understand the parameters of the contest. Whoever authored this page is lazy.
"why" is a perfectly valid question to ask
thanks for using Leebra!
go to feed...