calci's corner

but if we arrange those electrons just so, and let them do their thing, we can create a pattern that someone will experience as bits, registers, numbers, letters, instructions, algorithms, messages, financial transactions, videos, thoughts, worlds, etc etc.

the whole project of computer programming is corraling the electrons into situations where they will obey rules we have in our heads. electrons are surprisingly predictable, so this isn't a fool's errand. but every layer of the stack of abstractions is something we built: arranging one thing to produce a pattern we want to see. the chip arranged so the 'high and low voltages' fit our idea of 'bits' and 'logic gates'. the screen whose lights create a 'field of colour' for an organism that has this level of visual acuity, this frequency response in its cone cells, this capacity to see shapes and edges. these bits and logic organised into an 'algorithm' that takes 'data' that we think of as 'vertices' and 'triangles' and produces the appearance of 'perspective rendering', which approximates our concept of a '3D object', of even a 'virtual world'.

source

be aware that you will never feel completely prepared. avoid bouts of anxiety and be wary of self-deprecating thoughts. keep studying consistently, as this will bring progress.

understand the business rules of the problem you are solving (i.e. clearly understand what the code needs to accomplish in the real world).

more important than speed is direction. take your time, but move forward with purpose.

avoid studying only by copying tutorials or code snippets. this approach limits your development and increases the chance of being easily replaced by artificial intelligence.

seek out as much experience as possible and don't be afraid to make mistakes - they are part of the process.

take pleasure in learning and exploring. try to create things that you really want.

one of the biggest mistakes is to create the same projects that everyone else is doing. look for innovation, originality and solving real problems.

networking: participate in groups and communities, genuinely contribute to discussions, get involved with open source projects and make yourself visible in the field.

be patient. learning and professional development are continuous.

No subscription. Just program.

On your computer. You got to use it forever and ever and never had to worry about it going away.

Because it was physically on your computer. As a program. That you actually owned. Not because you got it separately, but because it was a standard inclusion with your computer.

I'm sorry but I'll just never get over it. I remember when companies cared about their products being usable out of the box. I remember when our things belonged to us.

My Linux PC came with LibreOffice installed right out of the box, along with several other useful programs, and a Flatpak installer that lets me search for and install a whole gamut of open-source freeware, including esoterica like QGIS.

No cruft. No adware. No spyware. No subscriptions.

It's MY machine, and the software on it is MINE, physically installed on MY hard drive.

thought it would be a good psa

for artists here too

some advice i have for future computer science students

as soon as you learn data structures & complexity, run, don’t just walk, RUN to leetcode while the knowledge is still fresh in your mind. your entire career and whether you’ll get a well-paying job vs an average paying job depends on how good you are at leetcode.

build as many projects as you can, and i’m not talking tutorial projects that take a few hours, i’m talking big projects. working on a project for a month or two will get you really far.

if you don’t have an internship, do not waste your summers, learn new technologies, languages, concepts and build projects you can put in your cv.

try to participate in hackathons and coding competitions. it’s okay if you fail, but you’ll learn a lot.

learn how to read documentation. most tutorials don’t even cover a quarter of what a language, framework or software has to offer. the sooner you make reading documentation a habit, the better it is. and yes i know, documentation is long and hard to read. my advice is only read the sections that are relevant to you in the moment. something i also personally do is look at the code examples at the same time as i am reading the paragraphs, it really helps easily absorb the information.

try not to use chatgpt. and if you do, then at least use it for stuff you know you can do yourself and will be able to correct if the bot gets it wrong. using chatgpt is a very slippery slope and the more you use it the less you learn.

the math is important. math teaches you how to reason and how to develop better logical thinking. just because you don’t see yourself using the xyz theorem you’ve learnt anytime in the future doesn’t mean the math is useless.

be prepared to get comfortable with erros, issues, bugs and just problems in general. you’ll be coding 30% of the time and debugging 70% of the time (i’m exaggerating but sometimes it feels like this is the case lol), and that’s okay, it’s how we learn and the sooner you embrace it the better. if you’re someone who easily gets frustrated, then this is a heads up.

learn as you go. there is no such thing as waiting until you know everything before you start on a project. the only way and the best way to learn in this field is practice, so build, build, and build.