Pretty much everyone is in the same boat. Even if you have an advanced degree, most of what businesses need is plugging together components and adding business rules to create a product. As a discipline, we're too young and our technology is too immature to support a true split between engineering/science and computer programming. If you want to work on interesting problems you're passionate about, there's a few ways…
Ask HN: Are you working on interesting technical problems?
141–150 of 441 posts
Re: Ask HN: Are you working on interesting technical problems?
#142I stay away from webdev. I did a couple of small projects but the web was just an outer API, the main work was done by native code running on CPUs or GPUs.
I stay away from enterprise systems, or fin.tech, or ad.tech. I removed enterprise-targeted keywords from my resume, Java, J2EE, SOAP, SQL. I have some experience with them from my early career but I don’t want to use them anymore.
Also, for many years I’ve never worked in/for huge companies, i.e. google/amazon/microsoft scale. My employers/clients are/were mostly small to medium companies.
What do I do? Almost everything else. Native desktop, native mobile, embedded, GPGPU, robotics, GIS, videogames, CAD/CAM, streaming media. Many startups, and small to medium companies, have problems to solve that I find interesting to work on.
There’re still boring parts in my work. But because of my experience I usually find ways to minimize the time I’m spending on them. The most generic advice, pick the right tools.
Re: Ask HN: Are you working on interesting technical problems?
#143I have been able to invent my own projects along the way, such as mp3 to subtitles and a student portal for the college side of the charity. It's been really fun. However without writing a crud page for some new idea that someone has once a week I dont think I'd still be here.
Re: Ask HN: Are you working on interesting technical problems?
#144Earlier quoted context omitted.
You have found the boundaries of the box, and anything you find outside the box will be judged against everything inside the box. There are a lot of people inside the box, and the box is small, so they make a lot of noise. When you get outside of the box you need to also get away from the box so that you can't hear the judging.
Interestingly put. Sounds poetic. So here I am, with the map of the boundaries of the box finally taking shape. Now the question is, how do I exit the box? I'd like to walk around on the outside and check it out. Also, is leaving this box even a good idea? What if everyone left the box at the same time? Would the world collapse then? (I can't help myself, I tend to be interested in the global view as well.)
It's a very nice idea.
It does have the potential to create localized unimpressedness though; the question is how powerful the temporarily-put-out groups would be, and whether the backlash would remove your power as well.
Money is power, laterally too.
Re: Ask HN: Are you working on interesting technical problems?
#145You 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…
Boring problems are quite manageable when they are also important and meaningful. The general lack of purpose most of us find in our jobs (apart from 'earning money') is the real problem.
Re: Ask HN: Are you working on interesting technical problems?
#146My 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?
Re: Ask HN: Are you working on interesting technical problems?
#147If you're really looking for interesting technical problems, I highly recommend looking into systems biology. There's interesting mathematical, computational, and biological problems being worked on here (with lots of funding!).
Re: Ask HN: Are you working on interesting technical problems?
#148The roles were for more CRUD-related gigs. I don't really get the emphasis on those CS particulars when you don't really run into them much.
Anyway, no my job is not interesting. The challenges are organizational and political rather than technical.
Re: Ask HN: Are you working on interesting technical problems?
#149I generally like what I do. I stay away from webdev. I did a couple of small projects but the web was just an outer API, the main work was done by native code running on CPUs or GPUs. I stay away from enterprise systems, or fin.tech, or ad.tech. I removed enterprise-targeted keywords from my resume, Java, J2EE, SOAP, SQL. I have some experience with them from my early career but I don’t want to use them anymore. Also…
I also like to abstract away the non-sense part of a problem, so that I can focus on the real intellectual puzzles.
Re: Ask HN: Are you working on interesting technical problems?
#150Earlier quoted context omitted.
While I don't agree with Marx, your sense of ennui seems to reasonably represent what I understand to have been his concepts of reification and alienation. One might ask: what does the alternative look like? From what I can tell Marx is a bit wishy-washy on that point. Hayek more helpfully explained that the market provides a mechanism for determining value, not virtue . That it works, but doesn't uplift. And that tr…
> the market provides a mechanism for determining value The market's notion of value is weighted by wealth: making coffee for the rich is "valuable", meeting the basic needs of the poor is not "valuable." This makes the market notion of "value" very different from just about any other notion of value in the world. If you muddy the distinction, or let someone else muddy the distinction, markets become almost tautologi…
Hayek understood that what we think about prices and what we think about ethics are distinct things. He didn't see rightness as flowing from markets. He saw it as a discovery process for allocations of resources.