Editing Algorithms for the Love of It

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 3: Line 3:




= Highly Suggested Learning Preparation =  
= Learning Tips =  


* If you come from a developers' bootcamp / didn't-study-Computer-Science-in-school background....., a big mistake many people like yourselves make is diving into a college-level Algorithms class first. I think it's much wiser to obtain a 500-900 page basic Data Structures Computer Science book, watch an online course on Coursera, and then augment that with the more comprehensive Algorithms course available on MIT.
* It is extremely easy to forget this stuff unless you find a way to involve it in your everyday life (context) - always, always try to find some kind of relationship between these concepts and your every day code, no matter how obscure!
* Memorization is '''very''' important - do not believe otherwise!
* Memorization is very important - do not believe otherwise!
* It is extremely easy to forget this stuff unless you find a way to involve it in your everyday life (context) - '''always always''' try to find some kind of relationship between these concepts and your every day code, no matter how obscure!
* If you come from a developer bootcamp / didn't study computer science in school background - a big mistake many people make is diving into a college level algorithms class first. Most of the basics of algorithms are covered in a freshman level Data Structures class. I highly recommend shelling out for a 800 or 900 page college data structures book. The problem with online classes is that they condense too much information into short 5 minute sound bites, when what you really need is hundreds of hours of lectures and an even thicker textbook. Once I got my hands on a Data Structures text book I felt much less overwhelmed, and the lengthier explanations and examples made the coursework easier to understand. You honestly aren't going to encounter this stuff very often in your day to day life as a software engineer, but it's fun stuff to know and should be a good hobby you keep up unless you luck out and get one of those rare dream jobs at Google or academia.


Formerly [https://noisebridge.net/wiki/(affiliated_with)_Women_Who_Code_Algorithms_Study_Group algorithms study group affiliated with women who code]
Formerly [https://noisebridge.net/wiki/(affiliated_with)_Women_Who_Code_Algorithms_Study_Group algorithms study group affiliated with women who code]
Please note that all contributions to Noisebridge are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see Noisebridge:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)