Our mission is to make access to new ideas, experience and trends comfortable for IT specialists by providing professional conferences combined with festivals. We truly believe that our conferences drive development of IT community of Ukraine; set up creative atmosphere, filled with useful and high-quality information, where every moment can become a turning point in one's professional career and be the source of inspiration on the way to achieving goals. Our events are not just conferences. They are places of mutual education, inspiration, and growth.
13:01 Нихрена не понял. Как тест может создать сессию (т.е, на сколько я понимаю, открыть браузер - get(url)) на одном инстансе ггр, а потом вдруг сделать запрос на другой?
Basically boils down to "write JS functional and not OOP" which is ok if you can, but its really unfair to say you can do anything functional. There are strong cases for OOP and good programmer should always consider both approaches when solving problem.
Уши режет "руинглиш". Намного лучше, когда говорят либо полностью на английском, либо полностью на русском. Почему нельзя, например, сказать поддерживать проект, вместо сюпортить проект... Звучит как женщина из видео, которая даёт интервью в магазине и непонятно, на каком языке она говорит...
There is a lot of good advice here. However, I think he is going too deep into the "don't use it" approach. The reason arrow functions have an arrow is because of .map, it's where we use it the most. He is probably also in the minority against TS -- people use it and like it for good reason.
5 месяцев назад
"I need the freedom to express myself" - he makes fun of this argument for differing code style, but it honestly does make sense. I've seen code that was written a certain way, and the way it was written expressed to me some interesting idea about how to interpret or understand the sort of code that was written. For example, I once saw code with this unconventional syntax: ```javascript someObject. some(). chaining(). pattern(); ``` We're used to seeing the lines delimited behind the `.` operator rather than following it. I asked who I was working for at the time about it and they told me javascript used to disallow delimiting lines before the dot (or before something that makes it obvious the statement is continuing, almost like how you'd use `\` to escape a line-feed in bash). So that at the very least is a piece of history I would not have learned if somebody updated the code style. Another interesting idea expressed in this formatting is that the last character of each line tells you something about the next line. Hey, that's kind of valuable. It's through this idea that I came up with my own unconventional syntax - bare with me, I'll explain: ```javascript someObject .some() .chaining() .pattern() ; ``` By wasting an extra line and making the code look weird, this actually drastically improves readability. You can scan down the source code in a vertical line without having to collect knowledge about everything off to the site to find out where callbacks are closed etc. Honestly though, I think we shouldn't have to write syntax when we could instead have keyboard-driven structured data editors that only allow inputting valid code, which present the code to you in a way that takes advantage of the visual cortex a little bit more.
Nice lecture! This lecture not long before the war in Ukraine started, you'd almost forget how good the computer scientists/devs from Ukraine are with all the focus on that war... Some of my former colleagues (in the Netherlands) are from the Ukraine, so I worked with them for years... Hope it ends soon, and preferably Ukraine gets its whole country back.
Докладчица молодец: заранее приготовила тексты issue, UI, классы... Чтобы на ерунду время не тратить. Очень ценю такой подход. А вот митапы skillbox раньше чаще всего попадались. Там докладчики тоже код пишут в реальном времени, но фигарят без какого-либо плана и полдоклада выбирают названия для методов. Часто очень так.
Есть много спорных моментов, как относительно подходов, так и реализации. Паразитная нагрузка на базу для снятия тамстампов, излишняя сложность организации нагрузочного тестирования. Достаточно было обложиться мониторингами на каждый сервис, проверсти изолированные тесты, и один общий интеграционный
It will be very hard for C# to truly compete with "High Performance scnenarios" like needed in embeded systems but this might be sufficiant for game dev. C# Unity use to suck so hard and they have come a long way up. That one part about "array of structures" made it worth it to watch. There is one very important point he missed though... --> .Net introduced a new heap section called "pinned object heap". It avoids fragmenting the heap which is the problem when temporaly pinning arrays with "fixed" statments, and is perfect for deeling with buffers in unsafe context. Although it remains significantly slower than static and unmanaged memory, I have high hopes than one day we will be able to pin complex objects and not only primitve array data types. PS : If your a web/cloud dev I might have wasted your time beg my pardon :'P
Not using `this` seems to me quite extreme. Sure, if you do FP you probably don't need it, but that's not for everyone and for every project. Not liking fat arrow fn just because of its looks is not a great argument. And if you are not a die hard FP fan, `class` is actually a very useful construct. So I am not sure a lot of the stuff that Douglas presented is anything more than his personal preference.
Why are you presenting the English version - yet speaking runglish -- sounds terrible.. I have been a professional Sr QA Analyst for 25 y in USA.. Never heard nonsense like this before..
Success is exchange of knowledge and ideas to learn from each other and applying together. Organisation is not a school classroom where goal is individual to achieve. It is obvious if we think of ourselves and declare what is best but take a tour outside the window and imagine they are infinite stars who I think would understand what language thier words should have gone through until they join us and I think we are not yet in advance proportion to meet their numbers. I believe in learning what I lack no matte what. Writing, shaping, applying and computing should be rethink to understand in each deeply and collective and cooperative work need nothing else but communication to see what we or the organization want.