4 ms·
> I am equally suspicious of those excited by hard computing problems. Debugging memory leaks is a hard problem. Deducing the cause of periodic load spikes on e
by dpark 15y ago
> I am equally suspicious of those excited by hard computing problems. Debugging memory leaks is a hard problem. Deducing the cause of periodic load spikes on ec2 instances in the middle of the night is a hard problem. I must admit, however, that these tasks does not excite me.
Those are not hard computing problems. They're just hard problems. Solving hard computing problems involves developing new algorithms and heuristics, building elegant solutions to complex issues, working around hard constraints, optimizing for massive scale, etc. Creating a system that quickly sorts and ranks flights by different criteria could be a hard computing problem. Figuring out why that system crashes on Tuesday mornings at 2:37am is just a hard problem.
Very little of what most software engineers do on a daily basis is actually about solving hard computing problems. It's mostly just work, which is why we get paid. The hard computing problems are generally fun. The rest is what earns a living.
- awt 15y agoYou are right. It is exciting to solve those problems. I wish I had more opportunities to do that.
- eternalban 15y agoPretty much agree with you. I would classify between tedious and hard (where both would take the same amount of effort). Beyond that, some borderline tedious/hard problems can be fun (and you can/will get paid for it.) For example, I've to date spent untold hours of my own time trying to squeeze as much performance as possible from a concurrent pipelined noSQL driver. The tedious part is the trial and error of trying n different variations, running effective benchmarks, etc. The thrill :) is in seeing throughput increase 3 fold. It is a rush.