HackerTrans
トップ新着トレンドコメント過去質問紹介求人

crcastle

no profile record

投稿

Who Will Monetize Truth? [pdf]

readwise-assets.s3.amazonaws.com
2 ポイント·投稿者 crcastle·2 か月前·0 コメント

The quiet grief of adult friendship

timesofindia.indiatimes.com
4 ポイント·投稿者 crcastle·2 か月前·1 コメント

How to Call an API from an Email

redo.com
3 ポイント·投稿者 crcastle·2 か月前·0 コメント

The Figure-Eight Model for Agentic DevEx

medium.com
3 ポイント·投稿者 crcastle·2 か月前·0 コメント

[untitled]

1 ポイント·投稿者 crcastle·3 か月前·0 コメント

Bloom filters: the niche trick behind a 16× faster API

incident.io
2 ポイント·投稿者 crcastle·3 か月前·1 コメント

Dear Heroku: Uhh What's Going On?

judoscale.com
108 ポイント·投稿者 crcastle·3 か月前·45 コメント

AWS engineer reports PostgreSQL perf halved by Linux 7.0, fix may not be easy

phoronix.com
410 ポイント·投稿者 crcastle·3 か月前·165 コメント

Future Shock

blog.ceejbot.com
3 ポイント·投稿者 crcastle·4 か月前·1 コメント

Render raises $100M at $1.5B valuation

render.com
3 ポイント·投稿者 crcastle·5 か月前·1 コメント

Public Makes Millions on Plunging Crypto

cepr.net
29 ポイント·投稿者 crcastle·7 か月前·22 コメント

Nat traversal, and how we're improving it

tailscale.com
2 ポイント·投稿者 crcastle·9 か月前·0 コメント

Absolute Scale Corrupts (2019)

tailscale.com
1 ポイント·投稿者 crcastle·9 か月前·0 コメント

Setting Up a Home ISP with GPON

apalrd.net
3 ポイント·投稿者 crcastle·9 か月前·0 コメント

The Meandering Sea of Primordial Soupy Thought

kennethreitz.org
3 ポイント·投稿者 crcastle·10 か月前·0 コメント

Open Source SDR Ham Transceiver Prototype

m17project.org
117 ポイント·投稿者 crcastle·10 か月前·11 コメント

コメント

crcastle
·3 か月前·議論
Not historically.
crcastle
·3 か月前·議論
Ubuntu is used in many serious backend environments. Heroku runs tens of thousands (if not more) instances of Ubuntu on its fleet. Or at least it did through the teens and early 2020s.

https://devcenter.heroku.com/articles/stack
crcastle
·4 か月前·議論
Full post title is Building a Firewall ...via Endpoint Security!? Reverse Engineering macOS 26.4's Undocumented Network Events

The second sentence may be more useful as the title here.
crcastle
·4 か月前·議論
This is one of the more level-headed and empathetic writings that I've seen on the impact of LLMs on software engineers and our (or at least my) current strange combination of unbridled enthusiasm with existential dread. And it finishes with actual practical advice. (the post was derived from a talk the writer gave at his company)

> there’s fear in the air. You’ve heard that if you don’t learn these tools, you’ll be unemployable. That sounds pretty awful to me. What if none of us have jobs at the end of this?

> The industrial revolution didn’t eliminate human labor. It changed what human labor meant. Human labor still mattered at the end of it. The people who adapt to major technological shifts don’t just survive—they become more valuable, not less.

> I’m here to tell you it’ll be okay. You are smart. You can adapt. I believe in you.

> It’s not about 20x the number of lines of code you write, though you can do that. It’s about doing things you wouldn’t have attempted at all.

> A refactoring you’d never have had time for.

> An analysis you’d never have bothered with.

> A prototype you’d never have built.

> I’ve been doing this for nearly thirty-five years, and this is the most exciting time to write software I’ve seen. Yes, there are pleasures lost here. I love the flow state of writing code, just like I love printing black and white photographs in the darkroom. I don’t have to lose either one. I can still do both for pleasure. Black and white photography isn’t part of anybody’s journalism workflow any more, but people still do it. There’s a place for it all.

> The tools make it easy to produce a lot of code fast. They do not make it safe to skip evaluating what it did. Nobody is exempt. Don’t make our security team have to file disclosure reports, or clean up our messes.

> Two facts:

> We are responsible for what we ship.

> We can’t skip evaluating the work.