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
-
I'm actually getting into and learning lots of stuff at my job (i'm currently a trainee so that's kinda the point)
So far i've learned lots of stuff about javascript (i had NO knowledge, only some java when i first started there), some testing stuffs, and as of this week i'm getting my feet wet with docker -
For me its a mix of both. Im very much a proponent of the "fail faster" prototyping approach that I learned from game design books. But when I do fail, I usually look up why exactly and that way I learn about all the things I dont need right now and that dont work as I expected them, but might need in the future and now they are in my head catalogue of options
Related Rants
Everything is going as planned
How many of you feel you learn something on the job?
As for myself, I learn much more from books than sitting day in, day out at work, doing more or less of the same things.
To me, this whole trial-and-error way of 'learning' is not really learning. I don't subscribe to this dogma. I don't 'learn' by messing up and fixing something. I need a full specification of why something works, when and how. I'm not satisfied by just being a code plumber.
This, next to the fact that most jobs in small startups don't provide a budget for you to expand your knowledge.
question
learning
job