Evgeny Veretennikov

460 posts

Evgeny Veretennikov

Evgeny Veretennikov

@evis_dev

Team Lead at Yandex Verticals, proud husband and father of three. Passionate about enhancing developers' lives and organizing Scala events.

Moscow, Russia Entrou em Eylül 2012
78 Seguindo31 Seguidores
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@mitchellh We actually do know. Hot code reloading is still alive in the BEAM (Erlang/Elixir VM). You can swap modules in prod without restarting.
English
0
0
0
69
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
Look, say what you will about it, but right click editing a PHP file in an FTP client with upload-on-save is still the tightest and fastest feedback loop I've ever had in my life. We actually don't know how to do this anymore as an industry.
English
205
143
2.7K
253.8K
Pavel Durov
Pavel Durov@durov·
🔥 This summer, Telegram users will gain access to the best AI technology on the market. @elonmusk and I have agreed to a 1-year partnership to bring xAI’s @grok to our billion+ users and integrate it across all Telegram apps 🤝 💪 This also strengthens Telegram’s financial position: we will receive $300M in cash and equity from xAI, plus 50% of the revenue from xAI subscriptions sold via Telegram 💰 Together, we win ❤️📈🏆
English
2.2K
3.1K
24.5K
2.8M
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@Ano4maly @ChShersh Also, you might not need to build huge public frameworks to do meaningful work. Even internal tools can have real impact and bring joy.
English
0
0
0
20
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@Ano4maly @ChShersh So here’s one possible path to working on frameworks and getting paid: 1.Join a large company. 2.Notice pain points in tools/frameworks you use. 3.Give feedback. 4.When there’s an opportunity — take it.
English
1
0
0
21
Dmitrii Kovanikov
Dmitrii Kovanikov@ChShersh·
Learning CS is much easier when you have 10 years of coding experience
English
33
47
1.8K
66.8K
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
Вас ждут: — 7 хардкорных докладов про Scala, ФП и JVM, типизацию и разработку бэкенда — Спикеры из Яндекса, Т-банка, BIOCAD, EcomTech — Круглый стол в формате открытого диалога — Нетворкинг и афтепати Увидимся на конференции 🔥 [2/2]
Русский
0
0
0
13
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
⚡ Приглашаем на конференцию F[Scala] 2024 30 ноября в Москве пройдёт ежегодная конференция по Scala и ФП от Яндекс Вертикалей. Посмотреть программу и зарегистрироваться можно здесь: yandex.ru/project/vertic… Для тех, кто не сможет прийти — будет онлайн-трансляция. [1/2]
Русский
1
0
0
17
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@lukasz_bialy @adamhearn @SethTisue Thanks for response! I think we’ll give Scala 3 a shot in our projects, and I’ll get back to you. When I tried it a year ago, there was a lot missing, but a lot has changed since then: cross-compilation support in Bazel’s rules_scala, better derivation in PureConfig, and so on.
English
1
0
1
76
Łukasz Biały
Łukasz Biały@lukasz_bialy·
Yes, but what it means is that 2.13 is not getting any new development beside urgent bugfixes, security patches and migration support tools. I can understand that 2.13 can be seen as a local optimum, a kind of sweet spot, but all new stuff is going to happen in 3.x, including new jvm features.
English
1
0
1
43
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@lukasz_bialy @adamhearn Thanks for wanting to help! Before figuring out how to make the migration easier, we would like to know if we would actually benefit from migrating, considering its cost. A clear plan for the end of life of Scala 2.13 would help with this.
English
1
0
1
86
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@lukasz_bialy @adamhearn By the way, opinions on migration in our case would be helpful. For instance, deciding not to migrate at all, or migrating gradually with low priority over the years, or just forgetting about it and never migrating.
English
1
0
2
46
Evgeny Veretennikov
Evgeny Veretennikov@evis_dev·
@lukasz_bialy @adamhearn Our company has 4M lines of Scala code in a monorepo on Bazel. Migrating to Scala 3 could take months, if not years. Our engineers feel comfortable with Scala 2.13, and tmp version mismatch could cause issues on its own. We're not sure if the benefits of Scala 3 are worth it.
English
1
0
4
138
Łukasz Biały
Łukasz Biały@lukasz_bialy·
@adamhearn What would make a difference in adoption of Scala 3 in enterprise in your opinion? Honest question.
English
5
0
3
469
Voytek Pituła 💙/💛/🖤
I just learned we reopened our Scala position! We are looking for three mid/senior Scala devs. If you're looking for a fully remote, well-compensated, functional Scala job, you know the drill. jobs.lever.co/swissborg?depa… As always, happy to answer any questions! We also look for Android Dev, Rust Dev and SRE :)
English
4
15
44
4.3K
Theo - t3.gg
Theo - t3.gg@theo·
Monorepos are the new GraphQL
English
86
28
937
190.7K