Traun

@dotdump @quantum_nomad_ Поиск, марки, номера строк - куда более точные и быстрые способы навигации. Но миникарту все равно можно добавить

@quantum_nomad_ нет, не быстрее ни миникарты ни нормальной полосы прокрутки, какая там может быть навигация... через поиск и по закладкам прыгать разве что

в битве VIM vs GUI IDE есть один простой критерий выбора победителя лично для вас если вы больше пишете код чем читаете то vim-образные редакторы имеют преимущество в виде полной свободы от мыши но если вы больше читаете и смотрите на код то GUI выигрывает и будущее за вторым.

@dotdump @quantum_nomad_ @goyilaxiecle Все описаные задачи решаются одним LSP, не нужны никакие сотни плагинов. Навигация по синтаксическому дереву, всплывающие подсказки и даже рефактор кода на множество файлов. Удобство хоткеев вопрос личный, но как по мне `y+<scope key>` > `<select scope> + Ctrl+C` `p` > `Ctrl +V`

@quantum_nomad_ @goyilaxiecle сотни плагинов требующих сотни часов для того чтобы с ними разобраться и всё равно всегда будут задачи которые удобнее делать мышью и горячие клавиши недоступные в терминале даже банальное копирование в буфер человеческими кнопками там невозможно

@NaMi____NaMi Даже с wayland x11 никуда не денется, не просто так ведь существует xwayland

Признаться честно мне нравится делать удобные небольшие (sic!) GUI именно на голом X11, без Qt/GTK/FLTK/etc. Чистая Сишечка. Всё просто. Да, жаль, что с появлением и распространением Wayland-а старые добрые иксы возможно уйдут в прошлое.

@teej_dv - Compile time type deduction - `maybe` return types by default - platform independent primitive type sizes

whats your favorite type system feature in a programming language? it can be an unused lang or whatever, just something cool that you think other languages could be doing if it they were designed w/ it from the start ... definitely not making my own lang ... do not tell prime

@SyntaxError2505 @ChShersh It's no longer 2000s, ez win

@ChShersh Of course it is. Go debug templates

I still believe Rust and C++ devs can be friends

There was a point where my Linux install was several partitions, each with a different filesystem, stitched together. I had ext4, f2fs, btrfs, xfs and jfs. This became really funny when Windows update later wiped my partition table

@filpizlo @segun_os_ From personal experience extensive babysitting is still required to produce modern idiomatic c++. Also the token consumption is quite .. suboptimal

@segun_os_ Even older models are fantastic at C++

you literally cannot vibe code c++ char is an 8 bit string that can also be an unsigned 8 bit int depending on how you use it. the level of precision required to write c++ is too high for vibecoding. there are just too many quirks in the language.

@0xfe0d Поздравляю!

Сегодня был тот ещё денёк! Не вдаваясь в лишние детали, Тимофей Антонович прибыл!

@dotdump hot reload

мы недооцениваем тот факт что программировать можно непосредственно взаимодействуя с состоянием программы и всеми загруженными данными а не только описывая последовательность действий и затем наблюдая что получилось когда всё отстрелялось правда так можно только в Clojure

@dmitrii_redkin @lindaoneesama @vpn_liberty Не преступный а приватный. Какие-то умыслы придумывать пошли ещё

@lindaoneesama @vpn_liberty Смысл не в наличии или отсутствии чего бы то ни было (тем более, что логи на самом деле есть), а в том что инструмент изначально рекламируется как преступный, а значит создавался именно ч преступным умыслом.

В Европе ликвидировали анонимный VPN: у First VPN изъяли 33 сервера в 27 странах В операции участвовали силовые структуры 18 государств, среди которых Франция, Великобритания, Нидерланды и Швейцария. Домены First VPN (1vpns com, 1vpns net, 1vpns org), а также .onion-версия в сети Tor, заблокированы — сейчас вместо сайта отображается страница правоохранительных органов. По данным «Европола», First VPN позиционировал себя как сервис «вне юрисдикции» и обещал полную анонимность без сотрудничества с властями. ________ Вот вам и сами думайте что

@rfleury @DJ_CURFEW When I see these posts from Ryan, I already know that there's some AI snakes oil shilling in the OP. Like a mark of quality but in reverse

@DJ_CURFEW Nobody is buying it. Delete your account

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

@_bravit благодарствую

@TraunQuilizer Не, ну в принципе тут KotlinConf сейчас, но я приехал не на неё, а чтобы по рабочим вопросам пересечься с человеком, который приехал на неё.

Сейчас проснулся по будильнику и минуты три не мог понять, где я, зачем проснулся, и что вообще происходит. Но уже прогрузился, еду в любимый Схипхол. Мюнхен, жди!

@_bravit @alexott А, таким иногда любая линия грешит, особенно, если на магистраль, например, какой-нибудь олень (настоящий, с рогами) выйдет. Увы

@TraunQuilizer @alexott Нет. Например, уехал на такси вместо электрички, которой не было целый час, а время прибытия десять раз откладывалось каждые пять минут на пять минут.

Чёт странно: электрички по расписанию ходят, только что велосипед чуть не переехал. Я точно в Мюнхене?

@_bravit @alexott Уехал во фрайзинг вместо аэропорта?)

@alexott Рассказывай! Я редко в Мюнхен езжу, но даже у меня есть куча историй с этими S1 и S8!

@NaMi____NaMi но вообще поддерживаю, давно пора

@NaMi____NaMi tl::expected

Когда я приду к власти, я законодательно обязую все обновить компиляторы! Ибо это пиздец. Особенно без std::excepted

Ден Симмонс предсказал что когда мы проваливаемся в подпространство дойчеебанвское и якобы поезд задерживается, то на самом деле ии использует процессорные ресурсы мозга (дойчеебан как мы знаем проебывается всё чаще). Молодец мужик👍

@richgel999 If you want "safe" code, don't introduce [] operator to the codebase. It is raw access by definition. You want better safety, use iterators for gods sake it's 2026

C++ memory safety: “use modern C++”. Okay so let’s check out std::span. Surely it’s safe right? No, it doesn’t bounds check until C++26 (maybe). The lang is unsafe.

@dotdump @DanielMeows У терминалов для этого встроенные шорткаты есть, даже не нужно убирать руки с букв Ctrl+R поиск по истории команд Ctrl+P прошлая команда Alt+B/F прыгать по словам etc

@DanielMeows а как в консоле список последних комманд листать или двигать курсор по словам (с нажатым Ctrl)

чисто думаю в последние 15 минут что в средний ноутбук легко влезла бы обычная клавиатура с нормальными стрелками, блоком PageUp-PageDown, Home-End и даже пустым местом для постукивания пальцами если бы они не пытались туда вмандить этот свой ебучий хуеблядский нампад