News for hackers. Stuff that matters.
Re:How I learned to program by clifanatic on Monday September 12, 2016 @03:45PM (#12483016)
> no one’s going to stop you from spending time reading at work or spending time learning

What? You've lived a truly blessed life, Dan Luu. I've observed the opposite, pretty consistently. I've been working as a programmer for 25 years and I've found, across nine separate employers (and lost-track-of-how-many different supervisors) that spending any appreciable time reading (even a book about Angular when you're supposed to be learning Angular) will become a management issue. Everywhere I've ever worked has expected learning to be on your own time. Don't believe me? Put "read three chapters of a book" on a status report and see how many levels of management show up at your desk to micromanage your time.

Re:How I learned to program by Casseres on Monday September 12, 2016 @03:55PM (#12483108)
> Put "read three chapters of a book" on a status report and see how many levels of management show up at your desk to micromanage your time.

Try something like "reviewed industry publications for new paradigms and optimization techniques."

Re:How I learned to program by clifanatic on Monday September 12, 2016 @04:31PM (#12483370)
Yep, that's pretty much how I spin it. But make no mistake, I have to "spin" the fact that I'm reading about programming while working as a programmer.
Re:How I learned to program by vogt on Monday September 12, 2016 @03:50PM (#12483059)
Weird. I have found this to basically never be the case. Even some of the worst managers I've had have supported learning on the clock, through reading materials, tutorials, or otherwise. I've even had some jobs where learning time was a regularly slated part of my work week, and in some cases was allowed to take classes which cut into work a bit. My current employer has a library of technical books and educational material that any of us are free to rent and learn as we go.
Re:How I learned to program by lfowles on Monday September 12, 2016 @05:19PM (#12483781)
Sounds nice. I brought up the concern that learning on the job was frowned upon and was told "that is just keeping yourself marketable, you do that on your own time".
Re:How I learned to program by Ensorceled on Monday September 12, 2016 @06:16PM (#12484133)
Not sure why you're being down voted since places like this exist ... I know because I've worked at them.
Re:How I learned to program by lfowles on Monday September 12, 2016 @07:02PM (#12484372)
OT: How are you able to tell I'm being downvoted?
Re:How I learned to program by treehau5_ on Monday September 12, 2016 @07:12PM (#12484418)
It appears faded to other people
Re:How I learned to program by vogt on Monday September 12, 2016 @10:59PM (#12485358)
Bummer. I know that reality exists, it's just unfortunate. I wouldn't want to work for anyone who had that attitude if I had the option.
Re:How I learned to program by lfowles on Tuesday September 13, 2016 @02:13PM (#12490835)
I have a love hate relationship with the place, it's rarely black and white. I get to work on really cool projects and stay in an incredibly low cost of living area.... but the internet access is awful and I don't get much time to improve myself.
Re:How I learned to program by khedoros on Monday September 12, 2016 @04:26PM (#12483323)
A standing directive that I've got is "get your work done; other than that, I don't care how you spend your time". I regularly put something like "researched current code-signing best practice" into my status reports (and have for the past 8 years, when appropriate).

My time at home is mine. If I'm reading a technology book, it's usually something I'm curious about and don't have a direct use for in my professional life.

Re:How I learned to program by alasano on Monday September 12, 2016 @05:15PM (#12483750)
I'll consider myself very lucky then. At my firm we're strongly encouraged to take 4 hours per week to dedicate to learning something new or bettering our existing skill set. You simply let your team lead know your current objectives for the month and we're given access to pluralsight/codeschool etc. I honestly didn't know how much fun work could be while still being work until I started here.
Re:How I learned to program by brtt on Monday September 12, 2016 @03:56PM (#12483121)
Does the same hold true if you put replace "read three..." with "research"? Perhaps it's specific to my industry (data), but I spend a considerable amount of time reading about new techniques and approaches to make our codestack more efficient.
Re:How I learned to program by overcast on Monday September 12, 2016 @05:46PM (#12483966)
That's not my experience at least in a "DevOps" role. In fact a large portion of our time is spent reading/learning documentation, and random websites. Getting punished for learning on the job, would immediately lead to me looking for a new job.
Re:How I learned to program by GrumpyYoungMan on Monday September 12, 2016 @04:17PM (#12483273)
>Put "read three chapters of a book" on a status report and see how many levels of management show up at your desk to micromanage your time.

Can't say I've ever had a problem with that in my two decades in the industry. Learning is expected and mandatory.

Re:How I learned to program by jtrtoo on Friday September 16, 2016 @12:09AM (#12511759)
Awesome handle!
Re:How I learned to program by bigtunacan on Monday September 12, 2016 @08:13PM (#12484783)
I'm quite surprised by this since most programming jobs will involve solving problems you don't know how to solve on a regular basis. Reading, whether it's books, blogs, Stack Overflow are ways to help you solve problems.

If you are a JavaScript programmer and spend the work day reading about Elixir; that is a problem. It likely doesn't apply to work so that should be on your own time.

Re:How I learned to program by clifanatic on Tuesday September 13, 2016 @09:53AM (#12488203)
> since most programming jobs will involve solving problems you don't know how to solve on a regular basis

Yes, you'd think that would be blindingly, painfully obvious to anybody with the cognitive ability to tie their own shoe laces. And it probably is, to everybody except the MBA "efficiency experts" that are taking over my profession.

Re:How I learned to program by lostboys67 on Tuesday September 13, 2016 @05:23AM (#12486598)
You must have bad luck with employers I don't recall this being an issue at my employers.

At my first job (from high school) my first instruction was "go to company library get the book on fortran and learn it".

Re:How I learned to program by clifanatic on Tuesday September 13, 2016 @09:51AM (#12488184)
I guess. Nine in a row.
Re:How I learned to program by MaulingMonkey on Tuesday September 13, 2016 @02:13PM (#12490842)
Places I've worked have had their own mini-libraries. I have some kind of documentation loaded up on at least one of my monitors at pretty much all times.

I don't spend significant amounts of time doing nothing but research however. The problem might not be "read three chapters of a book" on a status report, it might be having only that on a status report.