What is going on in Unix with errno's limited nature(utcc.utoronto.ca)

61 points by ingve 1 year ago | 38 comments

Monitoring your logs is mostly a tarpit(utcc.utoronto.ca)

97 points by signa11 3 years ago | 77 comments

I can't recommend serious use of an all-in-one local Grafana Loki setup(utcc.utoronto.ca)

103 points by ink_13 3 years ago | 75 comments

Plaintext is not a great format for (system) logs(utcc.utoronto.ca)

5 points by thunderbong 2 years ago | 1 comments

What ZIL metrics are exposed by (Open)ZFS on Linux(utcc.utoronto.ca)

43 points by rbanffy 2 years ago | 2 comments

The Bogus CVE Problem(lwn.net)

224 points by signa11 3 years ago | 106 comments

Do the simplest thing that could possibly work(seangoedecke.com)

1015 points by dondraper36 1 year ago | 364 comments

Blog post by Sean Goedecke arguing engineers should understand the current system deeply and then do the simplest thing that could possibly work.

TODOs aren't for doing(sophiebits.com)

380 points by todsacerdoti 1 year ago | 218 comments

A blog post by Sophie Alpert arguing that TODO comments are valuable as documentation of known issues even if never acted on, and shouldn't be auto-deleted or tracked.

Domain expertise has always been the real moat(brethorsting.com)

774 points by aaronbrethorst 4 months ago | 484 comments

Blog post arguing that agentic AI shifts software's binding constraint from building code to judging correctness, making domain expertise the real moat.

The new skill in AI is not prompting, it's context engineering(philschmid.de)

832 points by robotswantdata 1 year ago | 467 comments

Blog post by Philipp Schmid arguing that context engineering, supplying LLMs with the right information and tools, matters more than prompting for AI agents.

Most arguments are about ego, not ideas(wangcong.org)

560 points by backlit4034 3 months ago | 431 comments

Personal blog post by a software engineer explaining why he stopped arguing with people over technical correctness and what he learned about arguments.

LLM-powered tools amplify developer capabilities rather than replacing them(matthewsinclair.com)

323 points by matthewsinclair 1 year ago | 214 comments

Blog post by Matthew Sinclair arguing that LLM-powered programming tools act like a mech suit amplifying developers rather than replacing them.