erik_seaberg

5 ms·

1.
by erik_seaberg 2y ago
It’s better to quote a reserved word than to be unable to use it.
2.
by erik_seaberg 2y ago
Seems to me the article focused on how they did this big job, rather than why.
3.
by erik_seaberg 2y ago
There are times when mistakes will cause more serious problems for customers. There are times when staff will be less available to aid recovery. A good strategy shouldn't deny these truths.
4.
by erik_seaberg 2y ago
Will the compiler infer that a lambda or a method ref implements Func with its exception type param, or do you have to rewrite call sites?
5.
by erik_seaberg 2y ago
Software demand skyrocketed because of the WWW, which came out in 1991 just before Python (although Perl, slightly more mature, saw more use in the early days).
6.
by erik_seaberg 2y ago
Deep work needs peace and quiet. This is getting hard to find in an open plan office, except late in the evening.
7.
by erik_seaberg 2y ago
This. It's so frustrating that sync.Map isn't generic and reusing the builtin map API is impossible.
8.
by erik_seaberg 2y ago
Boring repetition is a bad fit for the human brain. Working memory is very small. Mistakes per line are frequent. It wants to see patterns that are not quite there. Even when it works out, it's millions of times slower than having the
9.
by erik_seaberg 2y ago
I remember science news articles about cooling rather than warming. Newsweek had to retract at least one of theirs: https://www.newsweek.com/newsweek-rewind-debunking-global-co...
10.
by erik_seaberg 2y ago
Around competitive prices and terms rather than a monopoly.
11.
by erik_seaberg 2y ago
It might seem really unlikely any acquirer would ever sue, but if your big company has compliance auditors they will need to see something in black and white.
12.
by erik_seaberg 2y ago
The warning went at least as far as the inland side of Fremont, which seemed extreme.
13.
by erik_seaberg 2y ago
Pairing doesn't replace code review because the reviewer needs to see the finished branch with fresh eyes, unbiased by discussion and false starts, to know whether it's safe and clearly explained in writing for every oncall in the
14.
by erik_seaberg 2y ago
A "trusted team" pushing unreviewed code to prod is breathtakingly reckless. I don't trust anyone to do that. Not even myself. Please review my code, because our customers matter and so does oncall's peace and quiet. O
15.
by erik_seaberg 2y ago
I'm reminded of Bright's https://en.wikipedia.org/wiki/Empire_(1977_video_game) , a turn-based PvP strategy game. My friend's 1989-ish instance was sadistic enough to batch execute four turns per day. Eve
16.
by erik_seaberg 2y ago
Fixed pitch fonts and ASCII art are outdated; not even Dwarf Fortress relies on them anymore. You can sort of line up numbers, but you have to be careful to use U+2007 FIGURE SPACE (not U+0020 SPACE) and U+2212 MINUS (not U+002D HYPHEN-MINU
17.
by erik_seaberg 2y ago
This comes down to Postel's Law; they recommend liberally receiving what you conservatively cannot send. Also from RFC 2616 but not cited by the author: > This flexibility regarding line breaks applies only to text media in the enti
18.
by erik_seaberg 2y ago
The resources are 0.004% of the population of one wealthy country, who devoted themselves to shaping about 400 tons of stainless steel. Nothing constructive comes of starving a project that size, certainly not the global carbon sequestratio
19.
by erik_seaberg 2y ago
Escaping pollution is not a reason for going. Creating habitable areas on/under Mars is clearly harder than maintaining habitable areas on/under Earth. We have people who are much more motivated to do it and we might learn more fr
20.
by erik_seaberg 2y ago
Is there tooling to automatically transpile from other languages to this?
21.
by erik_seaberg 2y ago
Hundreds of programming languages set very high expectations, which should support groundbreaking ideas like Lisp style macros and multimethods, ML style pattern matching, Prolog style search and unification, and Smalltalk style metaprogram
22.
by erik_seaberg 2y ago
Static typing prevents reusing functions unless they're generic. The other option is to give up static typing and pass "all" everywhere, like a dynamic language.
23.
by erik_seaberg 2y ago
Google is famous for tough interviews and accepting a small fraction of applicants. I was impressed with everyone I met, and Pike's "incapable" statement was baseless and insulting.
24.
by erik_seaberg 2y ago
Half of my comments were "nit: consider blah blah" where I want it on his radar, but I approved anyway and if he declines I'm fine with it.
25.
by erik_seaberg 2y ago
Fitting a C compiler on a PDP-11 was an impressive achievement, but as a language it was a poor foundation to build anything reliable, and we still live with the consequences.
26.
by erik_seaberg 2y ago
I'd expect that because Promises are small Javascript objects while goroutines each get a stack that grows from at least 2 KB.
27.
by erik_seaberg 2y ago
f(g(), h()) can't work with MRVs, only f(g()). multiple-value-list, multiple-value-call, and quietly ignoring unneeded values makes them much more usable.
28.
by erik_seaberg 2y ago
Imagine Walmart telling all their customers "Come back tomorrow, maybe, we can't manage to keep any of our stores open. At least nobody is going to die."
29.
by erik_seaberg 2y ago
I remember someone arguing that disabling assertions in prod is like wearing a life jacket in the harbor but throwing it overboard going to sea. And Moore's Law paid for them years ago.
30.
by erik_seaberg 2y ago
We can pay for oncall availability, but rewarding outages and slow recoveries is a dangerous incentive.

More ›