4 ms·
> The problem is that it's the wrong topic for somebody who does software development! For somebody building the next CRUD app, perhaps. In my line of work (E
by groovy2shoes 10y ago
> The problem is that it's the wrong topic for somebody who does software development!
For somebody building the next CRUD app, perhaps. In my line of work (EDA software), I routinely apply concepts from my computation science education on the job and in my code. Algorithms, data structures, discrete mathematics, graph theory, set theory, type theory, universal algebra, tractability theory, automata theory — these are all topics where knowledge has come in handy in my professional experience at various jobs.
Of course, concepts from other fields — biology, linguistics, and physics, for example — have also come in handy on occasion. I almost feel like there's no such thing as a "wrong topic for somebody who does software development", though some topics are certainly more relevant/useful than others.
- oblio 10y agoWell, then you're most likely part of minority. And even in that minority I'm willing to bet that a lot of the time is spent in things that have little to do with Computer Science. Be honest and think of all the time you've spent fiddling with build systems, various random tools (compilers, scripts, databases, version control, etc.).
- groovy2shoes 10y agoFar too often, to be sure. Two things I have yet to encounter in my (admittedly short, so far) professional career are a sane build system and version control that isn't a PITA...
- stonemetal 10y ago>I routinely apply concepts from ... theory Sounds exactly like what I would expect an Engineer to do. Apply theory to the real world. Versus a scientist who I would expect to develop, test, and prove new theories.
- csours 10y agoIf you are building programming languages, compilers, tools, etc, Comp Sci is certainly pertinent. If you aren't building programming tools, you can get away with a minimal Comp Sci background.