Reporters often get rumors or tips that it would be irresponsible, unethical, and legally risky to publish. A reporter might spend years chasing rumors only to hit dead ends because the people involved don’t want to talk — or because, as is revealed much later, they can’t talk due to ongoing litigation. Often, a reporter will choose to sit on a story because publishing it could risk identifying or harming the victims involved. These are frustrating but normal realities of the job, and sometimes it takes a tipping point (such as a public lawsuit) to make enough people finally feel comfortable speaking on the record. What some observers (many in bad faith, some perhaps not) are interpreting and shouting on Twitter as “Jason hid misconduct allegations” is in reality how journalism works.

Bitcoin’s price, no matter how robust, does not actually mean that bitcoin has become more useful for everyday transactions, or more widely adopted for payments since its 2022 crash. 

“In terms of actual real-life use cases, I don’t feel like anything has changed since its peak,” Erlam says. “It’s all belief in what the product can become as opposed to what it offers now.” 

Суспільство не має позитивних рольових моделей комбатанта. Немає перед очима тих, хто віддав батьківщині всі борги – і тепер насолоджується життям у тилу разом із дружиною та дітьми. Люди не бачать тих, хто міг би повернутися до рідного міста і гордо розповідати про власний бойовий досвід та досвід своїх побратимів. Єдиний доступний тилу опис військової біографії зводиться до фраз "пішов і загинув", "пішов і повернувся без ноги", "пішов і тепер безстроково воює".

Several employees adopted the term “toxic positivity” to describe the culture of the company, which discouraged criticism.

В умовах війни на виснаження та домінування оборони над наступом здатність одночасно тримати лінію фронту, забезпечуючи сприятливий баланс вибивання та поступово накопичуючи переваги над противником, і гарантувати стабільність та нормальне функціонування країни є набагато важливішим індикатором успіху, ніж швидке звільнення тимчасово втрачених територій.

Критично важливим періодом буде наступний рік-півтора. Саме в цей час у РФ мають почати наростати суперечності на тлі значного перерозподілу ВВП на користь ведення війни, а також почати вичерпуватися радянські запаси бронетехніки й артилерійських стволів, на які сьогодні значною мірою спирається РФ.

Put another way: I'd love it if people would avoid writing their
descriptions as "In this pull request, the Xyzzy driver error handling
was fixed to avoid a NULL pointer dereference".

Instead write it as "This fixes a NULL pointer dereference in .." or
particularly if you just list bullet points, make the bullet point
just be "Fix NULL pointer dereference in ..".

This is not a big deal, I realize. But I happened to try to rewrite a
few of these cases the last week, and I think simple and to-the-point
language is better. The imperative version of just "Fix X" is about as
clear as it gets.

Is this acceptable? Not really. Is it understandable? Absolutely.

Legacy tech is complicated. It’s one of the biggest barriers for organisations undertaking digital transformation

Just as with early typewriters, any “smart” solution would be prohibitively complicated or expensive to make. But what if the character following a carriage return was guaranteed to be non-printing? This would give the teletype a chance to catch up. And so teletypes undid the early convenience of typewriters, and Carriage Return became decoupled from Line Feed. The former key moved the carriage to the left, but stayed on the same line. The latter advanced the paper to the next line, with no horizontal movement. Sometimes, the Line Feed code would arrive after a carriage return was complete. Other times, it would come in the middle of the carriage returning, but the teletype could deal with those movements coexisting.

This is the origin of the CR/LF debacle that’s still an occasional problem for today’s programmers.