einpoklum
https://en.wikipedia.org/wiki/Em_(typography)
it seems the width of an M should be exactly equal to the x-height in points (IIUC).
Also, whoever said that fonts intended for a terminal need to be narrower? Some terminals have narrower chars, some wider. And terminal emulators often allow for multiple char aspect ratios - e.g. via bitmap fonts of different aspect ratio.
Anyway, the typeface looks interesting, but I would have liked for the creators to compare and contrast it with existing (and popular) monospace / terminal-oriented typefaces.
Digital information and toner/ink on paper will not last nearly that long.
Maybe humans of this age should be curating some etching on stone or even more durable materials, to record some of our history for posterity?
As a senior (of sorts), even though I don't quite rush to code, I often find myself starting to code something 'naively', while my understanding is lacking (typically in a tangled, inconsistent and poorly documented codebase). But what probably sets me apart from juniors is how I handle getting stuck, or rather what it means for me to try to "fix things". I spend time thinking about what I've discovered that has gotten me stuck, what I must take into account, and how I should alter my approach (or refactor the existing code to be more accommodating).
Sometimes I manage to formulate ideas apriori that reduce the frequency of my getting stuck, and/or the extent to which I need to backtrack. But - not always.
Ah, that's only true if whoever is in charge is willing to _have_ a bottleneck in reviewing. In some software development groups, there is a strong pressure for reviews to pass, i.e. expectation that reviewers approve; and the notion of veto is not common, so that if some reviewer objects, the implementing developer can find others who would be willing to accept, bypassing the objections. Also, few people are willing to conduct long reviews of a lot of code, and even less people are willing to read multiple comments in a long review of a lot of code.
Now, in some projects, there are only one or two "owners" or "marshals" for some areas of the code, so they can apply a strict standard if they want to, but - their time is limited, meaning that long LLM vibe-pull-requests are likely to either be ignored for a long time or rejected off-hand.
I have many years of the experience of of raising concerns, criticism and objections in reviews
My experience is that maintainers cannot do this. Or rather, that it is useless.
The bottleneck has never been the writing of the code. It's all the rest that takes the majority of the time. Of course, it is often the writing which lets you expand your understanding or your awareness of challenges and pitfalls, which then puts you back on the drawing board.
... but his government does support the ICC prosecuting Russians, on behalf of Ukraine, even though none of the two states is a party to the Rome statute / member of the court.
[1] : https://www.salahadawi.com/hacker-news-ai-detector/49946567
Also, I bet the whole blog post's worth would flash through the author's mind within all of 10 seconds whenever they were reminded of the possibility of taking the course. It takes both patience and self-discipline to put it all on paper like that.
Great blog post! Makes me want to take an EMT course :-)
No, we are not. Sure, there is a lot of slop-coding/vibe-coding going on, but not much of it in serious code. In my experience and to my knowledge.
Of course, I encounter the opposite problem with humans: They often don't bother to write proper commit messages; and many tend to squash them in favor of giant single-commits which just say "Implemented feature #123".
Also, on a semi-related note - there is the legality of gambling, the legality of running a gambling operation, and the legality of doing so for pecuniary gain, and it is possible for just part of these three to be illegal.
Some insights:
* There is sooo much space debris! Dead sattelites and rocket bodies
* Starlink put up a hell of lot of satellites, too.
* There is a pretty dense sphere of items around the earth at geo-stationary orbit, a bit like a mantle; but most of all in a circle on that sphere.
* Grapes are great snacks
* Grape juice is tasty (and you dilute it if it's too sweet)
When they're available, I buy both, quite frequently. I don't like alcohol though - never developed a taste for it; so, no wine for me.
Actually, we don't know that. The meaning of volatile is rather subtle
It is less pain than for most other languages, except for C. The pain is in exposing a C API for your C++ code. Then you build a library and you're set - because basically every language has the ability to call C code. Python, Rust, Java, etc. etc.
And then, on the other hand - I really doubt GP's map beats a vector, with all of those pointers bins and stuff, in a non-contrived benchmark with 10 elements.
Finally - it's not either-or: There are better hash maps whose memory is sequentially allocated and/or are otherwise cache-aware. And there are data structures geared towards parallel execution on multiple threads; and towards SIMD; etc. etc.
Yes, Android is a rather Google-ified experience, but there is life outside of Google. Let's live it.
I imagine:
* Massive budget overruns
* Year and year of delays
* It ending up wasting more energy than it produces, or just not working, period
* Politicians disclaiming responsibility and blaming it on "the AI"
* The contractor companies profiting immensely over the entire period, and ending up not having to worry about maintenance, warantees, etc.
That is essentially impossible, since if your pored over individual lines, your scrutiny cannot be razor sharp. There are few people who can pore over code with razor-sharp scrutiny (and different people are better at scrutinizing different aspects).
> Even back in March, you could tell it "give me a function that adds two numbers" and you could be 100% confident that it would write the correct function.
I am doubtful that this is the case. Even that supposedly-naive example is not as trivial as you might imagine, when you consider overflow, defined vs undefined behavior, and floating-point representation details. And you can't be confident like that about a human either.