r/computerscience • • Apr 05 '26 WOW

Useful diagrams

Post image
1.2k Upvotes

Hi everyone,

I recently came across this old diagram and I found it incredibly useful as a reference.

I was wondering if anyone here knows of other similar resources (like detailed charts, схемatics, books, or technical manuals) that systematically cover cables, ports, and connectors in a structured and exhaustive way.

I’m especially interested in materials that go beyond the basics and include less common or legacy standards as well.

Any recommendations would be greatly appreciated!

Thanks in advance :)


r/computerscience • • Jun 14 '20

General Sister Mary Kenneth Keller the first woman to earn a doctorate in computer science in the USA 1965

Post image
1.2k Upvotes

r/computerscience • • Aug 05 '21

General Built a computer from scratch. A Z80 running at 2mhz, 32k ram, 32k rom, an 8255 for IO, port A of the 8255 connected to the LEDs. You don't want to see the back of it trust me.

1.2k Upvotes

r/computerscience • • Aug 12 '20

Artificial Intelligence creates 3D rendering of landmarks by interpolating thousands of tourist images

1.1k Upvotes

r/computerscience • • Nov 01 '20

Updated: QR code paper

Post image
1.1k Upvotes

r/computerscience • • May 28 '25

New algorithm beats Dijkstra's time for shortest paths in directed graphs

Thumbnail
arxiv.org
1.1k Upvotes

r/computerscience • • Jun 15 '19

General This explains so much to me

Thumbnail
i.imgur.com
1.0k Upvotes

r/computerscience • • Feb 24 '21

General Morning train rides 545am

Post image
1.0k Upvotes

r/computerscience • • 5d ago

General Carnegie Mellon is putting computer science courses on YouTube for free

Thumbnail
cs.cmu.edu
1.0k Upvotes

r/computerscience • • May 02 '20

Discussion To what degree Would Augmented Reality change the way we study math?

1.0k Upvotes

r/computerscience • • Oct 15 '20

Advice The advice I wish I would have recieved a few years ago

1.0k Upvotes

When I was first starting my undergrad in CS, I came to this sub in utter frustration. I had learned java, and was being asked to learn other languages, too. I struggled to adapt. I knew the concepts, but I didn't know how to translate that into another language. I didn't even know how to start learning C or C++. I came here asking for advice and reassurance, however I received anything but.

"If you can't learn another language, you shouldn't be in the field.""You should switch majors now before you've gone too far, because you're going to be worthless in the field.""What did you expect when you signed up for CS? Of course you're going to have to learn another language. Get over yourself."

These comments on a long deleted post stuck with me. The people who posted them have probably forgotten what they said. They have no idea how hard it was for me to read those words, and how their words made me genuinely think that I wasn't cut out for this area of study.

They were wrong. I'm now about to graduate, am in the top 10% of my class, and have overcome the struggle of adapting to new languages (mostly!). I'm still far from being an expert, but I've come a long ways.

I'm now here to give the advice my younger self was seeking, in the hopes that it'll help some of you who feel discouraged in the same way I was.

  1. Learning a new programming language gets easier over time. Of course you're going to struggle when you learn your first or second language! That's fine! It's normal! It's a new concept for you! Don't give up!

  2. Focus on the big picture! Learn about efficiency, data structures, and theories. Explore data science and machine learning. Don't be afraid to take a class just because you don't know the language that'll be used! Computer science is more than learning the differences between python and java. So much more.

  3. Just because you know a lot of languages doesn't necessarily mean anything. It's more important to know the concepts and how to apply those concepts in your code. You can always google for the specific implementation!

  4. Reading all the documentation about a language doesn't mean anything until you sit down and start coding. I know it's anxiety inducing. I know it's tough to get to that point. Start off learning how to print, how to make lists/arrays, and how to iterate. Implement those concepts. That'll give you a good idea of how to begin. Your compiler or IDE may give you errors. That's fine! You can learn from them. Just start at the first error you get, and work your way through.

  5. Everyone struggles in the beginning. You're not unusual for crying out of frustration. You just need to take a deep breath and ask for help. If you're struggling, you should seek out people willing to help you. There's no shame in it.

  6. Don't listen to miserable people on the internet. You are good enough. You chose a hard field, but you got this.

And my final bit of advice goes to the people on this sub:

Be kind. Your words have meaning, even if you comment in a hurry. The person on the other end may genuinely be affected by what you say, so make sure they're affected positively.

edit: a word


r/computerscience • • Apr 11 '19

General Katie Bouman with the stack of hard drives containing Terrabytes of data obtained from the EHT. It was her algorithm that took disk drives full of data and turned it into the image we saw yesterday. Reminiscent of Margaret Hamilton with her stack of printouts of the Apollo Guidance System.

Post image
974 Upvotes

r/computerscience • • May 27 '20

Computer screen under microscope

Post image
969 Upvotes

r/computerscience • • Sep 03 '20

Today I had the chance to see the very unique Enigma Machine and I thought I would share it with you guys!

Post image
958 Upvotes

r/computerscience • • Feb 20 '20

Donald Knuth Deemed Me "A Gentleman and a Hacker"

Post image
957 Upvotes

r/computerscience • • Jan 03 '25

Jonathan Blow claims that with slightly less idiotic software, my computer could be running 100x faster than it is. Maybe more.

919 Upvotes

How?? What would have to change under the hood? What are the devs doing so wrong?


r/computerscience • • Apr 25 '19

It is

Post image
916 Upvotes

r/computerscience • • Feb 13 '25

A new sorting algorithm for 2025, faster than Powersort!

908 Upvotes

tl;dr It's faster than Python's Default sorted() function, Powersort, and it's not even optimized yet. See chart below:

JesseSort uses a Rainbow data structure to keep search space small. A Rainbow is an array of array-like structures with a special feature: the first and last values of each subsequent subarray are guaranteed to be in sorted order. The "base array" in the black rectangle represents the search space for inserting new values. As a band can have near-infinite values in it and its search space remains its 2 ends, one can easily see how JesseSort offers value at scale.

JesseSort has 2 main phases: insertion and merging. For each new value, do binary search for insertion index inside base array in log time, insert value into band (front or back of it), replace value in base array, loop. Then merge all bands until one remains. To avoid front-end insertion issues, we split the Rainbow bands into 2 halves and reverse the order of the bottom half subarrays.

Code and paper here: https://www.github.com/lewj85/jessesort

Edit: This is apparently related to Patience Sort. And I've unexpectedly solved its biggest issue by essentially playing 2 games of Patience simultaneously, one with descending stacks and one with ascending stacks. I provide an update here: https://www.reddit.com/r/computerscience/comments/1iqvj4n/updates_on_jessesort/


r/computerscience • • May 01 '21

New to programming or computer science? Want advice for education or careers? Ask your questions here!

890 Upvotes

The previous thread was finally archived with over 500 comments and replies! As well, it helped to massively cut down on the number of off topic posts on this subreddit, so that was awesome!

This is the only place where college, career, and programming questions are allowed. They will be removed if they're posted anywhere else.

HOMEWORK HELP, TECH SUPPORT, AND PC PURCHASE ADVICE ARE STILL NOT ALLOWED!

There are numerous subreddits more suited to those posts such as:

/r/techsupport
/r/learnprogramming
/r/buildapc
/r/cscareerquestions
/r/csMajors

Note: this thread is in "contest mode" so all questions have a chance at being at the top


r/computerscience • • Aug 10 '21

Conway's Game of Life emulated in Conway's Game of Life

859 Upvotes

r/computerscience • • Feb 27 '21

General An engineer wiring an early IBM computer.1958

Post image
859 Upvotes

r/computerscience • • Aug 19 '20

General And so it begins.

Post image
817 Upvotes

r/computerscience • • Apr 19 '26

General I was taught nothing about APIs

816 Upvotes

Whenever i see people talking about actual real-world uses of coding it's almost entirely building APIs, working with APIs, integrating APIs, automating APIs. It seems to me, anecdotally at least, like the majority of all computer science work (professional or even just hobby) is centered on working with APIs

And like. I know what an API is, kind of. But I Graduated and even got multiple certifications on top of that and I never got so much as a single lecture about APIs. I don't even know what they're used for. Can you make your own API (like, realistically)? I don't know. I feel like this is a topic that you could and probably should have multiple different entire classes solely focused on, it's arguably something as fundamental to modern computer science as writing code. And they don't teach it. If i want to learn anything about APIs, conceptually or practically, it's hope a company hires me and then trains me, or youtube tutorials and i don't even have enough of a baseline to know what specifically I'd be searching for a tutorial on.