kiitos

6 ms·

31.
by kiitos 1y ago
delegation of trust is an essential and unavoidable property of any system that serves a non-trivial number of human participants
32.
by kiitos 1y ago
keypair != human
33.
by kiitos 1y ago
> I look at cross core communication as a 100x latency penalty if your workload is majority cpu-bound then this is true, sometimes , and at best most workloads are io (i.e. syscall) bound, and io/syscall overhead is >> cros
34.
by kiitos 1y ago
> How do we reconstruct past memory states? That's the fundamental problem. reconstructing past memory states is rarely, if ever, a requirement that needs to be accommodated in the database layer
35.
by kiitos 1y ago
Within the Google codebase and in projects using Bazel, directory layout for Go code is different than it is in open source Go projects: you can have multiple go_library targets in a single directory. A good reason to give each packa
36.
by kiitos 1y ago
> the build graph -- the very thing that BUILD files define -- is the best place to encode [dependencies] in a programmatic manner. so the thing is that a BUILD file doesn't define the build graph, it approximates it -- the buil
37.
by kiitos 1y ago
> BUILD files give you a chance to encode the high-level architecture of your software project as a graph of dependencies that lives outside of the code. this is wild, the code literally defines dependency relationships at the mechanical
38.
by kiitos 1y ago
indeed, no idea why so many folks seem to think `bazel` is like some co-equal alternative to language-native build tooling/processes, it's a fine tool for certain (niche) use cases but in no way is it ubiquitous or anything approa
39.
by kiitos 1y ago
"event system" is any mechanism where events (readiness, completion, signals, GUI messages) drive control flow, restricting "event system" to descriptor readiness exclusively is the author's personal framing, not ex
40.
by kiitos 1y ago
there are just as many equally-qualified experts who have been consistently giving exactly the opposite feedback/signal, which you never seem to acknowledge or incorporate into your comments
41.
by kiitos 1y ago
for me the takeaway here isn't that sorting should use some smarter/better mechanism for inferring semantic intent from filenames, but rather that sorting should not try to infer semantic intent from filenames in the first place
42.
by kiitos 1y ago
you're right, i guess it's only negative if you think it's important for people to understand the code they produce, if that's not a concern for you then no problemo
43.
by kiitos 1y ago
> If they are playing a constructive part inside the organisation, at what level of notoriety and assholeness should the moderators pull the pin? in general, that's 100% up to the discretion of the owners/moderators (shrug)
44.
by kiitos 1y ago
what? private communities (which in this context would include any website that doesnt end in .gov) banning assholes, has no impact on the human rights of those banned assholes, it is not a human right that you get to have an account on a p
45.
by kiitos 1y ago
what do I find objectionable? > The first step to resist or undo Woke Invasion in your organization (or your psyche) is to thoroughly understand its creed Critical Race Theory, so as to uncover the fact that generally speaking woke disci
46.
by kiitos 1y ago
> There's a user expectation that photo20.jpg comes after photo3.jpg. my user expectation is the opposite i get what you're saying but it's not achievable in practice, at least not consistently
47.
by kiitos 1y ago
ls sorts filenames strictly lexicographically, comparing character by character, so e.g. "055436307" is compared as the characters "0", "5", "5", etc. so it sorts before "121134" because &qu
48.
by kiitos 1y ago
if you're spending anywhere near as many engineering hours "getting code to work" as you're spending "thinking" then something is wrong in your process
49.
by kiitos 1y ago
nobody in this or any meaningful software engineering discussion is talking about software projects that are 1000, or even 10000, SLoC. these are trivial and uninteresting sizes. the discussion is about 100k+ SLoC projects.
50.
by kiitos 1y ago
> If the thinking bit is your favorite part, AI allows you to spend nearly all of your time there if you wish, from concept through troubleshooting... What about if the "knowing/understanding" bit is your favorite part?
51.
by kiitos 1y ago
> do you not recognize that collectively, as a society, Nazis decided to attack Jews, trans, disabled, and others? ... in the end very few people think they themselves are evil. yes, I agree with you, that society made some pretty bogus
52.
by kiitos 1y ago
> https://srid.ca/unwoke i mean, this is a set of opinions and positions that are far beyond anything that could be called "moderate opinion[s] on gender representation" and are pretty uncontroversially terribl
53.
by kiitos 1y ago
the people talking to you are talking about something very different than simply "political beliefs that you disagree with" the appropriate level of capital gains tax at the 80th percentile is a political belief that you can tweet
54.
by kiitos 1y ago
> The problem is who gets to pick who is right and not? we all do, collectively, as a society > So yes, to protect those groups being persecuted (trans, minorities, and Jews alike) you need to protect the speech of abhorrent groups li
55.
by kiitos 1y ago
> The "fundamental distsys problem" here originates in the language level: the problem is the attempt to hide the existence of a network protocol from the application code. so the problem isn't about whether or not the app
56.
by kiitos 1y ago
i just don't use commits like you do, and that doesn't mean i'm being less careful or less thoughtful, or that my changes are worse than yours commits are what i say they are, nothing more or less
57.
by kiitos 1y ago
> But most Americans want the government reduced, facts not in evidence tldr: no they do not
58.
by kiitos 1y ago
> trying to make network calls look like local calls hides important details which distributed applications must handle, like latency and network instability. among many other concerns, yes https://en.wikipedia.org/wiki&#
59.
by kiitos 1y ago
> The argument here is that the reason CORBA failed is because it lacked the language-level concepts to make it work well, in particular strong asynchronous programming primitives and promise pipelining. i'm honestly not sure how to
60.
by kiitos 1y ago
> if you only use commits as some sort of help while developing, you might as well just squash them before making a PR. yeah for sure you want to squash-merge every PR to main, right? commits are just commits, there is no moral value to

More ›