Programming

17325 readers

100 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

End-to-End Arguments In System Design (hachyderm.io)

submitted 8 months ago by otl@hachyderm.io to c/programming@programming.dev

2 comments fedilink hide all child comments

End-to-End Arguments In System Design

https://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf

Awesome paper clearly articulated.

This article reminds me how demoralising finding work feels for me sometimes. I wish I could put something on a résumé that says I appreciate this kind of system thinking. Who cares how many years of programming in a specific language, or which "well-known" companies someone has worked at? It feels like hiring journalists based on their years of experience with pencils.

@programming #programming

top 2 comments

sorted by: hot top controversial new old

[–] solrize@lemmy.world 4 points 8 months ago* (last edited 8 months ago) (1 children)

A classic from 1981.

[–] otl@hachyderm.io 3 points 8 months ago

@solrize 43 years young.

When I hear people talk about system issues (e.g. complex microservice architectures) I thought it was all cutting-edge problems of cutting-edge tech. Looks like people have been running into the same things for decades!

@programming