Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Don't Google first before coding. Use your thinking ability to code whatever you can no matter how shitty the code is or how fucked up it is on performance. After you have a working feature, go and Google and look for the right way to do it. Compare and learn.
-
willol13898yNo matter how good a programmer you are. The key of a project success is in communicating with people
-
Dont do stuff because you think it looks good on your resume/cv
Do stuff because you like it and it challenges you
If you keep on doing stuff that you think looks good on a resume/cv you'll most likely end up unhappy with work and change jobs alot, which incidently is not something you want on your cv
And that was advice given to me long before my dev life started -
Don't use single character variables or abbreviated function names — current me, talking to past me.
-
Live inside open source projects and see how others do it, and compare it with your own way.
As a self learning Dev, it helped me see how others think, and I sometimes come to no conclusion, for example: https://github.com/google/iosched/...
Google puts data model with the rest of the code , while I always put them inside a models folder, can't think of which if better since Google's way is good as it packages everything together, as for my way it does it by type.... I don't know 😔
What's the best advice anyone gave you in your dev life?
undefined