6

One of the most annoying things I find about being in the field of Computer Science: you have to read thick book after thick book, just to stay ahead or on par with technology.

Oh, technology x came out. New item appears in to-do storyboard: "read book x". Oh, only 900 pages huh? Oh, deadline this week huh? There goes my weekend.
What's this? After having read book x, now I have to read book y and also read about design patterns again?

Sigh.

Comments
  • 7
    Book? What is that? xD
  • 1
    Why bother.. Better enjoy your life
  • 1
    @netikras I have to maintain my job. I can't just say: oh, I'm not going to study a new framework customers are paying for.
  • 0
    @CaptainRant selling other vendors' frameworks? That must be a hugging exhausting job. And a weird sounding one ofc :)

    I didn't think it's a part of your job. Sry
  • 0
    @PublicByte Not know, they want to use them. I'm developing with those technologies.
  • 3
    @netikras It's quite normal for a consultant to constantly have to study new frameworks and technologies because he needs to be marketable to the new clients that he's going to work for.
  • 4
    Aren’t 9 out of 10 new things irrelevant within a year‘s time? If it is still relevant after that it might be worth learning, otherwise safely skip it.
  • 0
    @sawmurai In this case, the technology will be used for probably years to come.
  • 0
    You need to put effort into it, which is true for pretty much any field.
  • 0
    @RememberMe People in other fields don't need to go home and spend their evenings reading books about their work. They just don't.
  • 0
    @CaptainRant Well, in medical fields, they do, but I digress.
  • 0
    @CaptainRant it's true for pretty much every technical field or place where there's some advancement going on.
  • 0
    @RememberMe Yeah, I was referring to hard labor and factory jobs, cleaning jobs, etc. Those exist too.
  • 1
    Never red a coding book in my life.
    Whenever there is a new language i create a software out of it and debug it (since it wont work from the first time) and google errors and end up materise it.
    It may take few days or 2 weeks, but in the end i get to get the "how it works" and the syntax.
    Deep down, all of them function the same way.
  • 0
    I will admit I enjoy reading programming books but you don’t need to read the books to keep up. Read a blog post, watch a tutorial, read some documentation and play around. Books are helpful and can give excellent insights but going through thicc books isn’t the only effective method to keep up
  • 1
    I've spent so much time on a book that by the end of it I needed a newer book haha!!! Love having that library though, it's like trophies
  • 0
    @Bubbles Truly successful people (like a Neurologist I used to date) will tell you that a mere idea of something isn't enough for the brain to successfully process things. You need the whole picture.

    It's the same reason why back at university I needed to use all senses and resources: watching, listening, writing, hearing, video, tutorials, books, fundamentals, everything. It's not normal for a person to fully grasp something by having minimal information. Sure, you can do inference, but no.
Add Comment