4 ms·
Understanding algorithmic complexity was highly useful for me recently when moving a system from inefficient prototype to full-scale version. Complexity theory
by foobarchu 8y ago
Understanding algorithmic complexity was highly useful for me recently when moving a system from inefficient prototype to full-scale version. Complexity theory helped me out with determining the exact pain points in my design and what needed to be altered how (which was most of it). Similarly, graph theory heavily influenced that initial design, which was far more elegant. When moving that system from a single-threaded program that ran on one core into a distributed system running on dozens of VM's with an 'eventually consistent' datastore between them, I tapped into classes on network theory, distributed computing, and operating systems.
Also, during the original design, I tapped into theory of functional programming in coming up with a highly functional architecture (even though the 'functions' are actually abstract processes on a virtual machine).
I'm a big proponent of theoretical CS!
- rs86 8y agoKnowing CS is extremely important. That's the difference between being a modern day factory worker and a high value expert.
- senatorobama 8y agoHow can I demonstrate knowledge of CS in my resume?
- rs86 8y agoI don't know. It shows up easily in interviews or degree
- raarts 8y agoThat's bull. Being an expert does not simply follow from attending a few CS classes and getting a degree. Coming out of college you know very little. The least thing my company can use is overinflated egos.
- WhitneyLand 8y agoI also bristled at the factory worker reference your replied to, as it refers to every relative I have (first one to get a degree). However your reply still isn't logical. 1) A CS degree is a lot more than a few classes of CS, not even counting math and other content. 2) I think when people here are saying "degree" it's really just a short cut for saying "taking some concentrated time to study important theoretical concepts that are useful to know as you go about real life software development". In other words, you could do the same thing without college. It's just harder to juggle multiple things and not have the structured path. Even this is not perfect because it's still unfortunately a resume signal, but that's a separate problem. 3) Coming out of college with little professional or practical experience has nothing to do with the value of leveraging what was learned in college as you go about obtaining that experience. You're company may not want people without practical experience, that doesn't mean they're against having a theoretical grounding also, two separate criteria. 4) This has nothing to do with ego. As I say the previous reference made was an unfortunate choice, but doesn't generalize to all people who take this path.