3 ms·
First of all, let me point out that this: > Most of my work seems to be boring CRUD work where the challenge is gluing libraries together or figuring out busin
by carapace 8y ago
First of all, let me point out that this:
> Most of my work seems to be boring CRUD work where the challenge is gluing libraries together or figuring out business requirements. Actual interesting technical problems seems to be mostly wrapped in ready-made libraries / SaaS services.
...isn't a problem. It's a sign of maturity of the field. In 2018 most problems that you can solve with a computer should have an off-the-shelf library or service. (And most of the job of most working programmers should be mostly selecting and configuring existing solutions according to known design patterns. Like most engineering.)
Second, you've got to take into account that NN/ML/AI et. al. is going to "eat" a portion of all programming work within the next fifteen years or so.
(I think we're due for a contraction of professional programmers, at least as far as the job has been done for decades.)
If you really want to tackle intricate problems you're gonna want to look at biology or nanotech. People in this discussion have already mentioned "matter compilers" and "systems biology".
If you really want to stick to Computer Science problems I would suggest coordination and control of swarm robots. (That's what I'm working on, FWIW.)
- matt2ray 8y ago>Second, you've got to take into account that NN/ML/AI et. al. is going to "eat" a portion of all programming work within the next fifteen years or so. Are there any repos I should look at to learn this? How is this possible when even humans can't read sarcasm online? I'm genuinely blown that this is even possible?!?
- carapace 8y agoRepos, no. But, no coincidence, I have open two relevant tabs right now: "Software 2.0", Andrej Karpathy https://medium.com/@karpathy/software-2-0-a64152b37c35 https://medium.com/@karpathy/software-2-0-a64152b37c35 > It turns out that a large portion of real-world problems have the property that it is significantly easier to collect the data (or more generally, identify a desirable behavior) than to explicitly write the program. "Deep Learning is Eating Software", Pete Warden https://petewarden.com/2017/11/13/deep-learning-is-eating-software/ https://petewarden.com/2017/11/13/deep-learning-is-eating-so... > The pattern is that there’s an existing software project doing data processing using explicit programming logic, and the team charged with maintaining it find they can replace it with a deep-learning-based solution.