Live data from Hacker News

Ask HN: Are you working on interesting technical problems?

news.ycombinator.com

321–330 of 441 posts

Re: Ask HN: Are you working on interesting technical problems?

#321
Instead of looking for interesting technical problems, how about looking for interesting business problems. I find far more personal value in solving real problems for people than I do in technical challenges. Also, you're more likely to find more money is present in creating things that offer meaningful business value.

Re: Ask HN: Are you working on interesting technical problems?

#322
Of course not. Neither am I working on a meaningful product. If people could just do the jobs they wanted to do, could you imagine how many cancer researchers, doctors, food distribution chain specialists and so on there would be?

Interesting technical problems are boring compared to meaningful problems - but there's hardly the money to improve society. Instead we get to put together software that shuffles money around or does the same thing as something else with some integration or blows up people in the middle east because that's what makes money.

Re: Ask HN: Are you working on interesting technical problems?

#323

You might as well have asked who among us won the lottery. I've been struggling with this for years now; after 4 boring jobs I finally gave up even the expectation that what I'll be asked to do will be even remotely interesting (or socially useful). The chance of landing an interesting job is absolutely minuscule - the market rewards whatever it rewards at the moment, and that's where jobs flock. These days, one of t…

Eventually everything becomes "just a job." In my mid twenties this was hard for me to grasp. I was working as an electronics design engineer for a company that made low-end industrial controls. We had a customer who had what seemed like the dream company to me: he made robots for animatronics and lab applications. One day I was talking to him about how exciting the work was and his answer surprised me: it used to be…

I wonder if there are some people who are exceptions.

I worked with an software developer at my last job who was incredible. He seemed to have a strong interest for the technology, no matter what technology that was. At the time, it was iOS, and he was an absolute master of iOS. I was constantly impressed by his attention to detail and emphasis on quality, well written, technically challenging code.

I've loosely followed him since, and he seems to be absolutely crushing it wherever he goes. He's spanned many different roles and seems to do enjoy taking on new challenges in the form of different programming languages / platforms.

When I think back to him, I remember someone who seemed to just love programming. In a way, he was like a Robot. It doesn't appear to matter much to him what he's working on, or if it's "fulfilling" in the ethical sense.... He just enjoys the process of coding, and being damn good at it.

Re: Ask HN: Are you working on interesting technical problems?

#324
post #311

Earlier quoted context omitted.

Eventually everything becomes "just a job." In my mid twenties this was hard for me to grasp. I was working as an electronics design engineer for a company that made low-end industrial controls. We had a customer who had what seemed like the dream company to me: he made robots for animatronics and lab applications. One day I was talking to him about how exciting the work was and his answer surprised me: it used to be…

>Why? I've discovered over the years that I am far more excited by making customers happy than by doing technically interesting work. I've come to see the technology as a means to an end, not the end in itself. 100% agree. I'm a Data Scientist and I'm supposed to have one of the most exciting and sexiest jobs in tech. But after many years of doing this I've come to realize that working with good customers and seeing…

I've seen this sentiment many times here on HN. I wonder, who are your customers exactly?

At one of my previous jobs, "my customers" were the managers of some company who asked managers of the company I worked in to deliver some software that will be sold as a part of a software package, to be used by someone downstream. I don't know who ended up using my work and how, because we were isolated by several abstraction layers from that. I did care about the happiness of those people, little I knew about them. But I couldn't care less about the happiness of our customers - a company I didn't hold in high regard, with managers not being particularly helpful. I suppose I did get some small sense of satisfaction when their managers told my managers that the work is good. But that was it.

So, are we talking about happiness of customers, or happiness of people actually using the product? Those are very often different groups. Or, in other words, are we talking about finding happiness in generalized servitude, or making people's lives better?

Re: Ask HN: Are you working on interesting technical problems?

#325
Generally the technical stuff is fairly easy, at least compared to understanding the business requirements!

That said, probably 50% of my job is involved with interesting technical problems, combining cloud scale analytics and machine learning in the engineering sector.

Re: Ask HN: Are you working on interesting technical problems?

#326
I've been in and out of that boat for years. There's something about doing basic work that just drains creative people. I've found some solace in choosing projects that have a social good component associated with them -- CRUD that feels good. I think a big part of personal happiness is learning to shift your source of joy from actions to outcomes they lead to.

I'm also working on an open source programming assistant to help automate that kind of joyless work so developers can focus on the novel parts of their projects. Hoping it helps people like you get back to what you value. https://github.com/opticdev

Re: Ask HN: Are you working on interesting technical problems?

#327
post #311

Earlier quoted context omitted.

>Why? I've discovered over the years that I am far more excited by making customers happy than by doing technically interesting work. I've come to see the technology as a means to an end, not the end in itself. 100% agree. I'm a Data Scientist and I'm supposed to have one of the most exciting and sexiest jobs in tech. But after many years of doing this I've come to realize that working with good customers and seeing…

I've seen this sentiment many times here on HN. I wonder, who are your customers exactly? At one of my previous jobs, "my customers" were the managers of some company who asked managers of the company I worked in to deliver some software that will be sold as a part of a software package, to be used by someone downstream. I don't know who ended up using my work and how, because we were isolated by several abstraction…

Personally I work in the health tech space - specifically a pharmacy. Our customers are people who are able to get cheaper medications and better health help and pharmacy technicians who are more productive due to our software. The job is technically just Django/CRUD with some integrations, but the impact can be fulfilling.

I don't think you can get that kind of satisfaction in B2B software as a developer (only a salesperson/exec).

Re: Ask HN: Are you working on interesting technical problems?

#328
At my job? Nope. And I'm totally okay with that. I've worked on interesting technical problems in the past, and I've worked at companies with a huge social impact. I'm pretty have those behind me. Those things will eat me alive every time.

It's not that I don't care about my current job or that I don't do it well. It just doesn't involve anything even remotely interesting technically or socially. I work for a company that makes money. That's it. And I'm quite happy with that. I show up in the morning, do my job, and go home.

I don't have a wife or a family, but I do have me to take care of. And after years of neglecting myself physically and mentally, I'm taking the time to get some balance in my life. Get some exercise, spend more time with relatives and friends, more time with my girlfriend, and develop some of my own pet projects (both technical and musical) that I've been putting off for a long time.

You don't need an excuse to have a boring job that leaves you with extra time on your hands. It doesn't have to be because of a wife or husband or kids or a sick parent or anything. Taking care of yourself is a good enough reason to pull over into a slower lane or enjoy the one you're in now.

Most people are not really doing anything that interesting in the technology world. Many people who think they are doing interesting things are just hyped. The vast majority of the world's problems that can be solved by tech, have been solved. The only thing that's left is to implement them, and that's not super exciting a lot of the time.

If you feel the need to do more, you're going to find that need best met on your own or with a small group of friends working on projects. Most likely not at work.

Re: Ask HN: Are you working on interesting technical problems?

#329

My suggestion : forget you CS degree, drop the idea of doing something interesting during your work hours, think about it as inevitable procedure to earn your montly salary. At 5pm run away from your office and focus on whatever you think is interesting.

Is this view that common? I'm all for work-life balance and working on passion projects on the side. But do that many people really think of their developer job as a salary and a daily grind?

For me it doesn’t seem a daily grind. When I am actually writing software, I completely love it, even after 14 years of doing it professionally full time (and several years part time during uni). The only parts that I never liked were the bureaucratic bullshit, production support even at insane hours of the day, and the politics with your colleagues. Usually those were a relatively small part (20-40%) of the total and I still could enjoy writing good software the rest of the time. Now finally contracting I’m in a position were my coding skills are really appreciated and I enjoy my time coding and helping my colleagues without all the bullshit. Maybe I don’t score high in the interesting jobs lottery, but I’m perfectly happy of the pretty good amount of money that I get doing something that I love in old, boring, huge companies.

Re: Ask HN: Are you working on interesting technical problems?

#330
post #311

Earlier quoted context omitted.

>Why? I've discovered over the years that I am far more excited by making customers happy than by doing technically interesting work. I've come to see the technology as a means to an end, not the end in itself. 100% agree. I'm a Data Scientist and I'm supposed to have one of the most exciting and sexiest jobs in tech. But after many years of doing this I've come to realize that working with good customers and seeing…

I've seen this sentiment many times here on HN. I wonder, who are your customers exactly? At one of my previous jobs, "my customers" were the managers of some company who asked managers of the company I worked in to deliver some software that will be sold as a part of a software package, to be used by someone downstream. I don't know who ended up using my work and how, because we were isolated by several abstraction…

I was referring to people who were actually using the product. I've had a number of jobs in my life, including being in the services division of a product company and also in an internal consulting team of an extremely large non-tech company. I would typically interact directly with the people who are using what we were building. So I could see exactly what they needed and did not need (despite what they said they wanted) and manage that so they were happy with the end product.

I've also worked in situations you've described. My only interaction with the end user is through layers of middle management. I found that environment to be extremely demotivating and certainly no direct sense of satisfaction. One of the small benefits of being a Data Scientist right now is that a lot of managers don't really understand what it is I do so I get some interaction with the end-user from a requirements and solution validation standpoint. But I suspect in a few years Data Scientists will become invisible cogs (like everybody else) in the Enterprise IT machine.

Post reply on HN