I found something that didn't feel like work, turned it into my career, and then realized that when there are real business outcomes riding on it, suddenly it feels like work. To the point that I now don't even like doing it as a hobby.
What Doesn't Seem Like Work?
51–60 of 332 posts
Re: What Doesn't Seem Like Work?
#52Creating useful things, or something that is fun to do.
Making something come to life, a product, a character, a moment, that people use or enjoy experiencing.
It could be in programming, art, a system, a product, something digital, something physical, anything useful that removes part of the monotony of life, reduces drag, and improves the thrust of life.
To me a comic strip, a rocket ship, a new game, a system that takes away boring tedious parts of life, quality of life improvements, and anything helpful to make the day more of an adventure, are all on the same plane.
Re: What Doesn't Seem Like Work?
#53This excerpt - "what he really liked was solving problems. The text of each chapter was just some advice about solving them. He said that as soon as he got a new textbook he'd immediately work out all the problems—to the slight annoyance of his teacher, since the class was supposed to work through the book gradually." is literally me. I did that. Every year at my school I did exactly that. Once I actually turned in m…
As (failed) physics major, it sounds so strange to hear someone claim to be good at math but not physics. To me physics is 98% math. It's a few empirical facts from experiments and then bucketloads of math.
Re: What Doesn't Seem Like Work?
#54Is it common for programmers to dislike debugging? I'm stunned. I never considered the possibility, it's always been something I enjoyed. I don't believe it impacts you either way in terms of capability but I imagine it impacts your desire to continue.
If you are working on support/maintenance roles (in engineering) at big enterprise product company then debugging is major part of your job. I enjoy debugging as it is another way to solve problem. But for some people it gets repetitive (and boring) since you have to do that day in day out as a part of support roles.
Bad management -> bad design decision and poor resource allocation -> blame those lower on the org chart than you -> pressure to "just get this fixed and out the door" -> high levels of technical debt and programmer "burn-out"
Re: What Doesn't Seem Like Work?
#55Some programmers are engineers: they deal with the world as it is -- messy, inconsistent, evolved. They are good at debugging, because they are in tune with how things actually work (not how people SAY they work.) They like trying things before reading about them.
Some programmers are philosophers and mathematicians: they like to consider things from first principles, read a lot, and build up systems in their head. They make huge breakthroughs because they question fundamental assumptions. But sometimes they over-model things and ignore how the world actually works, in favor of "elegant" ideas. They may not like debugging because it is often dealing with other people's broken assumptions (i.e. legacy code), and not any real fundamental idea.
So PG clearly seems to have the philosophical bent and has made breakthroughs. But if he really likes debugging, then that means he comes at programming from BOTH the engineering and philosophical traditions, which probably explains why he's a great programmer. (I just stumbled across a copy of ANSI Common Lisp at work -- looking forward to seeing his style more closely.)
I think to be really good at something, you have to understand it in two different ways. Same goes for being able to write code from scratch (maker perspective) and being able to hack into it (breaker perspective).
Although, I have to say, there is a big difference between debugging your OWN code and other people's code. Not sure if anyone likes debugging typical enterprise code. :)
Re: What Doesn't Seem Like Work?
#56This excerpt - "what he really liked was solving problems. The text of each chapter was just some advice about solving them. He said that as soon as he got a new textbook he'd immediately work out all the problems—to the slight annoyance of his teacher, since the class was supposed to work through the book gradually." is literally me. I did that. Every year at my school I did exactly that. Once I actually turned in m…
As (failed) physics major, it sounds so strange to hear someone claim to be good at math but not physics. To me physics is 98% math. It's a few empirical facts from experiments and then bucketloads of math.
Re: What Doesn't Seem Like Work?
#57Is it common for programmers to dislike debugging? I'm stunned. I never considered the possibility, it's always been something I enjoyed. I don't believe it impacts you either way in terms of capability but I imagine it impacts your desire to continue.
Re: What Doesn't Seem Like Work?
#58This excerpt - "what he really liked was solving problems. The text of each chapter was just some advice about solving them. He said that as soon as he got a new textbook he'd immediately work out all the problems—to the slight annoyance of his teacher, since the class was supposed to work through the book gradually." is literally me. I did that. Every year at my school I did exactly that. Once I actually turned in m…
As (failed) physics major, it sounds so strange to hear someone claim to be good at math but not physics. To me physics is 98% math. It's a few empirical facts from experiments and then bucketloads of math.
it wasn't enough to tell her "well it still gives us the valid results" - she had to be able to interpret every portion of an expression and then make intuitive sense of it.
at first i was annoyed with this habit of hers, but eventually i started doing it to. for a lot of really math-minded people, hand waviness is anathema, and physics was full of "2 + 2 = 5 for sufficiently large values of 2, so we'll just assume that to make things easier"
Re: What Doesn't Seem Like Work?
#59Is it common for programmers to dislike debugging? I'm stunned. I never considered the possibility, it's always been something I enjoyed. I don't believe it impacts you either way in terms of capability but I imagine it impacts your desire to continue.
On a couple of teams I fell into the role of "team debugger", helping everyone with whatever was broken, and those have been my happiest times.
Re: What Doesn't Seem Like Work?
#60What if you don't have anything like this?