- Programming Digest
- Posts
- Programming like it’s 1977
Programming like it’s 1977
128 bytes of RAM, no operating system, and limited types of sprites
Jakub Chodounsky
May 20, 2024
Programming like it’s 1977
10 minutes by Adam Tornhill
Earlier this year I started a new hobby: writing games on the Atari VCS. The Atari VCS – or Atari 2600 as later versions were labeled – is a curious piece of hardware. It's heavily constrained with its 128 bytes of RAM, no operating system, and limited types of sprites.
WorkOS: Enterprise-grade Auth designed for B2B SaaS
sponsored by WorkOS
WorkOS is a modern identity platform for auth as well as complex enterprise features like SSO, SCIM, and RBAC. It provides modular and easy-to-use APIs, helping hundreds of high-growth companies like Vercel, Webflow, and Perplexity become Enterprise Ready. Integration is simple, and you can enjoy free User Management up to 1,000,000 MAUs.
Why do CPUs have multiple cache levels?
15 minutes by Fabian Giesen
The short version is that the various cache levels have very large variations in how they are designed; they are subject to different constraints and fulfill different purposes. As a rule of thumb, as you climb up the levels of the cache hierarchy, the caches get larger, slower, higher density (more bits stored per unit area), consume less power per bit stored, and gain additional tasks.
Making a Postgres query 1,000 times faster
19 minutes by Alejandro García Montoro
Learn how we discovered what was slowing down large database queries, and what we did to make Postgres queries 1000x faster.
You probably don’t need microservices
8 minutes by Bruno Costa
Microservices are very popular nowadays. It's a great architectural style that helps to scale the system and the organization. Many successful companies use microservices (e.g. Netflix, Spotify, etc). Therefore, it's normal that most companies are using or planning to use it. But some miss the added costs it brings.
Avoiding the soft delete anti-pattern
7 minutes by Tim Fisken
The main problem with soft deletion is that you’re systematically misleading the database. This is most obvious in the case of foreign key constraints. If it’s important to your data integrity that some column in one table references a row that exists in another table, a foreign key constraint instructs the database to enforce that by, among other things, preventing the deletion.
how did you like this issue? |