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
-
Agree with @Pseudonymous, and I personally would say both, but books first. A well written book will give you a good understand of fundamentals, and generally be a good source of information, but researching things is good in terms of making sure you fully understand what the author is talking about and how tech discussed in the book has faired in modern times etc.
Also expert insight can be a good source to figuring out what you truly care about and what to "google". But that's just what I can say from what I've seen, and it may not apply to you. -
@tentsuriki np, there's usually a set "must read" items for different parts of the industry, like you'll come across "Clean code" and "pragmatic programmer" if you're interested in dev side of things, both of which are great books, fortunately/unfortunately I managed to cover the topics at work and figured out the advantages/disadvantages of naming/testing/threading without need for the book, but otherwise they would've been even better. Either way the must reads are usually a good start and then you should start figuring out what's worth reading!
do you think it's better learn from books, or just google everything that you want to learn?
question