├── brand.png ├── brand.svg └── readme.md /brand.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/learning-gardens/_emulating_intelligence/baaac610e08fae3382d37ba8cf4ddb70d5a95558/brand.png -------------------------------------------------------------------------------- /brand.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 14 | 16 | 18 | 19 | 21 | image/svg+xml 22 | 24 | 25 | 26 | 27 | 28 | 31 | 35 | 39 | 43 | 47 | 51 | 55 | 59 | 63 | 67 | 71 | 75 | 79 | 83 | 87 | 91 | 95 | 99 | 103 | 107 | 111 | 115 | 119 | 120 | 124 | 128 | 132 | 136 | 140 | 144 | 148 | 149 | 153 | 157 | 161 | 165 | 169 | 173 | 174 | 178 | 182 | 186 | 190 | 194 | 198 | 199 | 203 | 207 | 211 | 215 | 219 | 223 | 224 | 228 | 232 | 236 | 240 | 244 | 248 | 249 | 253 | 257 | 261 | 265 | 269 | 273 | 274 | 278 | 282 | 286 | 290 | 294 | 298 | 299 | 303 | 307 | 308 | 309 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | ![Emulating Intelligence](brand.png) 2 | 3 | # Emulating Intelligence 4 | 5 | A machine learning and artificial intelligence learning group 6 | 7 | ## Overview 8 | 9 | This is mostly a placeholder at the moment, but I think this learning group could be structured around five threads: 10 | 11 | - the practical: how to build software using AI/ML 12 | - the theory: the underlying concepts that power the algorithms 13 | - the social: the possible or present impacts of the deployment of AI systems 14 | - the philosophical: if desired we can also talk about implications AI has for the place of humans, consciousness, etc 15 | - the integration: how experiences/interactions with AI are designed 16 | 17 | I think that covers it? 18 | 19 | ## Structure 20 | 21 | The "practical" thread might be tricky to pull of since it would require a several hours together (if it's structured as workshops). Another possible arrangement is we all agree to e.g. learn one framework with regular goals/check-ins and we each learn them independently (though we of course can help each other out with learning e.g. via Slack). 22 | 23 | I'd also say we should stick to a single language (Python) to minimize overhead of jumping around different languages. 24 | 25 | A big open question is how do we organize a course that has some very technical material for people of many different backgrounds in a way that isn't too lecture-focused and more discussion-oriented? 26 | 27 | ## Syllabus 28 | 29 | I think the syllabus could be based off of [my AI notes](http://frnsys.com/ai_notes/) but those are mostly focused on theory. So it would need to be supplemented with the "practical" thread (I think that can be informal though), the "social" thread (I have a stash of readings on those that I'll drop in here at some point), and the "philosophical" thread (I don't have much there tbh). --------------------------------------------------------------------------------