Разное околотехническое:

https://news.1rj.ru/str/extern_world (тот самый бежавший из России математик Богатов, сидевший за тор-ноды)
https://news.1rj.ru/str/peterblog (чей-то личный бложек, кажется какой-то рок стар, но это неточно)
https://news.1rj.ru/str/myobrechenychannel (единственный подкаст, который смотрю, когда нормальные люди туда приходят)
https://news.1rj.ru/str/techsparks (попсовые новости, но не особо мерзкие)
https://news.1rj.ru/str/singulary (ещё попсовые околотехнические новости от кого-то известного кажется)
https://news.1rj.ru/str/globchan (ещё попс)
https://news.1rj.ru/str/lovely_it_hell (явно управленец какой-то, но техническое ещё проскакивает)
https://news.1rj.ru/str/imaxairu (хз зачем слежу, душа болит за них, сам канал невыносимо скучный)
https://news.1rj.ru/str/techchsh (картинки, некоторые полезны)
https://news.1rj.ru/str/shitsch (почти мемы)

ИТ-Мемасики:

https://news.1rj.ru/str/cantbeparsedinreasonabletime
https://news.1rj.ru/str/ntwrkmms
https://news.1rj.ru/str/minicomcn (телеком-коты!11)

Датавиз-релейтед (история с прошлой работы, может кому чо тоже интересно):

Дизайнерский спектр:

https://news.1rj.ru/str/data_csv (блог коллеги, лайк, шер, репост)
https://news.1rj.ru/str/chartomojka + https://news.1rj.ru/str/interactivenews (блоги бывшего коллеги)
https://news.1rj.ru/str/dataart11 (тоже из инфографической тусы)

Аналитический спектр

https://news.1rj.ru/str/dashboardets
https://news.1rj.ru/str/revealthedata
https://news.1rj.ru/str/rockyourdata (босс команды визуализации в Яндекс Go, большая шишка)
https://news.1rj.ru/str/datalytx (начинающим про питон, как и то что ниже, сам не читаю, посылаю ссылки юным питоняшам, когда спрашивают про войти в айти)
https://news.1rj.ru/str/python_in_depth
https://news.1rj.ru/str/init_python

Застрявшие между:

https://news.1rj.ru/str/nastengraph
https://news.1rj.ru/str/visualize_it

Генарт:

https://news.1rj.ru/str/mathimages
https://news.1rj.ru/str/karpik_realtime
https://news.1rj.ru/str/gen_channel
https://news.1rj.ru/str/sgryob

As you start to ponder the implied ethos, the stranger it gets. Would you like engineers to be passionate as they design new bridges? Would you like a surgeon to be passionate as she operates on you? Would you like judges to be passionate as they pass sentence on your friend?

I'd like such people to care about their vocation, but I'd prefer that they keep a cool head and make as rational decisions as possible.

Why should programmers be passionate?

I don't think that it's in our interest to be passionate, but it is in employers' interest.

(c) https://blog.ploeh.dk/2021/03/22/the-dispassionate-developer/

Extending web programming beyond the browser is not a novel idea. Indeed, we have done that with moderate success in our “Node.js” project. But over a decade later, we find server-side JavaScript hopelessly fragmented, deeply tied to bad infrastructure, and irrevocably ruled by committees without the incentive to innovate. As the browser platform moves forward at a rapid pace, server-side JavaScript has stagnated.

(с) https://deno.com/blog/the-deno-company

Since functions and data structures are completely different types of animal it is fundamentally incorrect to lock them up in the same cage.

(с) https://www.cs.otago.ac.nz/staffpriv/ok/Joe-Hates-OO.htm

The great software developers, indeed, the best people in every field, are quite simply never on the market.

….

The corollary of that rule—the rule that the great people are never on the market—is that the bad people—the seriously unqualified—are on the market quite a lot.

(с) https://www.joelonsoftware.com/2006/09/06/finding-great-developers-2/

I think learning how to translate problems and solutions into type theory should be a core skill of any senior developer. Instead of looking at the industry and seeing a churning sea of novelty, one sees but a polishing of old wisdom.

(с) http://www.pathsensitive.com/2021/03/why-programmers-shouldnt-learn-theory.html

Its downside: in my personal experience, mechanized verification outclasses even addictive video games in its ability to make hours disappear. As much as programming can suck people into a state of flow and consume evenings, doing proofs in Coq takes this to another level. There’s something incredibly addicting about having a computer tell you every few seconds that your next tiny step of a proof is valid.

(с) http://www.pathsensitive.com/2021/03/why-programmers-shouldnt-learn-theory.html

Pencil and paper are the best programming tools and vastly under used.

(c) https://chriskiehl.com/article/thoughts-after-6-years

Unix survives only because everyone else has done so badly

(c) UNIX-HATERS Handbook

Прекраснейшая находка от https://news.1rj.ru/str/oleg_log/4537

Where Do Bugs Come From? Bugs come from developers.

(с) Paul McKenney's parallel programming book

https://mirrors.edge.kernel.org/pub/linux/kernel/people/paulmck/perfbook/perfbook.html

Приехала голубушка!

Haskell has a low floor but a stratospherically high ceiling.

(c) SPJ в предисловии к книге Брагилевского

Never, ever expect hackers to be able to read closed proprietary document formats like Microsoft Word or Excel. Most hackers react to these about as well as you would to having a pile of steaming pig manure dumped on your doorstep. Even when they can cope, they resent having to do so.

(c) http://catb.org/~esr/faqs/smart-questions.html

Much of what looks like rudeness in hacker circles is not intended to give offense. Rather, it's the product of the direct, cut-through-the-bullshit communications style that is natural to people who are more concerned about solving problems than making others feel warm and fuzzy.

(c) http://catb.org/~esr/faqs/smart-questions.html

Mark’s pyramid illustrates how fundamentally different the role of architect compares to developer. Developers spend their whole career honing expertise, and transitioning to the architect role means a shift in that perspective, which many architects find difficult. This in turn leads to two common dysfunctions: first, an architect tries to maintain expertise in a wide variety of areas, succeeding in none of them and working themselves ragged in the process. Second, it manifests as stale expertise–the mistaken sensation that your outdated information is still cutting edge. I see this often in large companies where the developers who founded the company have moved into leadership roles yet still make technology decisions using ancient criteria (I refer to this as the Frozen Caveman Antipattern).

As an architect, focus on technical breadth so that you have a larger quiver from which to draw arrows.

(c) http://nealford.com/memeagora/2015/09/08/knowledge-breadth-versus-depth.html

If this is the solution, I want my problem back.

(c) https://nosystemd.org/

Suppose for a moment you are a computer programmer in a large company. You studied computers because you're a technology nut and you genuinely enjoy working with the machines. You do a great job for which you're rated highly every review period. Eventually, as the computer department grows, someone is needed to manage it, and since your record is outstanding, the position is offered to you. Well, for one thing, you may have no managerial skills, which means, as Dr. Peter has pointed out, you will be on the verge of reaching your level of incompetence. But even worse than that, you may not want to be a manager, because you know being a manager has to do with records and reports and people and problems, and you may never get near a computer again.

You can, of course, refuse the promotion, but if you do, you'll have limited both your salary potential and your standing in the company. According to the rules of the hierarchy, your current job has a ceiling, and if you want to rise, you have to go on to something else. This leaves you with two choices, each stifling enough to promote Burn-Out: Either you go ahead and spend the bulk of your time doing work you dislike, or you remain where you are and feel inadequately compensated for your outstanding skills. One more "Catch-22" the system hands out.

(c) Burnout: The High Cost of High Achievement. Freudenberger, Herbert, 1980

Overmechanization dehumanizes us. Man used to be the most powerful, highly-developed species. Now machines are.

(c) Burnout: The High Cost of High Achievement. Freudenberger, Herbert, 1980

Irreducible complexity. That nine-syllable phrase is, itself, irreducibly complex. It's over half a haiku. It's hard to talk about systems like this, and it's easy to wish that they were easy. Just keep in mind that unless (like Wiki) you can describe its entire operation in a few sentences, it's probably more complicated than you're giving it credit for.

(c) https://sites.google.com/site/steveyegge2/nonesuch-beast

На данный момент “Сбер” говорит нет, но мы приятно удивлены, что это вообще работает.

(с) https://www.cnews.ru/news/top/2021-12-13_sberbank_vyyavil_katastroficheskoe

Everyone fantasizes about what they would do with some sort of amazing power they don’t have. Be that power to rule a nation, be a billionaire, be famous, be a virtuoso or be able to fly and punch people with super-human strength.

The problem with software developers is that they get to act out those fantasies too much. Software is a very equalitarian medium. You don’t need to be Facebook to build a social-media platform that can support “Facebook scale”… but you’d be wasting your time building it. Facebook’s magic consisted in being able to acquire billions of users, scaling the system was the easy part.

(c) https://blog.cerebralab.com/Stop_future_proofing_software