coding-interview-university

Racket: https://learnxinyminutes.com/racket/ Python: https://learnxinyminutes.com/python/ pyret? pyret: https://pyret.org/pyret-code/ : > Why not just use Java, Python, Racket, OCaml, or Haskell? IMHO fun educational learning languages aren't general purpose or production ready; and so also at this point in my career I would appreciate a more reusable language in a CS curriculum. Python isn't CS pure like [favorite lisp], but it is a language coworkers will understand, it supports functional and object-oriented paradigms, and the pydata tools enable CS applications in STEM. A lot of AI and ML code is written in Python, with C/Rust/Go. There's an AIMA Python, but there's not a pyret or a racket AIMA or SICP, for example. "Why MIT Switched from Scheme to Python (2009)" https://news.ycombinator.com/item?id=14167453 Computational thinking >

Which programs offer Formal Methods and TLA+? Define a relative metric for comparison Programmer's Competency Matrix: https://cuamckuu.github.io/index.html Coding Interview University: https://github.com/jwasham/coding-interview-university Coding Guidelines: https://awesome-safety-critical.readthedocs.io/en/latest/#co... Predict software quality and/or career success Predict applied ML/AI failure due to insufficient Data Science fundamentals By well-rounded do you mean the ACM Computer Science Curriculum; or a strong liberal arts program which emphasizes critical thinking and effective communication; or Emotional Intelligence, Servant Leadership, and Project Management? InfoSec; Computer Security > Careers: https://en.wikipedia.org/wiki/Computer_security#Careers The NIST NICE Framework describes Categories (7), Specialty Areas (33), Wo

I'm not sure why you assume it has to be hundreds of hours. Take a look at something like https://github.com/jwasham/coding-interview-university, which has a lot of different topics. In interview loops I've done recently, I realized I was most nervous around Systems/Scaling and Graph (e.g. Dijkstra's) questions, so took some time to work on those. You don't have to do like the author of that piece and work for hundreds of hours. If trees are proving a problem or are an area you know you aren't so up on, then use studying to fill in the gap. Anything is better than nothing, and studying for, let's say, 10 hours might make you just more comfortable with the topic to turn the interview in a more positive direction. (Disclaimer: I have a academic background from years ago, just haven't used most of these things in years, since like everyone h

I got this push message from Hacker News this morning and felt obliged to post my opinion on the "LeetCode thing" cause I'm currently trying the same thing as you are. I have a master degree on CS and 4 years of professional experience and trying to keep moving forward. I don't believe solving LeetCode problems well is something that you have to be gifted to achieve. Ironically, I believed it once upon a time. I got very frustrated when failed tech interviews for Microsoft and Google when I was a new-grad and trying to find a decent job. I know it's frustrating to just look at somebody finishing all the contest problems in 10min and you're scratching your head for many hours or even a whole day. Believe me I was literaly doing this for a long time. But I started my professional occupation anyway. What I did then is keep trying for several

> My question is how do you find all those algorithms? Wikipedia never really feel like a good introductory nor discovery place. I know a place. From the Github repo Coding Interview University[0] there is a link to a Jupyter notebook[1] on various ways to solve the traveling salesman problem - it is a very good, detailed, resource. [0] https://github.com/jwasham/coding-interview-university [1] https://nbviewer.jupyter.org/url/norvig.com/ipython/TSP.ipyn...

Problem solving: https://en.wikipedia.org/wiki/Problem_solving Critical thinking: https://en.wikipedia.org/wiki/Critical_thinking Computational Thinking: https://en.wikipedia.org/wiki/Computational_thinking > 1. Problem formulation (abstraction); > 2. Solution expression (automation); > 3. Solution execution and evaluation (analyses). Interviewers may be more interested in demonstrating problem solving methods and f thinking aloud than an actual solution in an anxiety-producing scenario. https://en.wikipedia.org/wiki/Brilliant_(website) ; > Brilliant offers guided problem-solving based courses in math, science, and engineering, based on National Science Foundation research supporting active learning.[14] Coding Interview University: https://github.com/jwasham/coding-interview-university Programmer Competency Matrix: https://github.com/hlt

K12 CS Framework (ACM, Code.org, [...]) https://k12cs.org/ Computing Curricula 2020 (ACM, IEEE,) http://www.cc2020.net/ Official SAT Practice (College Board, Khan Academy) https://www.khanacademy.org/sat http://wrdrd.github.io/docs/consulting/software-development#... (TODO: add link to cc2020 draft) Programmer Competency Matrix: http://sijinjoseph.com/programmer-competency-matrix/ , https://competency-checklist.appspot.com/ , https://github.com/hltbra/programmer-competency-checklist Re: Computational thinking https://westurner.github.io/hnlog/#comment-15454421 Coding Interview University: https://github.com/jwasham/coding-interview-university

I have an undergraduate degree in computer science but I have never had a software engineering job. I worked for a year as a BA and then went ahead and did my master's in information systems. I have now been working as a Technology Analyst at a decent sized firm where I basically do all BA stuff, document requirements, JIRA, Scrum etc. I'm now realizing that BA/Project Manager work might not be the best fit for me. I do not enjoy my work and it gets pretty mundane. Is it too late to get back into software engineering? I have had a couple of internships where I wrote some code (not pure development internships) but I have never really worked in a professional software development environment. I also have some personal projects that I can put on my resume. To upsert my knowledge of computer science, I have started working through this (on t