3 ms·
Seconded...learning is not a linear-time experience...or, it shouldn't be at least. I didn't learn much during and right after university. But after a few year
by danso 11y ago
Seconded...learning is not a linear-time experience...or, it shouldn't be at least.
I didn't learn much during and right after university. But after a few years on the job as a reporter, I started getting ideas about how to apply my programming experience. One of my first programming-on-the-job experiences was writing a scraper for the local sheriff's website, so I didn't have to manually click through the inmate list.
(this seems to be a common idea among programming journalists; someone wrote a tutorial about it: https://first-web-scraper.readthedocs.org/en/latest/ https://first-web-scraper.readthedocs.org/en/latest/)
To reiterate LoSboccacc's point...with every new thing I wanted to explore, I had many excuses to try out new languages and tools...early on, many of my ideas were dumb (Drupal was my first concept of a website backed with a database)...but after enough misguided, but not crippling efforts, you get much better at being less misguided. And learning new technologies becomes less of a chore :)
- LoSboccacc 11y agoTo expand about university: it's my personal experience so ymmv Almost nothing in my curricula mapped to anything I worked afterward, and I am very glad of that. They forced me to learn how to think, how to solve problem, and gave me a set of analytical tools to understand the software world. True, I had to figure out java and javascript and aLl the other stuff on the gritty nitty details of programming myself, but I learned a lot faster than people attending work skill universities how to not work by coincidence and how to solve the real problem of software development of which coding is actually the very minor part. I'm amazed when I see people lost in coding while that is actually the less relevant part of the job.