Live data from Hacker News

What is the hardest thing in Computer Science?

news.ycombinator.com

31–40 of 42 posts

Re: What is the hardest thing in Computer Science?

#32

Earlier quoted context omitted.

Umm..what about Compilers and their implementation? Isn't it hard? PS: I find them the hardest.

compilers do a known thing. security means protecting against unknown things.

I get your point. Seconded.

Re: What is the hardest thing in Computer Science?

#37

Complexity

I'd like to hear some reasoning behind that. Maybe more adjectives? IMHO Complexity, in general, is good. Nature conserves it when its adaptive.

I don't mean to sound flippant but there actually seems to be lots of different hard problems in computer science, or computing (to be honest I'm not sure which we're talking about here) but all of the ones that I know of are hard due to complexity. Our science is good at reductionism, finding fundamentals, but when it comes to complex systems it simply informs our inadequate simulations. So I think the hardest problems in computer science will exist where we try and apply it in the real world to complex machines. In computing there are many hard things to make, databases, operating systems, programming languages, the list goes on - and they are hard because they are big and complicated and so making them is hard because to some extent it doesn't matter how much resource or intelligence you have because the problems that arise in complex systems start to get chaotic and intractable.

Re: What is the hardest thing in Computer Science?

#38

Making your code so simple (and well documented!) that it can be understood by programmers with much less experience than you, while not compromising speed or functionality. “Everything should be made as simple as possible, but no simpler.” -Albert Einstein

This is the one I strive for. Making a challenging thing self-evident and appear like it wasn't that much work, even when it was an explosion of code later distilled.

Re: What is the hardest thing in Computer Science?

#40
The hardest thing is to accept that you don't really need CS as a software developer. Even programming tasks - digging into legacy code, implementing features etc. - requires no CS knowledge, and programming is just one thing sw devs do.

Other words: there's no CS topic which helps you during an estimation meeting.

Post reply on HN