Perhaps the most famous site for learning how to code, this is must have for any aspiring computer scientist, web dev, or programmer. A smooth UI, dozens of courses, APIs, and fun quizzes if you decide to cough up a bit of money. $19 is crazy dirt cheap compared to some $200 courses out there on the web.
This is one of the BEST websites to learn about security and you can follow tutorials by real hackers and members of the IT field. With a strong community full of experienced authors, you will either flourish by using proper grammar or be mocked for asking “how do i hack gmail??”
ROBLOX hacking, general exploits, or just normal discussions. Roblox helped put me on my path to coding and I love how every day, millions of kids are being taught the ability of coding thanks to its studio.
I was feeling inspired last night, so I decided to make this purely for fun.
To the moon and back: Cold, dark nights clutching thermos flasks of hot coffee. Machinery whirring as telescopes trace a star across the sky. Intricate, geometric drawings of the celestial sphere. A messy bun and a NASA t-shirt. Filling in the logbook while punk rock blares in the background to keep you energised and awake. Pictures of nebulae and galaxies everywhere, because pretty space pictures is half the fun. Annoyed huffs every time someone mentions their star sign.
Natural Philosopher: Long, intellectual debates in coffee shops about mathematics, physics, philosophy. Chalkboards covered with equations and calculations in a precise, curving handwriting. That Eureka moment while deep in thought, expressed only with a small smile and a scribbled proof on the back of a serviette. Chaotic desks in front of bookshelves groaning with old textbooks. Antique lab equipment as functional decor.
“Trust Me, I’m a Scientist”: Large computer screens running freshly-typed code. Neat lab books and PDFs of journal articles. The smell of whiteboard markers. Polished new equipment in a tangle of cables, hooked up to a digital oscilloscope. Exact amounts of chemicals in rows in metal shelves. Resting your feet up on the bench after a long day in the lab. The satisfying hum of your colleagues as they work on their experiments around you.
Science Expedition: Dirt under your nails and a loosely-bound collection of field notes. Plant clippings carefully taken to be analysed back in the lab. Soft fur on tough, wild animals. The bitter smoke from eco-friendly firewood while you roast marshmallows and listen to a supervisor’s witty stories. Free-handing diagrams while looking through a microscope. Sketching flowers and that gorgeous ocean view from your last field trip. Reading Darwin on the bus home but falling asleep on your lab partner’s shoulder out of sheer exhaustion after the first three pages.
Life is a Science: Scrolling past an anti-vax facebook post and resisting the urge to burn down the internet. Shiny dissection kits and the sharp smell of formaldehyde. Making time to work out and pack a healthy lunch because your mind is sharpest when your body is well. Debunking the latest superfood fad with peer-reviewed journal articles. Making friends with some of the nicer med school kids in anatomy class. Colour-coded, neatly labelled diagrams and a thousand different terms memorised. Getting a double-helix DNA sculpture for your desk.
What they show on TV isn’t real hacking: Rubbing your eyes after staring at a screen for five hours straight. Having a blank keyboard because all the letters are rubbed off already. Energy drinks in strange colours at strange hours. Being fluent in four different coding languages. Circuit boards and printouts. Ones and zeroes. Running jokes about turning everything off and on again. Rage-quitting when you realise you forgot a comma or a colon somewhere. Black screens with brightly coloured lines. The comforting click-click of fingertips tapping keys. Applying to intern at Google every three months because maybe they’ll take you this time. Writing a piece of code to do something simple just because.
Margaret Hamilton (b. 1936) is a computer scientist and engineer
who, as Director of the Software Engineering Division of the MIT
Instrumentation Laboratory, played an important part in the Apollo space
programme. Her division was responsible for developing the onboard flight
software for the missions that put the first men on the Moon, and she was the
supervisor and lead programmer of the project.
She graduated with a
degree in abstract mathematics, during a time when computer science and
software engineering were not yet disciplines in their own right. She worked
for the SAGE Project, used by the military in aircraft defense. Since 1986 she
has been the CEO of Hamilton Technologies, an organization which she founded.
Hey, guys. I’ve decided to make my first study masterpost. This contains great free online courses to improve your coding skills and broaden your knowledge or a guide for a newbie who wants to start learning cs. Many of this recommendations were sent to me by some big tech-companies to help me to prepare for the interviews. Generally, it would be a great addition to classes taken at college.
This week’s spread!
Used the same style as last week, since I really liked that one. I noticed that I’ll use my bullet journal more when it looks pleasing to the eye. I know some prefer a more ‘practical’ journal, but this is what works for me. And anyone can journal the way they want right? That’s the good thing about bullet journals!
In 2014, President Obama learned how to write his first line of code from an 11-year-old. And this weekend, he announced a bold new initiative to ensure all of our students get the opportunity to learn the computer science skills they need to succeed in a 21st century economy. Learn more at wh.gov/CSforAll.
Happy Birthday Margaret Hamilton! The computer scientist who helped make the Apollo 11 Moon landing possible turns 80 today.
Hamilton earned a bachelor’s degree in mathematics and, at age 24, got a job at MIT as a programmer to develop meteorology software. In 1961 MIT was contracted by NASA to develop Apollo’s guidance system, and four years later Hamilton was put in charge of the software for navigation and lunar landing guidance. For Hamilton, programming meant punching holes in stacks of punch cards, which would be processed overnight in batches on a giant Honeywell mainframe computer that simulated the Apollo lander’s work. Her hard work paid off as the Eagle lander descended toward the Moon’s surface on 20 July 1969. The Apollo computer suddenly became overwhelmed, tasked with performing calculations unnecessary for the landing. But Hamilton and her team had prepared for such a possibility, coding in instructions that enabled the computer to correctly prioritize the most important commands.
Hamilton stayed on at MIT to head the software programming for Apollo and Skylab. Now an independent computer scientist, she described in 2009 her contributions to the Apollo software — which last month was added in its entirety to the code-sharing site GitHub: “From my own perspective, the software experience itself (designing it, developing it, evolving it, watching it perform and learning from it for future systems) was at least as exciting as the events surrounding the mission… There was no second chance. We knew that. We took our work seriously, many of us beginning this journey while still in our 20s. Coming up with solutions and new ideas was an adventure. Dedication and commitment were a given. Mutual respect was across the board. Because software was a mystery, a black box, upper management gave us total freedom and trust. We had to find a way and we did. Looking back, we were the luckiest people in the world; there was no choice but to be pioneers.”
Hi, I’m a Computer Science and Math major and here’s how I organize my university math notebooks. @hexaneandheels suggested/requested this post.
First of all, I have different (yet similar) setups for classes falling under two different branches of math, Continuous math and Discrete math. Long story short: Discrete math concerns sets of objects that are countable, and Continuous math concerns sets of objects that are “measurable.” Continuous math is, roughly speaking, math based on the continuous number line, or the real numbers. Its defining quality is that given any two numbers, you can always find another number between them–in fact, you can always find an infinite set of numbers between them. In discrete mathematics, you’re working with distinct values: given any two points in discrete math, there aren’t an infinite number of points between them. If you have a finite set of objects, you can describe the function as a list of ordered pairs, and present a complete list of those pairs. If you’re interested, there are further explanations here, here, and here.
Classes that rely more on continuous math: Calculus, Differential Equations, Real Analysis, Linear Algebra, Trigonometry
Discrete math classes: Discrete Mathematics (Discrete Structures), Logic and Proofs, Computability Theory, Number Theory, Graph Theory
Discrete Math: Lined notebook (in my case, Moleskine Volant, but there’s no need for fanciness)
Both: 2- or 4-pocket folder (I prefer Five Star) - to keep worksheets, your work from practice problems, exams, syllabus, scratch paper, and all related class papers
Page 1: Title Page (can include course # and professor)
Page 2-4: Syllabus (printed and taped in)
Page 5-6: Table of Contents
Page 7: First Chapter/Section Title page
Page 8: First Chapter/Section important dates/comments/notes
Page 9: First Section/Lecture
(and so on…)
FEATURES (I ADDED)
numbered pages (bottom left/right corners, see example above)
Headers and new pages for every new subject, with date of lecture (if applicable)
front cover pocket for formulae sheets/notecards (half an envelope, taped with washi tape)
key words underlined in color
blue ink boxes/brackets around practice problems and examples
recitation notes (even if you forget your notebook in recitation, tape them in! they’re so important)
ADVICE FOR UPKEEP
Don’t beat yourself up if your notebook isn’t perfect. Mine certainly aren’t! I only try to maintain enough organization for my notes to be a quick, easy reference when I work problems. If working more problems means sacrificing keeping the table of contents updated, so be it. I’m guilty of this!
BE NEAT, NOT PRETTY. Notice my notes don’t really adhere to the jazzy studyblr trend, and I never rewrite them (I only revisit to touch up/add info). Because they don’t need to! Working problems is the most important thing for success in university mathematics.
Always take notes in recitation to keep in the notebook.
Keep track of questions you have, either in a designated section of your notebook or other notebook. I have another small notebook for questions for all my classes, to use during office hours/reviewing/etc.