Earlier quoted context omitted.
I'll do that for the next one, glad you enjoyed it!
To confuse the issue further, I very much appreciated the format. I've found it much easier to get a better understanding of things like this when it's well-written text instead of slides. Slides that try to stand alone without supporting text (either spoken or written) tend to present a collection of facts without adequately explaining the concepts behind the facts (or the slides contain way too much text).
Abstract algebra for developers and people who hate math
51–56 of 56 posts
Re: Abstract algebra for developers and people who hate math
#52You gotta like math in order to be a cool programmer, otherwise it's like being in a wheelchair.
On the other hand, you can still get into the Olympics in a wheelchair ;)
Re: Abstract algebra for developers and people who hate math
#53Earlier quoted context omitted.
I don't think either of these things will provide a solution that the above is looking for. The problem is with the layout of your content and the fact that write like a math professor. I imagine you scare a lot of people off with a ton of math symbols at the opening, maybe leave that for later, or explain it all in plain English instead of using symbols.
I will try doing that, its just that when I look at math articles, I look for symbols not words :) But, I'll definitely do that in the next one and see what the response is.
Re: Abstract algebra for developers and people who hate math
#54Re: Abstract algebra for developers and people who hate math
#55I didn't do a good job of demonstrating why this might be useful to someone. I'm not sure it is useful, only enjoyable.
Re: Abstract algebra for developers and people who hate math
#56Earlier quoted context omitted.
Sorry, but OOP has virtually nothing to do with abstract algebra. Your whole post is about proving that something belongs to a general class and using the properties of a general class, and making such a vague analogy is completely contrary to that. For a real CS example, see cryptography.
I humbly disagree. Properly-done OOP is all about abstraction and reasoning. You're taking a set of concepts (business concepts, technical concepts, etc) and building a (hopefully) consistent model of how those concepts relate to each other. Included in this model is a deep understanding of the operations that can be performed on the model you've come up with. If you've done a good job about specifying the abstractio…