5 ms·

Lol, you think you are spending 40 hours a week at the forefront of problem solving new challenges? Let's be real, for a moment. By your definition of a hard e

Lol, you think you are spending 40 hours a week at the forefront of problem solving new challenges? Let's be real, for a moment. By your definition of a hard engineering problem, very few people are spending their time doing it. Virtually no one is doing it every day. Why pick on front end dev specifically? You think the average backend dev building installing flask is facing a lot of unsolved problems? You think the average game dev is rendering 3D models in some new, magical way?

EpicEng 10y ago
So, I didn't want to say what I do because I didn't want to make it personal, but yes, I do. I work in biotech and desogn control systems for an immunofluorescent imaging device and associated computer vision algorithms used to identify circulating tumor cells in the blood stream. We just released a prognostic test for colon cancer which is actually relatively groundbreaking as it provides a new treatment path for people who previously had no options. So yes, I feel that I am. I have been a part of small engineering teams delivering brand new technologies to the market my entire career. And you're right, very few people, especially in software, are solving hard problems. I wasn't picking on anyone, I was responding to a comment.
- randomdata 10y ago
  Stringing together some OpenCV functions isn't hard engineering.
- jhall1468 10y ago
  So you are using a fluorescent fiberscope to identify tumors. So you are implementing some vision library. How is that a hard engineering problem? > So yes, I feel that I am. That's the crux of the issue. You are doing exactly what you find so distasteful about web development: implementing existing algorithms to solve a specific problem. Unless of course, your team is actually inventing new vision algorithms that somehow changed the field, which I'd love to see the paper on.

EpicEng 10y ago

So, I didn't want to say what I do because I didn't want to make it personal, but yes, I do. I work in biotech and desogn control systems for an immunofluorescent imaging device and associated computer vision algorithms used to identify circulating tumor cells in the blood stream. We just released a prognostic test for colon cancer which is actually relatively groundbreaking as it provides a new treatment path for people who previously had no options. So yes, I feel that I am. I have been a part of small engineering teams delivering brand new technologies to the market my entire career. And you're right, very few people, especially in software, are solving hard problems. I wasn't picking on anyone, I was responding to a comment.

randomdata 10y ago
Stringing together some OpenCV functions isn't hard engineering.
jhall1468 10y ago
So you are using a fluorescent fiberscope to identify tumors. So you are implementing some vision library. How is that a hard engineering problem? > So yes, I feel that I am. That's the crux of the issue. You are doing exactly what you find so distasteful about web development: implementing existing algorithms to solve a specific problem. Unless of course, your team is actually inventing new vision algorithms that somehow changed the field, which I'd love to see the paper on.