サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
体力トレーニング
www.tbray.org
On March 15, 2010, I started a new job at Google. The fourteen years since that day feel like a century. The title of my announcement was Now A No-Evil Zone and, OK, I can hear the laughing from ten timezones away. I tried, then, to be restrained, but there are hardly words to describe how happy and excited I was. I had escaped from the accretion disk the former Sun Microsystems was forming around
[This fragment is available in an audio version.] I’ve just finished setting up a new Mac (14" MBP, M2 Pro, 32G, 4T). It dawned on me that most of my really intense interactions with this thing involve looking at “monospace” (i.e. fixed-width) text; in Emacs where I write this blog, in my IDE, and in my terminal. The ones that came with the machine by default are, well, OK, but maybe we can do bet
[This fragment is available in an audio version.] Today I’m leaving Twitter, because I don’t like making unpaid contributions to a for-profit publisher whose proprietor is an alt-right troll. But also because it’s probably going to break down. Read on for details. I was beginning to think the End-Of-Twitter narrative was overblown, but evidence is stacking up. First, the increasingly-toxic politic
[This fragment is available in an audio version.] Suppose you’re running your organization’s crucial apps in the cloud. Specifically, suppose you’re running them them on AWS, and in particular in the “us-east-1” region? Could us-east-1 go away? What might you do about it? Let’s catastrophize! Acks & disclaimers · First, thanks to Corey Quinn for this Twitter thread, which got me thinking. Second,
[This fragment is available in an audio version.] Grown-up software developers know perfectly well that testing is important. But — speaking here from experience — many aren’t doing enough. So I’m here to bang the testing drum, which our profession shouldn’t need to hear but apparently does. This was provoked by two Twitter threads (here and here) from Justin Searls, from which a couple of quotes:
May 1st was my last day as a VP and Distinguished Engineer at Amazon Web Services, after five years and five months of rewarding fun. I quit in dismay at Amazon firing whistleblowers who were making noise about warehouse employees frightened of Covid-19. What with big-tech salaries and share vestings, this will probably cost me over a million (pre-tax) dollars, not to mention the best job I’ve eve
More or less all the big APIs are RESTful these days. Yeah, you can quibble about what “REST” means (and I will, a bit) but the assertion is broadly true. Is it going to stay that way forever? Seems unlikely. So, what’s next? What we talk about when we talk about “REST” · These days, it’s used colloquially to mean any API that is HTTP-based. In fact, the vast majority of them offer CRUD operations
[This fragment is available in an audio version.] [Update: As of Jan 1, 2023 this is fixed! Thanks to Danny Sullivan and John Mueller of Google for figuring out what was going on. Yay!] I think Google has stopped indexing the older parts of the Web. I think I can prove it. Google’s competition is doing better. [Update, Feb. 2022: It’s still happening.] Evidence · This isn’t just a proof, it’s a ro
The IETF just published RFC 8259 (also known as “STD 90”). Editor, yr humble servant. The legacy-ASCII full text is here and there’s a nice-looking HTML verion here. I think this is the last specification of JSON that anyone will ever publish. The story of how we got to RFC 7159, this RFC’s predecessor, is told in JSON Redux AKA RFC7159 and I won’t re-tell it. The reason 8259 exists is that the EC
Suppose you’re doing technology, and like doing technology, and your career’s going well, and you find yourself wondering what you’re going to be doing in twenty years. I’ve been down several of the roads you might decide to take, and it occurs to me that talking them over might amuse and inform. Thanks are due to Andre Leibovici, who tweeted Is it possible to be in a sr. leadership position and s
I’m one. We’re not exactly common on the ground; my profession, apparently not content with having excluded a whole gender, is mostly doing without the services of a couple of generations. This was provoked by a post from James Gosling, which I’ll reproduce because it was on Facebook and I don’t care to learn how to link into there: Almost every old friend of mine is screwed. In the time between S
I find myself tasked with polishing and publishing a little custom JSON-encoded language. It’s harder than it ought to be. This didn’t start with the language, it started with prototype software this guy wrote, that did something old and familiar in a new and dramatically better way. He replaced a bunch of gnarly old code with a few JSON templates to save time. Now, in the rearview, the JSON looks
Gosh, it seems that my employer’s at-work culture is the talk of the Internet. Don’t know if I should share on the topic, but I feel the urge and bloggers with the urge gotta blog. Tl;dr · First: I haven’t seen that stuff Kantor and Streitfeld write about. Not saying that never did happen, or isn’t happening somewhere, just that I haven’t seen it. Second: The similarities between Amazon and Google
Item: The W3C HTML Working Group charter is expiring. Item: Discussion on what to do is inconclusive. Item: Things are pretty quiet in the WhatWG. Conclusion: The best thing to do about HTML is nothing. As Sam Ruby points out, interest in work on “vocabulary” (by which they mean the actual angle-bracketed thingies that go into HTML) seems pretty lacking. Me, I think HTML is done. Which doesn’t mea
As of December I’m working for Amazon. This will be different from my last few gigs; in particular, don’t expect to read about it here. The preaching and coding around privacy and security I’ve been doing these last few months has been a blast, but it doesn’t seem to be a paying job nor even a coherent organized project, the kind with co-workers. And Amazon is offering me one of those, so here I a
Most server-side APIs these days are JSON-over-HTTP. Developers are generally comfy with this, but I notice when I look at the JSON that it’s often, uh, what’s the tactful term these days? Let’s say “generously proportioned”. And I see clumsy code being written to walk through it. The options for dealing with this are interesting. For example · I’ve been working with keybase.io recently; when you
As of March 17th I’ll be an ex-employee. It’s an amicable separation in the face of irreconcilable differences: I wouldn’t move to California and Google wouldn’t open a Vancouver office. I haven’t decided what to do next. Let’s go with Q&A format. Seriously, about remote work? · Yep. Both before and after being hired, I had been asked to consider moving south. I didn’t want to and politely decline
We’re at an inflection point in the practice of constructing software. Our tools are good, our server developers are happy, but when it comes to building client-side software, we really don’t know where we’re going or how to get there. Happy times upstream · The art and science of building server-side code is just fine, thank you; the technology’s breadth and polish has been ramping for years and
Whether you like XML or not, we’re stuck with it for a long time. These days, the only new XML-based projects being started up are document-centric and publishing-oriented. Thank goodness, because that’s a much better fit than all the WS-* and Java EE config puke and so on that has given those three letters a bad name among so many programmers. XML for your document database is actually pretty har
A New HTTP Status Code for Legally-restricted Resources draft-tbray-http-legally-restricted-status-00 Abstract This document specifies an additional Hypertext Transfer Protocol (HTTP) status code for use when resource access is denied for legal reasons. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working doc
次のページ
このページを最初にブックマークしてみませんか?
『www.tbray.org』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く