Víáćéśłáv

Yet another DevOps engineer

[Леонидыч @El_Staino]

Жена сказала что хочет "реорганизовать" мой ящик с бельём но я обучен в корпоративном лицемерии и понимаю что это означает на самом деле. Массовые сокращения.

[alon @alonzuman]

having a wife is crazy cuz its like claude code but it prompts you instead

[worm (extra wormy) @wormymcwormersn]

drinking $1200 worth of cappuccinos at the dealership to cancel out the repair costs on my car

[Peter @peter]

things went from token maxxing to token budgeting real quick

[Víáćéśłáv @Daemonics]

@VSimileac @ChurchillPath Чё за сад?

[Víáćéśłáv @Daemonics]

@userdie Закон квадрата-куба

[Dave - Not Allowed Back at the Try-N-Save @davetulsa]

The AI journey at my company. It is a very, very large Fortune 500 company

1. Use AI you idiots
2. You aren’t using AI enough so we’re monitoring your AI usage and we’ll fire you if you don’t use it every hour
3. STOP USING SO MANY TOKENS ITS VERY EXPENSIVE

[Víáćéśłáv @Daemonics]

@varlamov Привет, чем занят?

[尸̢̖̞͕͉̟̯͎̘͛͘͢͟͢͠ 米͚̪͓̮̜̤̗̠͛͠͝͞͠ @lovedata]

Все нормальные люди: мы используем килограммы и километры
Американцы: мы слабоумные и используем фунты и мили
Канадцы: когда я родился, я весил 3,5 кг, сейчас вешу 150 фунтов, рост 5'6". Дом у меня 1 200 кв. футов, участок 1/4 акра, но на 3,2 метра от дороги земля общая. Замешиваю тесто из чашки муки и 250 мл молока, ставлю в духовку на 350F. Ещё купил полтора кило курицы по 10 долларов за фунт. Погода? +20С.

[Lev Walkin @levwalkin]

— У меня два типа знакомых сейчас. Одни в AI стартапах, а другие — лечатся от психических нарушений.

[Víáćéśłáv @Daemonics]

@Paulina_SPb Начинал как все, с автодополнения, потом перешел на вещи потяжелее - консоль, MCP. Дальше уже выхода не было, после агентских пайплайнов мало кто способен бросить...

[Eric Karl Hontz @eric_hontz]

The Russian language is beautiful

[Víáćéśłáv @Daemonics]

@Paulina_SPb @sparklingbomb @zhdite Живи

[sauce @jimbobrays_]

montreal is beautiful bc if you speak english they get annoyed and if you try to speak french they get annoyed and speak english back to you

[Víáćéśłáv @Daemonics]

@dolboebinusa Легально живущим более года - можно

[Víáćéśłáv @Daemonics]

@dmitrij_kozlov - разбить класс на несколько если разросся
- миграция без даунтайма
- могут быть разные таймзоны у кастомеров
- IaC, не надо вручную лазить в кластер
- не копипастить тупейший аод между классами

[дед Жень @dedzhenj]

Хозяйке на заметку.
Если у вас освободилась хорошая баночка от джема, салата или ещё чего-то, выбрасывайте её нахуй! Коварные баночки заполонят ваш дом.

[Nic Barker @nicbarkeragain]

To be a little less vague, I suspect that we're likely (not certain, but likely) to be entering into a period of unprecedented software degradation, and we're going to be seeing an increasing frequency of outages like this across many high profile products.

But IMO the cause is actually not just the-one-thing-that-everyone-is-always-talking-about, it's a number of things that have all been bubbling away at just below critical levels for a long time. Some of the things off the top of my head:

- Poorly designed / optimised software has been getting a free ride on hardware improvements pretty much since the invention of the computer. That chapter is now coming to an end, and will only be worsened by the enormous industry-wide pivot to producing & innovating on AI specific hardware, rather than general purpose CPUs etc.
- The ZIRP era created a temporary suspension of reality in our industry, and now that it's ended we need to deal with the hangover. Companies that spent years making no profit, paying extravagant compensation to employees / shareholders and giving away server time for free are now pivoting into extraction mode, which is putting further pressure on their low quality software. QA is being laid off, hardware budgets are being reduced, timelines for shipping features are becoming more aggressive, etc.
- The enormous amount of free money incentivised too many new people to join the industry too quickly. This has led to an abundance of poor quality education programs (bootcamps, uncertified colleges etc) and an influx of people into the industry who frankly aren't interested in programming. If you compared the average person in the industry now to 20 years ago, I suspect the difference in motivations would be stark. I'm not saying it's these people's fault necessarily, it's simply an inevitable result of the absurd compensation / performance expectations ratio that our industry has enjoyed for the last 15+ years. Working for a tech company has also become socially prestigious, which further adds to the problem.
- Because computer programming was once an incredibly niche area of interest, many of our fundamental systems are built on trust. We're now starting to see that if systems like open source, public supply chain, discussion spaces, education etc become flooded with bad actors, we have no real mechanisms to deal with them.
- Our hiring / recruitment pipeline has totally misaligned incentives. Even before the AI resume / AI HR-filtering arms race disaster that we're experiencing now, the widespread adoption of the leetcode style interviews IMO selected for a very narrow personality type, and filtered candidates that would have made great contributions to the industry long term.
- The pivot from purchasing long term stable releases of software, to paying a subscription for constantly updating software has done huge damage to software quality as a whole. Companies have lost their incentive to get their software "right" because they can just "fix it later", and for the consumer - you can't just go back to the version of github that still works because the new one has problems.

This was all happening well before AI entered the picture. I won't belabor the point because there has been endless discussion about it. But to me personally, there are two additional and deeply worrying problems with AI code generation.
- It's undeniable at this point that it negatively affects the people who use it. It stops juniors from getting better, and it burns seniors out and makes them hate their jobs. Like it or not, humans are still the core of this industry, and I don't see this ending well.
- It's completely unfit for purpose in the most important, high-stakes situations. One of the reasons that we excuse all the small errors it makes, is because it's low effort to type "do it again and fix this bug". That kind of thing doesn't fly when you only get one attempt because a mistake results in data loss or an outage. The damage is done.

All the above has led to a silent exodus of many of our most experienced and impactful people. There are so many amazing programmers who made enough through stock options / compensation that they didn't need to work anymore, and were only doing it because they enjoyed it. Many of these people have just quit the industry and switched to doing hobby projects in the last 5 years. These are the types of people who have the experience and foresight to prevent the types of outages that we're seeing at github today.

It's very easy to assume that the proverbial straw that broke the camel's back is entirely to blame here. But I think it's a reckoning that has been on the horizon for a very long time.

[Jessie Frazelle @jessfraz]

today will be known as the great april 27 github outage