#Yegor Bugayenko

[nuttysaladtree]

You probably already know this: Sklyarov was interviewed last year (2024-02-25) by Yegor Bugayenko for the latter's podcast, Yegor256. The YouTube video description—according to a machine translation—has only the website of his employer, Positive Technologies, and his Russian-language Wikipedia article.

I did not find anything newer on Positive Technologies' website than a 2022 press release on his team's work on a Mitsubushi vulnerability.

I'm trying to reach Dmitry Sklyarov; does anyone have contact info for him?

[some-programming-pearls]

How to Pay Programmers Less

How to Pay Programmers Less

To create software, you need programmers. Unfortunately. They are expensive, lazy, and almost impossible to control. The software they create either works or doesn’t, but you still have to pay them, every month. Of course, it’s always better to pay less. However, sometimes they may figure out they are being underpaid and quit. How do you prevent that? Unfortunately, we can’t use violence…

[libr-tumbl-alternative]

Today's programmers offer more valuable skills than simply being able to hack algorithms and make data structures, says Yegor Bugayenko. . Powered by AutoBlogger.co

[newseveryhourly]

Today's programmers offer more valuable skills than simply being able to hack algorithms and make data structures, says Yegor Bugayenko. https://ift.tt/2oiOJxz

[ash71ish]

Hey Yegor Bugayenko thanks for the follow!

Hey Yegor Bugayenko thanks for the follow!

— Ashish kumar chaubey (@Ash71ish) May 27, 2018

via Twitter https://twitter.com/Ash71ish May 27, 2018 at 06:28AM

[ericvanderburg]

Yegor Bugayenko Joins @CloudEXPO Faculty | @Yegor 256 #Java #Cloud #AI #ArtificialIntelligence #DigitalTransformation

http://i.securitythinkingcap.com/QSQ0Fg #tech

[dragoni]

Yegor provides an A-Z summary. The real discussion are in the comments

Design Patterns are ... Come on, you know what they are. They are something we love and hate. We love them because they let us write code without thinking. We hate them when we see the code of someone who is used to writing code without thinking. Am I wrong? Now, let me try to go through all of them and show you how much I love or hate each one. Follow me, in alphabetic order.

Here’s a small sample

Abstract Factory. It's OK.

Adapter. Good one!

Bridge. Good one!

Builder. Terrible concept, since it encourages us to create and use big, complex objects. If you need a builder, there is already something wrong in your code. Refactor it so any object is easy to create through its constructors.

Chain of Responsibility. Seems fine.

Command. It's OK.

Composite. Good one; check out this too.

Decorator. My favorite one. I highly recommend you use it.

Facade. Bad idea. In OOP, we need objects and only objects, not facades for them. This design pattern is very procedural in its spirit, since a facade is nothing more than a collection of procedures.

...

Front Controller. Terrible idea, as well as the entire MVC. It's very procedural, that's why.

...

Iterator. Bad idea, since it is mutable. It would be much better to have immutable "cursors".

...

MVC. Bad idea, since it's very procedural. Controllers are the key broken element in this concept. We need real objects, not procedural controllers.

[dragoni]

You're a good programmer. I'm a great entrepreneur. This is a breakthrough idea. Help me build it. I don't have cash, but I will give you equity. Deal?

Yegor Bugayenko -  Good Programmers Don't Work for Equity

sweat equity is so wrong