If it has nothing to do with a way to increase production, then the company has no business by investing in you learning that. BUT, if the company can benefit from you learning those skills, then it could be a missed oportunity not give you the resources to do it (learning it while on the company's time). Of course it's all a product of culture and supply-demand (systemic), if there are enough great programmers that…
Your Progress As A Programmer Is All Up To You
31–40 of 69 posts
Re: Your Progress As A Programmer Is All Up To You
#32Terrific post. This is exactly the type of individual I want to work with - someone who recognizes that they're in charge of their own advancement, and doesn't lay blame on any outside factors. As developers/builders/hackers we are ultimately responsible for our own success or failure.
i disagree somewhat. the article was a bit heavy on the narcissism, i wouldn't want to work with such a person. i'd rather work with the Brazil-esque Robert DeNiro type: "Listen, kid, we're all in it together."
Re: Your Progress As A Programmer Is All Up To You
#33Re: Your Progress As A Programmer Is All Up To You
#34Earlier quoted context omitted.
No, they are interested, learning is fun for them too. But not everyone is interested in learning the same things you are. For me, for example, there is absolutely nothing more boring, than some new fancy framework, API or a language. I am, however, very excited to try things that might reduce amount of bugs and potential security issues in my code, make it cheaper to run, cheaper to support.
So long as you don't have to learn a language, API, or framework to do it... I'm not sure what things are left you could do differently? Your list excludes all technology-related changes, so the rest becomes meta-activities: pair programming, documentation, planning, a good nights sleep, etc. Those are excellent, but I'm curious why are you willing to change those other areas but are resistant to technological ones?…
Re: Your Progress As A Programmer Is All Up To You
#35Earlier quoted context omitted.
some people feel that their lives do not revolve around programming, that there are other interesting things like traveling and child raising that take a chunk of their ever precious and limited time. so it's not to say they aren't interested, but rather lack the time to dedicate. therefore, it helps if the company they work for can offer a little time to learn new things.
I'm talking about developers who when offered a chance to learn something new at work reject it, usually while getting pretty defensive. My current hypothesis is people get so used to internally defending their neglect of the skills that earn them travel and shelter that when the opportunity arises to actually get paid to improve, all the reasons they normally use prevent them from even doing that.
Re: Your Progress As A Programmer Is All Up To You
#36I think ultimately, many people in the industry, they only get to learn new tech when they leave for their next job. The pressure is momentarily reduced while they learn at their new job.
Just my 2 cents.
Re: Your Progress As A Programmer Is All Up To You
#37I have been writing and rewriting a post for the better part of a year on this same thing. I think I've finally accepted that a majority of programmers actually are not interested in learning new things. I got into software because there was so much to learn and explore, so this realization still baffles me. Why on earth would someone want to do this job and not want to learn new things? It's like a baseball player w…
I am baffled by him. After spending two years with him, I still can't understand his motivations. I quit that job in large parts because of him.
Re: Your Progress As A Programmer Is All Up To You
#38Earlier quoted context omitted.
So long as you don't have to learn a language, API, or framework to do it... I'm not sure what things are left you could do differently? Your list excludes all technology-related changes, so the rest becomes meta-activities: pair programming, documentation, planning, a good nights sleep, etc. Those are excellent, but I'm curious why are you willing to change those other areas but are resistant to technological ones?…
Let's see, I'm learning about unscented Kalman filters, moving object tracking in computer vision, PCA, and more. I'm learning about the problem domain that I'm working in. I have no interest in learning yet another API unless I absolutely have to, because it isn't really interesting knowledge that I have to call the fibble() function before calling xacxtyor() in this poorly documented API. That's not learning, it's…
Also, if you like math go learn some functional programming. The ideas of abstract algebra, which you will encounter in FP, are increasingly relevant to machine learning as well. E.g. http://jmlr.org/proceedings/papers/v28/izbicki13.pdf
Re: Your Progress As A Programmer Is All Up To You
#39I have been writing and rewriting a post for the better part of a year on this same thing. I think I've finally accepted that a majority of programmers actually are not interested in learning new things. I got into software because there was so much to learn and explore, so this realization still baffles me. Why on earth would someone want to do this job and not want to learn new things? It's like a baseball player w…
No, they are interested, learning is fun for them too. But not everyone is interested in learning the same things you are. For me, for example, there is absolutely nothing more boring, than some new fancy framework, API or a language. I am, however, very excited to try things that might reduce amount of bugs and potential security issues in my code, make it cheaper to run, cheaper to support.
Re: Your Progress As A Programmer Is All Up To You
#40Earlier quoted context omitted.
So long as you don't have to learn a language, API, or framework to do it... I'm not sure what things are left you could do differently? Your list excludes all technology-related changes, so the rest becomes meta-activities: pair programming, documentation, planning, a good nights sleep, etc. Those are excellent, but I'm curious why are you willing to change those other areas but are resistant to technological ones?…
Let's see, I'm learning about unscented Kalman filters, moving object tracking in computer vision, PCA, and more. I'm learning about the problem domain that I'm working in. I have no interest in learning yet another API unless I absolutely have to, because it isn't really interesting knowledge that I have to call the fibble() function before calling xacxtyor() in this poorly documented API. That's not learning, it's…
i hear you on that one
> and I do everything I can to isolate myself from that.
but still, you can't stop thinking about design entirely. when a new ideally-pure-C-but-C++-if-you-really-need-stl library is ready to actually be put to use you'll have to put an api of some sort on it. hopefully that api will be informed by your use of other people's apis, both good and bad.
don't forget that the whole point of computers is that they're immediately useful. you can still do most of the math you want with a pencil, paper, and stack of books.