as a guy from Ukraine, and who familiar with group of people who receive paid "grants" i can say. This grants paid for political destructive groups. This is not about science, research, rights, whatever. I have war outside of my window. All "granted" organizations doing maximum efforts to lead much more deaths of ukranians as it possible. They doing maximum problems and political problems as they could. All sectors from IT, from lgbt, from different science grants and so on. All works in the same one road to weak Ukraine and kill as much people as possible. So yes, earlier i did not even imagine that grants it's some kind of salary. But now i have clear understanding for what and why the "free and easy" money paid for. These money paid not for purpose they initially paid. This is fund for political destructive organization covered by fake title.
C is an achievement that must be unlocked by programming in different other high-level languages for years.
Without this - C will be pointless lecture.
> Originally they were there to connect people and let them share in each other’s joy.
No, they looking for a ways how to easily and faster to fuck.
> They couldn’t measure joy, but they could measure engagement, and so they did.
> That measurement became their goal, and they focused on maximizing it.
Because this is social networks profit. Ads, and more people attached to some topic where can be shown an ads to these people. That's why and only that's why it is works like that. Nobody cares about principles. Only money. Power in money, a money is a power.
> What they didn’t understand was that negative, divisive, hate-inspiring posts get more engagement than positive, supportive, kind posts do.
For what do your country has intelligence and different defense structures?
Because it is very easy manipulate by people and do wars. Extremely easy to organize that and involve a lot of people to mass destruction events. Extremely easy. And i do not know (the same as you too) who is behind some kind of negative behind.
> . The algorithm didn’t care whether the posts brought joy or anger, it only cared about whether they brought engagement.
Because this is about ads and money. More people will watch ads more money social network will get. Easy.
> So in order to maximize engagement, the algorithm actively encourages and elevates posts that cause unhappiness among the platform’s users.
You said that? Is a bots with fake votes, SEO thing is not about manipulating data, opinions? Its easy to make fake accounts and promote hate as a wide interested topic, while it's not. Only social network know that.
> They join looking for support, or connections, to give back, or find meaningful relationships.
No, they looking for themselves reflected in the community.
> Measuring engagement doesn’t tell you if your community is happy, or healthy, or even accomplishing any of the things you were hoping it would accomplish.
Depends on a case. Some measuring engagement can prevent negative business processes.
> Knowing how much engagement you have doesn’t tell you how much value you’re getting
For that you have another metrics. Depends on a case. Registration, profit, grow, etc. Final countable results.
> Let’s bring this back to community building. We still want our members to be happy, right?
Who the fuck am i to let people happy? Happiness is subjective thing. I have no clue, no ability to make someone happy. The same as you, the same as anybody else. This is very agile thing depends on many factors and the most important wish to be happy and objective situation.
> So what should we value?
Does your community member even read or know about "values" at all?
Is it some kind of cult, or what?
----
I have a well known secret.
To get maximum engagement need to say that the white color is black color.
Water - is not a liquide, and planet earth is flat.
And then your "engagement" will go above the sky.
Just always need to split people, and say that one thing is not the thing what you used to think, it's another thing. totally vise versa.
Oh... Darling, exactly this you have done by saying:
"stop measuring engagement". And by this title invited to engagement a lot of people who forced to read all of your nonsense to one more time confirm that white is white, black is black.
I agree with the author. However, I need to do things that must be done now.
Because best code is the enemy of good code. Easy to fall to refactoring and lost everything in the end.
Good code is code that works and solves a problem right now.
Otherwise, we will not have clients waiting for a "well-polished" formatted product that is easy to read and maintain for us.
And that is the problem of the whole infrastructure.
We needed solutions for X, Y, and Z just yesterday.
And then, if it "shoot," we like idiots yearly fixing all problems that have been done earlier.
Speed is critical. More important than perfectionism or wish for well-structured, easy-to-read, maintained code.
Is that awful? Yes. I want my code to be good as it can be.
But is it possible to do it in a limited time when an urgent problem must be addressed? Nope.
And over time, we increase complexity, multiply complexity, and then leave because not able to maintain it anymore. That's why we touch different things while fixing everyday problems because we do not want to fix them later. Balancing complexity in future. But this is fake. This future never happen in 99% cases.
The biggest problem is that if we do not rush right now, there will be no tomorrow for the product we develop.
> Speed is critical. More important than perfectionism or wish for well-structured, easy-to-read, maintained code.
The thing is, poorly-structured, hard-to-read, unmaintained code is the enemy of speed. I don't think it's ever a good idea to go too far in either direction. If you spend all of your time on refactoring/cleaning up code, you never get anywhere in terms of functionality. But if you never refactor, you're development speed slows to a crawl, and making meaningful changes becomes impractical.
> The thing is, poorly-structured, hard-to-read, unmaintained code is the enemy of speed.
Sorry for debating with you.
But any modern code editor has tools which solves the problem of "well-structured" code.
What about "easy-to-read", this is depends on language, and the programmer.
I've seen so damn much beautiful code, with 1 character long vars.
And such code extremely hard to understand. The code is compact and beautiful.
But for understanding the code - required a lot of time.
I think, and my own experience proof that.
If you not in rush for finishing things just in time while the things actual - you lose. Always. And there will be no second or third chance.
That's why need to write how you used to write.
Only experience & practice give you ability to write good code.
Focusing on re-writting some code parts while fixing a bug - big problem.
If this re-writting thing does not change anything instead of "better understanding and better ability to read" - this is bad time wasting.
If you not in rush in developing things and doing right actions in right time while the problem or request actual - you lose. Always. Without second chance.
That's why need compromise and write shitty code for winning competition in short run.
And then, when you will have audience for your product, you can always fix here, and change there. Nobody will complain about bugs or issues until it leak personal data.
I'm not saying you should just do random refactorings. What I am saying is that if you are fixing something, and realize that you can fix it while improving the code at the same time, it is typically worth it. Obviously if the refactoring is a huge undertaking, it's not going to be a great idea to pair it with a bug fix. But if your are smart about it, you can usually keep the code base clean/well-factored incrementally.
The problem with "quick" fixes is that they often end up being slower, because hacking a fix into a complex code base often creates new bugs/problems, and you end up rolling back your broken "fix".
> Only experience & practice give you ability to write good code.
I agree, which means that always writing shitty code to get it out the door means that you will only practice writing shitty code.
Sometimes rewriting things allows you to fix things in multiple places at once instead of one at a time.
My coworker copy pasted a bunch of stuff into each page, so when I actually templated them I could fix the bug he had in every page, not just every time I find the bug
Emails - extremely cheap if compare with any other ads method.
Extremely effective, good to scale and gives much more results, that all known and tried ads networks with big budgets.
What about the topic -> all of that info related to 90% of users.
Most of normal casual users has one email, and all stuff mentioned in the topic.
Very rare cases when something else.
The list more about exceptions, instead of real life
I think this is one of the best languages that i ever seen before.
All interested by me concepts are covered, that open ability to write different complex logic for manipulating data.
WoW. Thank you very much for all of that! This is really great, and has powerful potential to become inner-script language for many different projects where must be ability to write some kind of macroses, scripts inside the main enveriopment (game engines, game emulators)
Good job! I feel that you have wide experience in scripting languages that developed inside some big project for inner purposes inside a big app.
Is the post joke? Are there any network technical who can explain that the packet can have different size and modified by different routers inside chain of path from source to destination? I mean some kind of absurd topic. And everyone instead of reading ethernet standard and teaching materials about this OSI level, start to debate about this thing.
if you had a router between you and the webserver you're accessing and it's MTU is 100 bytes then the largest packet getting through it is 100 bytes. The router will break larger packets into max 100 byte packets and send them through.
"This process is called fragmentation. Fragmented packets are reassembled once they reach their destination."
The default MTU for routers is 1500 bytes which is probably the 14-15kb limit was picked.
/it's been 20 years since i was really into networks so maybe things have changed with the default MTU...
