Get Well

getwell

This has become a well-known practice or even a meme. When someone pushes code to production on Friday, there is a significant outage of all services, customers are angry, ratings are going down, and revenue is dipping as fast as one can imagine. Eventually, everyone will be brought back to their laptops instead of spending time with family and friends over the weekend. But how did we end up in this situation? If you look at this from a holistic approach, that makes sense. If a team publishes their changes to production, therefore exposing them to the customers and potentially causing a high load, many things can go wrong. All the bugs that haven’t been identified during the testing phase could come out, and if no one is around - no one will be able to fix or revert changes that caused an outage. It is now a rule in any organization that implements Agile at least somehow. This means that releases should be minor, frequent, automated, allow backup, and even be exposed to a small number of customers at first. But why are we still so scared to release it to production? We prefer code freezes, no-release Fridays, and other innovations many of us have seen in our workplaces. While all the practices mentioned already, in theory, do allow a particular state of calmness in one's mind, there is always this feeling that something might go wrong and it will fail.Of course, there is nothing wrong with introducing code freezes for Christmas before Friday. The stakes might be so high that even the most sophisticated guardrails do not guarantee safe space. Ordinary releases should be allowed at any point and eventually by anyone who has done their induction training. Are We Agile Enough? Most organizations are still developing in Waterfalls with Sprints - they deliver frequently, but in chunks big enough to be called Epic or even Initiative, with a couple million budgets and anything from one month to almost a year's worth of development. Yes, they call themselves agile. They have all the definitions and automation tests, but no one believes in it somewhere deep in the complex. Most of the releases are still re-tested manually by developers, all the functionalities have to be approved by the risk department before release, and no one collects the metrics that can identify the significance of the released value. It is hard to say, but in most cases, it is true. We are stuck in a constant circle of meetings where we understand what must be done. But if not for that one Agile coach or COO passionate about Agile, that is still waterfall with slightly changed titles and an iterative cadence. Unless the shift of values is successful and the organization truly believes that what it implements and enforces has some meaning, it doesn’t matter. There might be some improvements and even significant ones, but the general course is the same: we imitate the standards they leave. Releasing on Friday is a good idea if you have achieved the Agile state of mind. Quality Control Practices Most of the organizations are still focused on pre-release testing. There are some tests. There is a manual testing process. Then there is testing on the almost-like-production environment, sometimes on-like-production environment, or even safeguarded from the customer’s real production environment. However, it is still pre-release and is not treated as a must for most companies to implement the same testing after release. It will likely be manual or automated testing for critical functionality, and only to the extent that quality engineers from specific teams can do it in hours or days. Ask any software developer on the interview - they will assure you they have 100% code coverage and are doing TDD. Ask any leader in the organization, and they will assure you that all the testing is automated and that only 10% of the functionality that is too costly to automate is still being tested manually. This might be true, but most importantly, it is not what we seek. Bugs will exist no matter how rigorous we are in testing. It is essential to identify them before customers start to be annoyed, and the money will be lost. Releasing on Friday is a good idea if you know how to identify bugs before your customers are annoyed. What Is the Release Process? There might be situations when the irreversible changes happen. There is a migration from the vulnerable software, a change in the database scheme, and a migration to the new infrastructure. You can name it. In this case, there might be no way of adding additional safeguarding for your operations. However, 99% of the release organizations are different from this. They are minor tweaks in maybe not that critical features that are not used by 100% of the customers, and even if something goes wrong - that’s tolerable.CI/CD has become almost synonymous with the release process. It is rare for organizations now to have a system admin who will go to the physical server, plug in a USB drive, and run a command on a server. Most likely, there is a pipeline in one of the known orchestration tools, and after the button is pressed, everything goes live. All release processes have to be automated, with clear and straightforward options to identify problems and back out if the result provides more harm to the business than benefits. Of course, some decisions must be made, but one must have data to base them on to make those decisions. Releasing on Friday is a good idea if there is a straightforward way of judging how the release went and a concise way of backing out. When to Push to Production? Some may argue that implementing all of the practices we have described is too expensive. And they are not wrong - it will take long hours, result in some failures, and potentially annoy customers. However, when you get the right mindset, implement the proper quality controls, and build an error-prone pipeline, there will be nothing to stop you from pushing to production whenever it is right to do so - on Friday, during Christmas, Easter, Black Friday, and before the summer social party. Are you releasing on Friday? If not - what stops you from doing so? Share your thoughts in the comments. This has become a well-known practice or even a meme. When someone pushes code to production on Friday, there is a significant outage of all services, customers are angry, ratings are going down, and revenue is dipping as fast as one can imagine. Eventually, everyone will be brought back to their laptops instead of spending time with family and friends over the weekend. But how did we end up in this situation? If you look at this from a holistic approach, that makes sense. If a team publishes their changes to production, therefore exposing them to the customers and potentially causing a high load, many things can go wrong. All the bugs that haven’t been identified during the testing phase could come out, and if no one is around - no one will be able to fix or revert changes that caused an outage. It is now a rule in any organization that implements Agile at least somehow. This means that releases should be minor, frequent, automated, allow backup, and even be exposed to a small number of customers at first. But why are we still so scared to release it to production? We prefer code freezes, no-release Fridays, and other innovations many of us have seen in our workplaces. While all the practices mentioned already, in theory, do allow a particular state of calmness in one's mind, there is always this feeling that something might go wrong and it will fail. Of course, there is nothing wrong with introducing code freezes for Christmas before Friday. The stakes might be so high that even the most sophisticated guardrails do not guarantee safe space. Ordinary releases should be allowed at any point and eventually by anyone who has done their induction training. Are We Agile Enough? Most organizations are still developing in Waterfalls with Sprints - they deliver frequently, but in chunks big enough to be called Epic or even Initiative, with a couple million budgets and anything from one month to almost a year's worth of development. Yes, they call themselves agile. They have all the definitions and automation tests, but no one believes in it somewhere deep in the complex. Most of the releases are still re-tested manually by developers, all the functionalities have to be approved by the risk department before release, and no one collects the metrics that can identify the significance of the released value. It is hard to say, but in most cases, it is true. We are stuck in a constant circle of meetings where we understand what must be done. But if not for that one Agile coach or COO passionate about Agile, that is still waterfall with slightly changed titles and an iterative cadence. Unless the shift of values is successful and the organization truly believes that what it implements and enforces has some meaning, it doesn’t matter. There might be some improvements and even significant ones, but the general course is the same: we imitate the standards they leave. Releasing on Friday is a good idea if you have achieved the Agile state of mind. Releasing on Friday is a good idea if you have achieved the Agile state of mind. Quality Control Practices Most of the organizations are still focused on pre-release testing. There are some tests. There is a manual testing process. Then there is testing on the almost-like-production environment, sometimes on-like-production environment, or even safeguarded from the customer’s real production environment. However, it is still pre-release and is not treated as a must for most companies to implement the same testing after release. It will likely be manual or automated testing for critical functionality, and only to the extent that quality engineers from specific teams can do it in hours or days. Ask any software developer on the interview - they will assure you they have 100% code coverage and are doing TDD. Ask any leader in the organization, and they will assure you that all the testing is automated and that only 10% of the functionality that is too costly to automate is still being tested manually. This might be true, but most importantly, it is not what we seek. Bugs will exist no matter how rigorous we are in testing. It is essential to identify them before customers start to be annoyed, and the money will be lost. Releasing on Friday is a good idea if you know how to identify bugs before your customers are annoyed. Releasing on Friday is a good idea if you know how to identify bugs before your customers are annoyed. What Is the Release Process? There might be situations when the irreversible changes happen. There is a migration from the vulnerable software, a change in the database scheme, and a migration to the new infrastructure. You can name it. In this case, there might be no way of adding additional safeguarding for your operations. However, 99% of the release organizations are different from this. They are minor tweaks in maybe not that critical features that are not used by 100% of the customers, and even if something goes wrong - that’s tolerable. CI/CD has become almost synonymous with the release process. It is rare for organizations now to have a system admin who will go to the physical server, plug in a USB drive, and run a command on a server. Most likely, there is a pipeline in one of the known orchestration tools, and after the button is pressed, everything goes live. All release processes have to be automated, with clear and straightforward options to identify problems and back out if the result provides more harm to the business than benefits. Of course, some decisions must be made, but one must have data to base them on to make those decisions. Releasing on Friday is a good idea if there is a straightforward way of judging how the release went and a concise way of backing out. Releasing on Friday is a good idea if there is a straightforward way of judging how the release went and a concise way of backing out. When to Push to Production? Some may argue that implementing all of the practices we have described is too expensive. And they are not wrong - it will take long hours, result in some failures, and potentially annoy customers. However, when you get the right mindset, implement the proper quality controls, and build an error-prone pipeline, there will be nothing to stop you from pushing to production whenever it is right to do so - on Friday, during Christmas, Easter, Black Friday, and before the summer social party. Are you releasing on Friday? If not - what stops you from doing so? Share your thoughts in the comments. Are you releasing on Friday? If not - what stops you from doing so? Share your thoughts in the comments.

Don’t Push to Production on Friday. Yet.		

In the React Compiler demo talk, one of the code examples was an event handler that contains a React state that depends on whether an HTML element is in focus. In my opinion, that example doesn’t demonstrate the power of React Compiler but instead shows its limitations. After reading this article, you’ll see why I think so. We’ll look at how we can improve our React app code by using built-in browser APIs and help React Compiler perform better, working around its limitations. We’ll also look at browser APIs that can help optimize React apps' performance in areas beyond React Compiler's scope. document.activeElement — to check if an element is in focus To check if an element is in focus, instead of creating a React state, we can use document.activeElement which returns an element currently in focus. We can read its ID and compare it with an ID of our element. :hover, :focus, :focus-within — for handling hover, focus, and other states Sometimes we dive into React and JS too much and use React state to handle hover or focus states. That actually results in unnecessary re-renders and code complexity. This happens especially often if the project uses Tailwind CSS or Styled-components libraries. We need to remember the power of other technologies available to us, such as CSS. The best way to handle hover, focus, and other states is to use corresponding CSS pseudo-classes. Handling Hover, Focus, and other states in Tailwind CSS should be done using special modifiers.
For styling based on parent state Tailwind CSS has a special group-{modifier} class.
For styling based on if any of the child elements are focused, there’s a focus-within within pseudo-class in CSS.
Styled-components support the same syntax as CSS for handling hover, focus, and other states. <details />, <select />, <input />, <form /> — to get needed functionality out of the box With native HTML elements, we can get a lot of functionality out of the box with great performance and accessibility, without the need to write extra code or add extra state in React. <details /> — for collapsible sections Open/Close states are handled automatically by the browser. We can use CSS to style it. <select /> — for dropdowns Open/Close states are handled automatically by the browser. The dropdown menu is optimized and responsive even on large lists of options, it is convenient to use on both desktop and mobile devices and it is accessible out of the box. <input /> and <form /> — for forms and submitting information Form elements keep an internal state without the need to create a state in React. Of course, for some scenarios, we can get more functionality by using some third-party form libraries in React, but we shouldn’t underestimate how much we can get out of the box with native HTML elements. Check out this example on MDN with a fully functioning payment form created using just plain HTML. Also, check out my other article for another example of how HTML forms can be used to minimize re-renders in React. CustomEvent — for decoupled communication between components Sometimes we need our components to communicate with each other independently, without us having to create a React.Context somewhere at the top of the application. We may need this if we are creating a component library, or if some of our components are web-components. For this purpose, we can use CustomEvents. Here’s an example of using a CustomEvent to implement a tooltip that closes when another one opens. This it how it looks in the browser: Only opening/closing tooltips re-render, in comparison to React.Context which when changed causes every component subscribed to it to be re-rendered. CSS transition and transform — for performant animations The transition property in CSS allows us to create animations. We should create CSS animations only using transform properties (scale, translate etc.) and not using positioning properties (top/left/height/width) which will cause continuous layout computation. Before using any CSS property for animation (other than transform and opacity), we need to determine the property's impact on the rendering pipeline. We should avoid any property that triggers layout or paint unless absolutely necessary. Browsers give us out-of-the-box functionality for creating animations and can optimize rendering flows if correct properties are used. We should always try to create our animations using CSS transitions/animations where possible. requestAnimationFrame, requestIdleCallback — for non-blocking computations If we need to change the CSS properties of an element using JavaScript we should do it with requestAnimationFrame API which will help in not blocking the user’s other operation but executing it at the end of the frame. Long-running and low-priority JavaScript tasks should be split into smaller ones and executed inside requestIdleCallback. There’s an “Idle Until Urgent” pattern. Web Workers — for multi-threading Web Workers make it possible to run a script operation in a background thread separate from the main execution thread (in this way they are different from requestAnimationFrame, requestIdleCallback that a running in the main thread). The advantage of this is that laborious processing can be performed in a separate thread, allowing the main thread to run without being blocked/slowed down. One limitation of Web workers is that they can’t directly access the DOM. But they can communicate with the window context through a messaging pipeline, meaning that a web worker can indirectly access the DOM in a way. One of the examples of using Web Workers in React apps can be a financial dashboard that processes large datasets to generate complex reports and charts. From the React app, we can send a message to the web worker to start the calculation. Once the worker is done, it sends the result back to the main thread (our React app) where we can use it to update the UI (set React state). Conclusion The example that I mentioned at the beginning of the article was used to demonstrate how React Compiler applies memoization to optimize re-renders when the state changes. But in that example, the state was not needed, and the same functionality could be achieved by just using built-in browser APIs. Unfortunately, React Compiler does not know about it, and it has to process the code that was given as is. If the code contains a redundant state, it will stay there. When the state changes, React Compiler will minimize (not guaranteed) how much React re-renders and memoization-related computations will still occur. So, the main principle of structuring state in React: avoiding redundant state, is still worth considering. Also, the more states, the more dependencies in the code that need to be kept in sync and covered by tests. Summary Rely on the browser’s built-in APIs as much as possible, as they are available “for free” (they don’t increase bundle size, etc.) and are almost always the best optimized.
Try to avoid creating states in React for states that can be handled by the browser.
React Compiler will not be able to cover all optimizations of your application. Many of them are beyond its scope. But many optimizations can be achieved using built-in browser APIs.
Before installing a new project dependency, double-check if it is really needed. With built-in browser APIs, we can get optimized performance out of the box. 👏 Thanks for reading! In the React Compiler demo talk , one of the code examples was an event handler that contains a React state that depends on whether an HTML element is in focus. In my opinion, that example doesn’t demonstrate the power of React Compiler but instead shows its limitations. After reading this article, you’ll see why I think so. demo talk We’ll look at how we can improve our React app code by using built-in browser APIs and help React Compiler perform better, working around its limitations. We’ll also look at browser APIs that can help optimize React apps' performance in areas beyond React Compiler's scope. document.activeElement — to check if an element is in focus document.activeElement — to check if an element is in focus To check if an element is in focus, instead of creating a React state, we can use document.activeElement which returns an element currently in focus. We can read its ID and compare it with an ID of our element. document.activeElement :hover, :focus, :focus-within — for handling hover, focus, and other states :hover, :focus, :focus-within — for handling hover, focus, and other states Sometimes we dive into React and JS too much and use React state to handle hover or focus states. That actually results in unnecessary re-renders and code complexity. This happens especially often if the project uses Tailwind CSS or Styled-components libraries. We need to remember the power of other technologies available to us, such as CSS. The best way to handle hover, focus, and other states is to use corresponding CSS pseudo-classes . Tailwind CSS Styled-components pseudo-classes Handling Hover, Focus, and other states in Tailwind CSS should be done using special modifiers. For styling based on parent state Tailwind CSS has a special group-{modifier} class. For styling based on if any of the child elements are focused, there’s a focus-within within pseudo-class in CSS. Styled-components support the same syntax as CSS for handling hover, focus, and other states. Handling Hover, Focus, and other states in Tailwind CSS should be done using special modifiers . Tailwind CSS special modifiers For styling based on parent state Tailwind CSS has a special group-{modifier} class . Tailwind CSS a special group-{modifier} class For styling based on if any of the child elements are focused, there’s a focus-within within pseudo - class in CSS. focus-within - Styled-components support the same syntax as CSS for handling hover, focus, and other states. Styled-components <details /> , <select /> , <input /> , <form /> — to get needed functionality out of the box , , , — to get needed functionality out of the box With native HTML elements, we can get a lot of functionality out of the box with great performance and accessibility, without the need to write extra code or add extra state in React. <details /> — for collapsible sections <details /> — for collapsible sections Open/Close states are handled automatically by the browser. We can use CSS to style it. <select /> — for dropdowns <select /> — for dropdowns Open/Close states are handled automatically by the browser. The dropdown menu is optimized and responsive even on large lists of options, it is convenient to use on both desktop and mobile devices and it is accessible out of the box. <input /> and <form /> — for forms and submitting information <input /> and <form /> — for forms and submitting information Form elements keep an internal state without the need to create a state in React. Of course, for some scenarios, we can get more functionality by using some third-party form libraries in React, but we shouldn’t underestimate how much we can get out of the box with native HTML elements. Check out this example on MDN with a fully functioning payment form created using just plain HTML. Also, check out my other article for another example of how HTML forms can be used to minimize re-renders in React . this example on MDN check out my other article for another example of how HTML forms can be used to minimize re-renders in React CustomEvent — for decoupled communication between components CustomEvent — for decoupled communication between components Sometimes we need our components to communicate with each other independently, without us having to create a React.Context somewhere at the top of the application. We may need this if we are creating a component library, or if some of our components are web-components . For this purpose, we can use CustomEvents . Here’s an example of using a CustomEvent to implement a tooltip that closes when another one opens. React.Context web-components CustomEvents CustomEvent This it how it looks in the browser: Only opening/closing tooltips re-render, in comparison to React.Context which when changed causes every component subscribed to it to be re-rendered. React.Context CSS transition and transform — for performant animations CSS transition and transform — for performant animations The transition property in CSS allows us to create animations. We should create CSS animations only using transform properties (scale, translate etc.) and not using positioning properties (top/left/height/width) which will cause continuous layout computation. transition transform Before using any CSS property for animation (other than transform and opacity ), we need to determine the property's impact on the rendering pipeline . We should avoid any property that triggers layout or paint unless absolutely necessary. transform opacity rendering pipeline Browsers give us out-of-the-box functionality for creating animations and can optimize rendering flows if correct properties are used. We should always try to create our animations using CSS transitions/animations where possible. requestAnimationFrame, requestIdleCallback — for non-blocking computations requestAnimationFrame, requestIdleCallback — for non-blocking computations If we need to change the CSS properties of an element using JavaScript we should do it with requestAnimationFrame API which will help in not blocking the user’s other operation but executing it at the end of the frame. requestAnimationFrame Long-running and low-priority JavaScript tasks should be split into smaller ones and executed inside requestIdleCallback . There’s an “Idle Until Urgent” pattern . requestIdleCallback “Idle Until Urgent” pattern Web Workers — for multi-threading Web Workers — for multi-threading Web Workers make it possible to run a script operation in a background thread separate from the main execution thread (in this way they are different from requestAnimationFrame , requestIdleCallback that a running in the main thread). The advantage of this is that laborious processing can be performed in a separate thread, allowing the main thread to run without being blocked/slowed down. Web Workers requestAnimationFrame , requestIdleCallback One limitation of Web workers is that they can’t directly access the DOM. But they can communicate with the window context through a messaging pipeline, meaning that a web worker can indirectly access the DOM in a way. One of the examples of using Web Workers in React apps can be a financial dashboard that processes large datasets to generate complex reports and charts. From the React app, we can send a message to the web worker to start the calculation. Once the worker is done, it sends the result back to the main thread (our React app) where we can use it to update the UI (set React state). Conclusion Conclusion The example that I mentioned at the beginning of the article was used to demonstrate how React Compiler applies memoization to optimize re-renders when the state changes. But in that example, the state was not needed, and the same functionality could be achieved by just using built-in browser APIs. Unfortunately, React Compiler does not know about it, and it has to process the code that was given as is. If the code contains a redundant state, it will stay there. When the state changes, React Compiler will minimize (not guaranteed) how much React re-renders and memoization-related computations will still occur. So, the main principle of structuring state in React: avoiding redundant state , is still worth considering. Also, the more states, the more dependencies in the code that need to be kept in sync and covered by tests. avoiding redundant state Summary Summary Rely on the browser’s built-in APIs as much as possible, as they are available “for free” (they don’t increase bundle size, etc.) and are almost always the best optimized. Try to avoid creating states in React for states that can be handled by the browser. React Compiler will not be able to cover all optimizations of your application. Many of them are beyond its scope. But many optimizations can be achieved using built-in browser APIs. Before installing a new project dependency, double-check if it is really needed. With built-in browser APIs, we can get optimized performance out of the box. Rely on the browser’s built-in APIs as much as possible, as they are available “for free” (they don’t increase bundle size, etc.) and are almost always the best optimized. Try to avoid creating states in React for states that can be handled by the browser. React Compiler will not be able to cover all optimizations of your application. Many of them are beyond its scope. But many optimizations can be achieved using built-in browser APIs. Before installing a new project dependency, double-check if it is really needed. With built-in browser APIs, we can get optimized performance out of the box. 👏 Thanks for reading!

Improving React App Performance: Leveraging Browser APIs to help React Compiler

Let's build a customer support chatbot using RAG and your company's documentation in OpenWebUI

আসুন OpenWebUI-তে RAG এবং আপনার কোম্পানির ডকুমেন্টেশন ব্যবহার করে একটি গ্রাহক সহায়তা চ্যাটবট তৈরি করি

Lassen Sie uns einen Kundensupport-Chatbot mit RAG und der Dokumentation Ihres Unternehmens in OpenWebUI erstellen

Creemos un chatbot de atención al cliente utilizando RAG y la documentación de su empresa en OpenWebUI

Créons un chatbot de support client en utilisant RAG et la documentation de votre entreprise dans OpenWebUI

आइए RAG और OpenWebUI में आपकी कंपनी के दस्तावेज़ों का उपयोग करके एक ग्राहक सहायता चैटबॉट बनाएं

RAGとOpenWebUIの会社のドキュメントを使用して、カスタマーサポートチャットボットを構築しましょう。

OpenWebUI에서 RAG와 회사 문서를 사용하여 고객 지원 챗봇을 구축해 보겠습니다.

Vamos construir um chatbot de suporte ao cliente usando RAG e a documentação da sua empresa em OpenWebUI

Давайте создадим чат-бота поддержки клиентов, используя RAG и документацию вашей компании в OpenWebUI.

RAG'ı ve şirketinizin OpenWebUI'daki belgelerini kullanarak bir müşteri destek sohbet robotu oluşturalım

Hãy xây dựng một chatbot hỗ trợ khách hàng bằng RAG và tài liệu của công ty bạn trong OpenWebUI

让我们使用 RAG 和您公司在 OpenWebUI 中的文档构建一个客户支持聊天机器人

The US presidential election, scheduled for November 5 of 2024, is beginning to have a strong impact on the cryptocurrency market. The topic of cryptocurrency continues to gain traction in speeches delivered by the candidates seeking to gain votes from the cryptocurrency community, which accounts for more than 46 million citizens in the United States - 22% of the adult population, according to the New York research agency NYDIG. Given the current administration’s totalitarian attitudes towards cryptocurrency and cryptocurrency companies, we can expect easing of regulation as we get closer to the November elections. Trump vs Biden Cryptocurrency Debate The debate between serving President John Biden and the presidential candidate Donald Trump was reported on May 15, 2024, by CCN. The serving president will have to answer several unpleasant questions regarding the implemented cryptocurrency regulation policy, which has led to an outflow of cryptocurrency capital, the shutdown of large companies, and high-profile lawsuits. From Donald Trump, who has turned the topic of cryptocurrency into a weapon against his opponent, in addition to attacks on the current state of affairs, one can expect loud election promises that can lead to significant volatility in the cryptocurrency market. The possible participation of Elon Musk, who has expressed his willingness to host the debate, and independent candidate Robert Kennedy Jr., also known for his love of cryptocurrencies, could turn the debate from a pre-election event into a cryptocurrency one. The first round of debates will take place on June 27, and the second on September 10. Coins without technology and product Meme tokens, popular in the cryptocurrency market in 2024, were a response to the position of the US Securities Commission (SEC), led by the main cryptocurrency villain Garry Gensler. According to the SEC's position, all cryptocurrency tokens issued by blockchain projects must be registered as securities. This makes sense: investors become familiar with the project, believe in its technology, and invest in the creation of the product through the purchase of shares or tokens. As a response to the SEC's position, the market has introduced meme tokens - comic-like cryptocurrencies, behind which there is neither technology nor product development, which does not allow the SEC to classify them as shares and, accordingly, charge the creators of the tokens with trading in unregistered securities. Today, there are 2,283 meme tokens listed on Coinmarketcap, representing only 10% of the total meme tokens created, and the combined capitalization of registered coins exceeds US$60 billion. The meme coin market continues to grow - 183 new cryptocurrencies were issued in April of 2024 compared to 18 in April of 2023. The average increase in the value of new coins after launch is 1300%, so it is not surprising that these coins without a product and technology have become so popular. The Hot Meme Summer 2024 The spring of 2024 saw the launch of several “political” meme tokens. The TRUMP token, created in February of 2024 on the SOLANA blockchain, has grown by 20% over the entire period and has now grown by 113% against the backdrop of Donald Trump’s decision to accept cryptocurrencies as donations during the election campaign. TRUMP is not currently traded on any centralized exchanges. TheMAGA token on the Ethereum blockchain was launched in December of 2023 and has grown by 41% over the entire period, and by 25% since the announcement of the debate on May 15. Like its predecessor, the token is not traded on centralized exchanges. The STRUMP token, launched at the end of March of this year on the Ethereum blockchain, grew 1100%, but between May 15 and May 22 showed a modest increase of 6%, which is significantly lower than the market average. STRUMP, however, is available for purchase on centralized exchanges. TheBABYTRUMP token launched at the end of February of this year on BinanceSmartChain, is up 39% to date, with a 17% increase between May 15 and May 22. The token is traded on centralized and decentralized exchanges. Another meme coin honoring Donald Trump, TREMP, was also launched in March on the SOLANA blockchain, and has grown by 800% over the entire period and by 90% from May 15 to  May 22. The token is traded in different places. Joe Biden is represented by the__Boden__ meme token on SOLANA. Since its launch in March, it has grown by 780%, and in the period from May 15 to 22 - by 6%. This token is available on various platforms. Elon Musk, a darling of the crypto community andDOGE ambassador, as well as a potential debate host, has two new coins dedicated to him. The OLENMOSK token, launched in March on the SOLANA blockchain, dropped in price by 86% over the entire period and remained stable from May 15 to May 22. It is, however, not available for purchase on centralized exchanges. Another token ELON is also in the red zone, having lost 92% in price over the entire period, but over the past week showed an increase of 13%. Unlike the previous token, ELON is traded on several large centralized exchanges. Judging by the number of new “political” meme tokens and the dynamics of their prices, the crypto community is betting on the further growth of the popularity of Donald Trump and his victory in the upcoming elections, which may affect the growth in the value of the cryptocurrencies inspired. However, you need to be prepared for total sales after the first stage of the debate. Not financial advice. DYOR The US presidential election, scheduled for November 5 of 2024, is beginning to have a strong impact on the cryptocurrency market. The topic of cryptocurrency continues to gain traction in speeches delivered by the candidates seeking to gain votes from the cryptocurrency community, which accounts for more than 46 million citizens in the United States - 22% of the adult population, according to the New York research agency NYDIG. Given the current administration’s totalitarian attitudes towards cryptocurrency and cryptocurrency companies, we can expect easing of regulation as we get closer to the November elections. The US presidential election, scheduled for November 5 of 2024, is beginning to have a strong impact on the cryptocurrency market. The topic of cryptocurrency continues to gain traction in speeches delivered by the candidates seeking to gain votes from the cryptocurrency community, which accounts for more than 46 million citizens in the United States - 22% of the adult population, according to the New York research agency NYDIG. Given the current administration’s totalitarian attitudes towards cryptocurrency and cryptocurrency companies, we can expect easing of regulation as we get closer to the November elections. Trump vs Biden Cryptocurrency Debate Trump vs Biden Cryptocurrency Debate The debate between serving President John Biden and the presidential candidate Donald Trump was reported on May 15, 2024, by CCN. The serving president will have to answer several unpleasant questions regarding the implemented cryptocurrency regulation policy, which has led to an outflow of cryptocurrency capital, the shutdown of large companies, and high-profile lawsuits. From Donald Trump, who has turned the topic of cryptocurrency into a weapon against his opponent, in addition to attacks on the current state of affairs, one can expect loud election promises that can lead to significant volatility in the cryptocurrency market. The possible participation of Elon Musk, who has expressed his willingness to host the debate, and independent candidate Robert Kennedy Jr., also known for his love of cryptocurrencies, could turn the debate from a pre-election event into a cryptocurrency one. The first round of debates will take place on June 27, and the second on September 10. The debate Coins without technology and product Meme tokens, popular in the cryptocurrency market in 2024, were a response to the position of the US Securities Commission (SEC), led by the main cryptocurrency villain Garry Gensler. According to the SEC's position, all cryptocurrency tokens issued by blockchain projects must be registered as securities. This makes sense: investors become familiar with the project, believe in its technology, and invest in the creation of the product through the purchase of shares or tokens. As a response to the SEC's position, the market has introduced meme tokens - comic-like cryptocurrencies, behind which there is neither technology nor product development, which does not allow the SEC to classify them as shares and, accordingly, charge the creators of the tokens with trading in unregistered securities. Today, there are 2,283 meme tokens listed on Coinmarketcap , representing only 10% of the total meme tokens created, and the combined capitalization of registered coins exceeds US$60 billion. The meme coin market continues to grow - 183 new cryptocurrencies were issued in April of 2024 compared to 18 in April of 2023. The average increase in the value of new coins after launch is 1300%, so it is not surprising that these coins without a product and technology have become so popular. Coinmarketcap Coinmarketcap The Hot Meme Summer 2024 The spring of 2024 saw the launch of several “political” meme tokens. The TRUMP token, created in February of 2024 on the SOLANA blockchain, has grown by 20% over the entire period and has now grown by 113% against the backdrop of Donald Trump’s decision to accept cryptocurrencies as donations during the election campaign. TRUMP is not currently traded on any centralized exchange s. TRUMP TRUMP SOLANA SOLANA not currently traded on any centralized exchange The MAGA token on the Ethereum blockchain was launched in December of 2023 and has grown by 41% over the entire period, and by 25% since the announcement of the debate on May 15. Like its predecessor, the token is not traded on centralized exchanges. MAGA not traded on centralized exchanges. The STRUMP token, launched at the end of March of this year on the Ethereum blockchain, grew 1100%, but between May 15 and May 22 showed a modest increase of 6%, which is significantly lower than the market average. STRUMP , however, is available for purchase on centralized exchanges. STRUMP STRUMP The BABYTRUMP token launched at the end of February of this year on BinanceSmartChain, is up 39% to date, with a 17% increase between May 15 and May 22. The token is traded on centralized and decentralized exchanges. BABYTRUMP Another meme coin honoring Donald Trump, TREMP , was also launched in March on the SOLANA blockchain, and has grown by 800% over the entire period and by 90% from May 15 to  May 22. The token is traded in different places. TREMP TREMP Joe Biden is represented by the__ Boden __ meme token on SOLANA. Since its launch in March, it has grown by 780%, and in the period from May 15 to 22 - by 6%. This token is available on various platforms. Boden Elon Musk, a darling of the crypto community and DOGE ambassador, as well as a potential debate host, has two new coins dedicated to him. The OLENMOSK token, launched in March on the SOLANA blockchain, dropped in price by 86% over the entire period and remained stable from May 15 to May 22. It is, however, not available for purchase on centralized exchanges. Another token ELON is also in the red zone, having lost 92% in price over the entire period, but over the past week showed an increase of 13%. Unlike the previous token, ELON is traded on several large centralized exchanges. DOGE OLENMOSK ELON ELON ELON ELON Judging by the number of new “political” meme tokens and the dynamics of their prices, the crypto community is betting on the further growth of the popularity of Donald Trump and his victory in the upcoming elections, which may affect the growth in the value of the cryptocurrencies inspired. However, you need to be prepared for total sales after the first stage of the debate. Not financial advice. DYOR Not financial advice. DYOR Not financial advice. DYOR

How the Upcoming Us Elections Are Changing the Cryptocurrency Market

Ideogram Prompt: Create a pixel-perfect Insta logo on a vibrant mushroom. The typography above mario reads "Beneath the Links" written in contra sega games letters., 3d render, illustration, typography, vibrant, anime Have you ever wondered what happens behind the scenes when you click a link? The Internet is a vast network, and web addresses, or URLs, are like maps guiding us through it. In this article, we'll explore the fascinating world of URLs by looking at how Instagram uses them. Get ready to learn how the web truly works! A Peek Behind the Curtain: Instagram's Login Process Imagine setting up an automatic Instagram post using a tool. You're presented with a long, mysterious web address: "https://www.instagram.com/accounts/login/force_authentication=1&enable_fb_login=1&next=/oauth/authorize%3Fclient_id%3D178678656777493%26redirect_uri%″ This address is like a treasure map, leading us through the intricate paths of the Internet. Let's break it down: https:// This is like saying, "Hey, let's talk securely." It's a safe way to send information. www.instagram.com This is Instagram's online address, where all its content lives. /accounts/login/ This directs us to the login page, like a signpost saying, "Welcome, sign in here.” force_authentication=1&enable_fb_login=1These add extra instructions, like "Make sure they log in securely," and "Let them use their Facebook info." next=/oauth/authorize This continues the journey, using a standard map (OAuth) for safe travels. It includes details like a client ID and where to go next. By deciphering this address, we understand how Instagram securely guides us through the web. Decoding the Secrets: The Magic of Parameters As we journey through the Instagram login URL, we encounter curious fragments filled with intriguing parameters. These parameters are like hidden keys, each serving a unique purpose in the authentication process: client_id: Imagine a unique identifier, like a special passcode, given to Instagram by the tool you're using (in this case, Zapier). This ensures that Instagram knows exactly which app is trying to access your account and can enforce special permissions or restrictions. redirect_uri: This is like a return address on a letter. It tells Instagram where to send you back after you've successfully logged in. It ensures you don't get lost in the vast web and always end up back where you need to be. response_type: Instagram is versatile, and this parameter determines the type of response it should provide. It could be a code, token, or other data, depending on the context of the request. scope: This parameter defines the permissions being requested. It's like a list of privileges, specifying what parts of your Instagram account the app can access, such as your profile or media. state: Security is paramount, and this parameter guards against potential threats. It's a random string generated for each request, ensuring that no mischievous imposters can tamper with the login process. logger_id: Instagram keeps a careful eye on things, and this parameter helps with debugging. It's like a unique identifier for the login attempt, making it easier to trace and resolve any issues that may arise. By including these parameters, Instagram orchestrates a secure and tailored login experience, ensuring that your journey through the web is both safe and seamless. A Visual Flow Why Understanding Web Addresses Matters Exploring web addresses is exciting, but it's also useful! Here's how: Fixing Problems: Understanding web addresses helps fix issues with websites and apps, like a detective solving a mystery.
SEO: Creating clear web addresses improves a website's visibility, helping people find it easier.
Building Blocks: Developing new apps and services relies on understanding the basics of web addresses.
Staying Safe: With cyber threats, knowing about secure web addresses protects your online safety.
Marketing: Marketers use special web addresses to track campaigns and understand their audience.
Sharing: Well-structured web addresses make it simple to share specific content or resources.
Short and Sweet: Long addresses can be shortened, making them easier to share and remember. USE CASES Troubleshooting and Debugging: Identify and fix errors in web applications by analyzing URL parameters.
SEO Optimization: Create user-friendly, keyword-rich URLs to improve search engine rankings.
API Integration: Access and manipulate web services by understanding query strings and path parameters.
Security: Detection of malicious URLs and prevent phishing or data breaches.
Link Tracking: Monitoring of traffic sources and user behavior with UTM parameters.
Custom URL Generation: Development of personalized links for marketing campaigns or user experience.
Data Sharing: Safe sharing of specific resources or searches using well-structured URLs.
URL Shortening: Generation of shorter links for ease of sharing while maintaining the original URL’s purpose. If you like the above, feel free to connect on LinkedIn/support me on Patreon/buy me a coffee to help me continue my journey. References : https://www.ibm.com/docs/en/cics-ts/6.1?topic=concepts-components-url
https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
https://owasp.org/www-community/attacks/csrf
https://developers.cloudflare.com/pages/functions/debugging-and-logging/
https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow/add-login-auth-code-flow Ideogram Prompt: Create a pixel-perfect Insta logo on a vibrant mushroom. The typography above mario reads "Beneath the Links" written in contra sega games letters., 3d render, illustration, typography, vibrant, anime Ideogram Prompt: Create a pixel-perfect Insta logo on a vibrant mushroom. The typography above mario reads "Beneath the Links" written in contra sega games letters., 3d render, illustration, typography, vibrant, anime Ideogram Prompt: Create a pixel-perfect Insta logo on a vibrant mushroom. The typography above mario reads "Beneath the Links" written in contra sega games letters., 3d render, illustration, typography, vibrant, anime Have you ever wondered what happens behind the scenes when you click a link? The Internet is a vast network, and web addresses, or URLs, are like maps guiding us through it. In this article, we'll explore the fascinating world of URLs by looking at how Instagram uses them. Get ready to learn how the web truly works! A Peek Behind the Curtain: Instagram's Login Process Imagine setting up an automatic Instagram post using a tool. You're presented with a long, mysterious web address: "https://www.instagram.com/accounts/login/force_authentication=1&enable_fb_login=1&next=/oauth/authorize%3Fclient_id%3D178678656777493%26redirect_uri%″ " https://www.instagram.com/accounts/login/force_authentication=1&enable_fb_login=1&next=/oauth/authorize%3Fclient_id%3D178678656777493%26redirect_uri%″ https://www.instagram.com/accounts/login/force_authentication=1&enable_fb_login=1&next=/oauth/authorize%3Fclient_id%3D178678656777493%26redirect_uri%″ https://www.instagram.com/accounts/login/force_authentication=1&enable_fb_login=1&next=/oauth/authorize%3Fclient_id%3D178678656777493%26redirect_uri%″ This address is like a treasure map, leading us through the intricate paths of the Internet. Let's break it down: https:// This is like saying, "Hey, let's talk securely." It's a safe way to send information. https:// This is like saying, "Hey, let's talk securely." It's a safe way to send information. https:// www.instagram.com This is Instagram's online address, where all its content lives. www.instagram.com This is Instagram's online address, where all its content lives. www.instagram.com /accounts/login/ This directs us to the login page, like a signpost saying, "Welcome, sign in here.” /accounts/login/ This directs us to the login page, like a signpost saying, "Welcome, sign in here.” /accounts/login/ force_authentication=1&enable_fb_login=1These add extra instructions, like "Make sure they log in securely," and "Let them use their Facebook info." force_authentication=1&enable_fb_login=1 These add extra instructions, like "Make sure they log in securely," and "Let them use their Facebook info." force_authentication=1&enable_fb_login=1 next=/oauth/authorize This continues the journey, using a standard map (OAuth) for safe travels. It includes details like a client ID and where to go next. next=/oauth/authorize This continues the journey, using a standard map (OAuth) for safe travels. It includes details like a client ID and where to go next. next=/oauth/authorize By deciphering this address, we understand how Instagram securely guides us through the web. Decoding the Secrets: The Magic of Parameters As we journey through the Instagram login URL, we encounter curious fragments filled with intriguing parameters. These parameters are like hidden keys, each serving a unique purpose in the authentication process: client_id: Imagine a unique identifier, like a special passcode, given to Instagram by the tool you're using (in this case, Zapier). This ensures that Instagram knows exactly which app is trying to access your account and can enforce special permissions or restrictions. client_id: Imagine a unique identifier, like a special passcode, given to Instagram by the tool you're using (in this case, Zapier). This ensures that Instagram knows exactly which app is trying to access your account and can enforce special permissions or restrictions. client_id: redirect_uri: This is like a return address on a letter. It tells Instagram where to send you back after you've successfully logged in. It ensures you don't get lost in the vast web and always end up back where you need to be. redirect_uri: This is like a return address on a letter. It tells Instagram where to send you back after you've successfully logged in. It ensures you don't get lost in the vast web and always end up back where you need to be. redirect_uri: response_type: Instagram is versatile, and this parameter determines the type of response it should provide. It could be a code, token, or other data, depending on the context of the request. response_type: Instagram is versatile, and this parameter determines the type of response it should provide. It could be a code, token, or other data, depending on the context of the request. response_type: scope: This parameter defines the permissions being requested. It's like a list of privileges, specifying what parts of your Instagram account the app can access, such as your profile or media. scope: This parameter defines the permissions being requested. It's like a list of privileges, specifying what parts of your Instagram account the app can access, such as your profile or media. scope: state: Security is paramount, and this parameter guards against potential threats. It's a random string generated for each request, ensuring that no mischievous imposters can tamper with the login process. state: Security is paramount, and this parameter guards against potential threats. It's a random string generated for each request, ensuring that no mischievous imposters can tamper with the login process. state: logger_id: Instagram keeps a careful eye on things, and this parameter helps with debugging. It's like a unique identifier for the login attempt, making it easier to trace and resolve any issues that may arise. logger_id: Instagram keeps a careful eye on things, and this parameter helps with debugging. It's like a unique identifier for the login attempt, making it easier to trace and resolve any issues that may arise. logger_id: By including these parameters, Instagram orchestrates a secure and tailored login experience, ensuring that your journey through the web is both safe and seamless. A Visual Flow Why Understanding Web Addresses Matters Exploring web addresses is exciting, but it's also useful! Here's how: Fixing Problems: Understanding web addresses helps fix issues with websites and apps, like a detective solving a mystery. SEO: Creating clear web addresses improves a website's visibility, helping people find it easier. Building Blocks: Developing new apps and services relies on understanding the basics of web addresses. Staying Safe: With cyber threats, knowing about secure web addresses protects your online safety. Marketing: Marketers use special web addresses to track campaigns and understand their audience. Sharing: Well-structured web addresses make it simple to share specific content or resources. Short and Sweet: Long addresses can be shortened, making them easier to share and remember. Fixing Problems: Understanding web addresses helps fix issues with websites and apps, like a detective solving a mystery. Fixing Problems: SEO: Creating clear web addresses improves a website's visibility, helping people find it easier. SEO: Building Blocks: Developing new apps and services relies on understanding the basics of web addresses. Building Blocks: Staying Safe: With cyber threats, knowing about secure web addresses protects your online safety. Staying Safe: Marketing: Marketers use special web addresses to track campaigns and understand their audience. Marketing: Sharing: Well-structured web addresses make it simple to share specific content or resources. Sharing: Short and Sweet: Long addresses can be shortened, making them easier to share and remember. Short and Sweet: USE CASES Troubleshooting and Debugging: Identify and fix errors in web applications by analyzing URL parameters. SEO Optimization: Create user-friendly, keyword-rich URLs to improve search engine rankings. API Integration: Access and manipulate web services by understanding query strings and path parameters. Security: Detection of malicious URLs and prevent phishing or data breaches. Link Tracking: Monitoring of traffic sources and user behavior with UTM parameters. Custom URL Generation: Development of personalized links for marketing campaigns or user experience. Data Sharing: Safe sharing of specific resources or searches using well-structured URLs. URL Shortening: Generation of shorter links for ease of sharing while maintaining the original URL’s purpose. Troubleshooting and Debugging : Identify and fix errors in web applications by analyzing URL parameters. Troubleshooting and Debugging SEO Optimization : Create user-friendly, keyword-rich URLs to improve search engine rankings. SEO Optimization API Integration : Access and manipulate web services by understanding query strings and path parameters. API Integration Security : Detection of malicious URLs and prevent phishing or data breaches. Security Link Tracking : Monitoring of traffic sources and user behavior with UTM parameters. Link Tracking Custom URL Generation : Development of personalized links for marketing campaigns or user experience. Custom URL Generation Data Sharing : Safe sharing of specific resources or searches using well-structured URLs. Data Sharing URL Shortening : Generation of shorter links for ease of sharing while maintaining the original URL’s purpose. URL Shortening If you like the above, feel free to connect on LinkedIn /support me on Patreon /buy me a coffee to help me continue my journey. LinkedIn Patreon coffee References : https://www.ibm.com/docs/en/cics-ts/6.1?topic=concepts-components-url https://en.wikipedia.org/wiki/Uniform_Resource_Identifier https://owasp.org/www-community/attacks/csrf https://developers.cloudflare.com/pages/functions/debugging-and-logging/ https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow/add-login-auth-code-flow https://www.ibm.com/docs/en/cics-ts/6.1?topic=concepts-components-url https://en.wikipedia.org/wiki/Uniform_Resource_Identifier https://owasp.org/www-community/attacks/csrf https://developers.cloudflare.com/pages/functions/debugging-and-logging/ https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow/add-login-auth-code-flow

Unlocking the Secrets of URL: A Journey for All

How Mental Models and Mathematics Help Solve
Engineering Problems

How to Find Out If You're Paying for Slow Internet

Mission Generation Using Classic Machine Learning and Recurrent Neural Networks in Zombie State

জম্বি রাজ্যে ক্লাসিক মেশিন লার্নিং এবং পুনরাবৃত্ত নিউরাল নেটওয়ার্ক ব্যবহার করে মিশন জেনারেশন

Missionsgenerierung mit klassischem maschinellem Lernen und rekurrierenden neuronalen Netzwerken im Zombie-Zustand

Generación de misiones utilizando aprendizaje automático clásico y redes neuronales recurrentes en estado zombie

Génération de mission à l'aide de l'apprentissage automatique classique et des réseaux de neurones récurrents dans un état zombie

ज़ोंबी स्टेट में क्लासिक मशीन लर्निंग और रीकरंट न्यूरल नेटवर्क का उपयोग करके मिशन जनरेशन

ゾンビ状態での古典的な機械学習とリカレントニューラルネットワークを使用したミッション生成

좀비 상태에서 고전적인 기계 학습과 순환 신경망을 사용한 미션 생성

Geração de missão usando aprendizado de máquina clássico e redes neurais recorrentes no estado zumbi

Генерация миссий с использованием классического машинного обучения и рекуррентных нейронных сетей в состоянии зомби

Zombie State'te Klasik Makine Öğrenimi ve Tekrarlayan Sinir Ağlarını Kullanarak Görev Oluşturma

Tạo nhiệm vụ bằng cách sử dụng mạng lưới thần kinh định kỳ và học máy cổ điển ở trạng thái Zombie

在僵尸状态下使用经典机器学习和循环神经网络生成任务

This is the third piece in my series about , which started with a focus on to then dive deeper into the landscape of Restaking EigenLayer Restaking Finance. Since then, we have seen the , such as and $ , which have attracted increasing attention. emergence of new players in the space Kelp DAO, Renzo, RSTK seems to be positioned to be one of the However, while many talk about how restaking works, and its benefits, Restaking main narratives driving 2024. it’s not all rosy. This article aims to take a step back and analyze at a higher level, highlighting risks and answering the question: is it really Restaking worth it? Let’s start with a quick intro to the subject. What Is Restaking? serves as a where participants commit their stake to secure the Ethereum network. Ethereum’s Proof of Stake (PoS) decentralized trust mechanism, Restaking is the idea that the same stake used to secure the Ethereum PoS can now be used to secure many other networks. Restaking can be interpreted as programmable staking, where users opt-in to any positive or negative incentives to secure other infrastructure. In practice, EigenLayer restakers supply (in the form of staked eth), so that economic trust anything objectively verifiable can be slashed. Would you, Eth staker, like to opt into additional slashing conditions on other chains? EigenLayer is “ ” the decentralized trust of Ethereum so that AVS services can leverage it without the effectively lowering the barriers to entry in this market. modularizing need to bootstrap their validator set, Typically, such modules require actively validated services that have their own distributed validation semantics to do verification. Usually, these actively validated services (“AVS”) are either secured by their own native token or are permissioned in nature. Why Would Anyone Do This? Simply put it, is because of economic incentives and yields. If Ethereum staking yields hover around 5% annually, restaking could offer an enticing additional yield. estimate of these rewards, as they will depend on demand and supply dynamics on the It’s not currently possible to provide an Eigen Marketplace. However, this translates into additional risks for stakers. Aside from the inherent risk of leveraging their staked ETH, when users opt-in to restake your tokens, they are essentially in case of errors, double signing, etc. on any of the AVS they secure. entrusting to the EigenLayer contracts the authority to slash their stake As such, as restakers could get slashed on ETH, on the restaking layer, or both. restaking adds a layer of risk, Is the extra yield worth ? restaking R(isk)-Staking For stakers, means that you can decide to opt-in to as many networks as you wish and boost your yields, hence, why EigenLayer refers to itself as “ restaking the Airbnb of decentralized trust.” It’s not all roses though.. as restaking adds some notable risks: ETH must be staked (or LSTs - hence not liquid) EigenLayer smart contract risk Protocol-specific Slashing conditions Liquidity risks Concentration risks De-facto, (due to staking), and adding additional risks on top of it, ending up with layered risks looking like: by restaking users are leveraging a token that is already exposed to risks Furthermore, any additional development of primitives on top of those would add even more complexity and additional risk. Aside from the individual risk of , the has also raised issues concerning Restaking, notably in the famous restakers Ethereum Developer community Vitalik article about not overloading Ethereum consensus. The issue with restaking is that it opens up new avenues of risk for staked Eth that secures the mainnet; it destines a part of it to secure other chains (as opted-in by stakers). Consequently, if they misbehave according to other protocol rules (which could have bugs or weak security), their deposit gets slashed. The debate is very actual with the devs and EigenLayer trying to find a way to coordinate efforts and make sure that Ethereum is not weakened by these technical advancements. Repurposing the most important “ ”, securing Ethereum, is indeed not an easy feat. layer Furthermore, a key aspect in this regard is the level of allowed for restakers. risk management Many Restaking projects give the However, as a I would want to personally vet and decide which AVS to restake to, to avoid being slashed by malicious networks and reduce the possibilities of new vectors of attack. whitelisting process for AVS into the hands of their DAOs. restaker, All in all, restaking is an interesting new primitive worth researching. Nonetheless, the concerns of Vitalik and others are not to be minimized. When talking about restaking, it’s important to bear in mind how this affects the security model of the Ethereum mainnet. It is, however, fair to contextualize restaking as offering an extra level of risk on top of one of the most important mechanisms securing Ethereum. In the end, whether restaking is worth it or not is an individual choice. Restaking Risks: Collusion risk: many operators could attack a set of AVS at the same time and compromise security. Slashing risk: users restaking are subject to slashing penalties from both ETH and AVS. Single point of failure: receives withdraw credentials from eth credentials (systemic risk for mainnet). Centralization risk for validators Adds additional risks to the stake-securing Ethereum Institutional Appeal Perhaps surprisingly, many institutions have signaled their interest in restaking as an additional reward on top of staked Eth. Nonetheless, they will probably carry out restaking through their custodians rather than joining any other service which might expose them to additional risks of slashing. Given the risk highlighted before, whether the highest interest for restaking will come from retail or institutions will be interesting. An additional yield on top of the native Eth staking is appealing for those already involved in it, but it’s not a life-changing yield for degens, given the risks. This opens up new use cases for Ethereum as a financial instrument. A particularly interesting comparison is made, comparing restaking applications to “ ” corporate bonds. New networks want to get L1 security, similar to how companies or nation-states use their financial systems to create bonds and secure their assets. In crypto, Ethereum is the widest and most liquid network, and probably the only one that could sustain this type of market — and the most secure from a similar point of view of nations states in the TradFi economy. Those interested in getting deeper into this can refer to: https://www.youtube.com/watch?v=d-wVZzgMhhQ&ab_channel=EigenLayer&embedable=true For now, most interest in restaking seems to be driven by speculations on the EigenLayer airdrop, which might just be the biggest airdrop ever in the history of crypto. How will the dynamics change after the airdrop? Perhaps a practical r/r analysis might then push some to other avenues which might be more fruitful. I would go as far as to argue that a high % of capital deposited in restaking is mercenary capital, which might then leave post-airdrop. Separating the speculative component will be fundamental to assessing the real interest that users have in this new primitive. Personally, the narrative is a bit oversold IMHO, with very present risks that have to be evaluated carefully. restaking Key Takeaways Thanks to restaking, AVS have lower cost barriers to kick-start when they can leverage. Ethereum’s highly robust security layer. Users benefit from increased capital efficiency by having the option to restake their ETH, in turn receiving more staking rewards. Restaking adds additional risk on top of other risks. Restaking is an exciting primitive that can spur a novelty of use cases. While full development of the Eigen marketplace will take place in about a year, there are already a few interesting restaking experiments being explored. Some concerns raised by Vitalik are related to the centralization of staking power, at the expense of solo staking. It will be interesting to observe how EigenLayer will team up with the Ethereum Foundation to address those. But aside from those, other issues remain. What Can We Do to Mitigate These Risks? Some of the solutions to mitigate the risks of restaking involve the (TVL caps, slashing amounts, fee distribution, min TVL, etc.) as well as ensuring the optimization of the parameters of restaking diversification of the funds across AVSs. An immediate step that restaking protocols can take into consideration is to allow users to select different risk profiles when depositing for restaking. Ideally, each user should be able to assess and select which AVS to restake to, without having to delegate the process to a DAO. This needs to be the product of joint efforts across AVSs and EigenLayer, to make sure there is a roadmap in process to minimize those risks. The EigenLayer team is already working with the Ethereum Foundation on further alignment and making sure that restaking does not add system risks to Ethereum, Liquid Staking Tokens, or AVSs leveraging it. More on Restaking: https://twitter.com/ChainLinkGod/status/1736897325820457018 https://twitter.com/francescoweb3/status/1706238268898177139 https://twitter.com/francescoweb3/status/1708776352898527489 The author of this post is not associated with the projects mentioned in this article in any way. All of the content above is not financial advice, and you are always encouraged to do your own research. Also published here

Restaking Risks: Is It a House of Cards?

For many people outside the IT world, a career where you just sit in front of a computer all day seems so easy. However, the more IT evolves, the more challenging and stressful it becomes. Throughout my own professional journey, from junior to senior and leading positions, I’ve been through different types of jobs and businesses with different paces and priorities. Through these experiences, I've gained valuable insights about stress management and its impact on your career. So let's talk about how to build a nice career in the IT world and avoid falling into the depths of stress, anxiety, and depression! It actually doesn’t matter if you have just started your career or if you have been working in this field for 10 years, there is something you should analyze before getting a new or next job. Think of What You Need From the Job A lot of people may not realize it, but work is a huge part of our lives and most of our day. So, with that in mind, what kind of job would you get? Well, in terms of a career, I like to divide jobs into two parts: Work for the sake of money or stability (or both): If you have a skill that you can sell but this path is not really aligned with your dreams, you may consider getting a "work for the money" job that can provide you with a good income for living while you take the first steps into a new career or create your dream project. You can find a lot of advice on how to quit your job and pursue your passion, but it's the worst advice for those who don't have a decent amount of savings to provide themselves with a whole year (at least) of job-free living. That's why the "work for money" job is essential, and the key here is to get a job that doesn't bother you much, where you can just quietly do your job and get your money while all your focus is on your "dream career" project. It means no harsh deadlines and a very slow-paced work environment. Product-oriented companies and non-leading positions should work the best. Work for career opportunities: This is a pretty obvious and classic way, but somehow many people fail here. The most common mistake is to jump into a career without knowing what you really want out of it. Avoid getting a job in a super big company if you dream of a startup; you will lose so much time and get irrelevant experience. The same is true if your dream is to become a software engineer, but everyone says that starting as a quality assurance engineer is easier. Figure out what you want out of your career as soon as possible and choose a job that will give you relevant experience and opportunities. Some people want to believe that they can find 2-in-1, but in reality, it is so difficult to find, and mostly it is available for high-level professionals. So if you’re just starting (or not yet) or you are a lost middle, separating these types can be very useful if you have big dreams! To understand what you need right now, separate the job from the career path. Then determine your dream career goals, the "where you want to be in five years." Analyze how close you are to it now and determine the exact things you need to get there. Then look at those things and decide what kind of job can give you that. Set the Right Expectations for the Position The amount of stress you are going to have totally depends on your expectations for the position. There are situations where people take a job that they think will bring them nice opportunities, but the company itself actually has a different vector and different goals. And after some time, it turns out that such a person is actually not the right choice for the position. I myself was in such a situation where, being in a lead position, you think that you can bring so many ideas to make a company better, but it turned out the company didn’t need that at all. So, as a good specialist who fits perfectly into the position, you have to clearly understand the company's needs, its mission, and its goals. And, of course, it should also match your ideas and expectations! Because if you don't match with a company, you will rather do something you enjoy but the company doesn't need it, and you will probably end up getting fired, or you will do the job right but it won't bring you joy and growth, and you will end up in depression. So, before you apply for a job, be clear about your plans and desired career path, and make sure it fits with the company and that they can offer you what you need. To understand that, try this: Review the company's website and social media. Such platforms often reflect their culture and values. Pay attention to the language they use—do they talk more about their perfect team or are they more client-oriented? How transparent are they about the processes and overall inside and outside culture? Do they write about appreciation of innovation and personal or professional growth? How clear are their goals for a random stranger who visits the platform to learn about the company? Ask cultural questions during the interview. Don’t forget that not only they assess you during the interview, but you should also assess them. Ask them about the culture, try to use tricky questions because they will try to sell you the perfect picture. How does the company maintain a healthy work-life balance? How does the company support professional growth? What are the company's employee recognition programs? While listening to the answers, pay attention to their voice and tone - are they passionate and excited to tell you this or can’t really find the words to describe it? Examine the company's employee perks and benefits. While this cannot be an indicator of the company’s culture, it can provide clues about the company's priorities and values. And an employee’s well-being matters so much and contributes to a stress-free environment. So, this was about the pre-work mindset. Let’s now move to the point where you already have a job. Fix Your Focus Problem One of the biggest catalysts for stress is a job that is not done on time. The reasons for missed deadlines can vary so much, but the biggest one that you can actually control, no matter what your position is, is your focus. It is hard to say who has more distractions - the office worker or the remote worker. I used to work in both environments, and I can say that there are enough distractions in both places, so it's better to see why you're distracted than try to get rid of them, especially if you can't. Here are the most impactful things, in my opinion: Declutter your work space regularly, but keep it interesting and exciting to work in. Sometimes people go all-in on minimizing distractions, ending up in a very boring and unwelcoming environment. Mute everything that disturbs you. And it’s not only about notifications. People can actually perform only one task at a time and focus on one thing at a time, so there’s no way you can be productive and efficient if you listen to podcasts or watch videos (or even movies). And if you really struggle with concentration, the music with lyrics can disturb you as well by bringing back memories or dreamy thoughts. Increase the quality of your sleep, diet, and wellbeing. Sometimes the concentration problem is deeper than you think. And so many people who struggle with concentration don't really notice that they've started sleeping worse, their diet isn't as varied, or even that anxiety has become a routine. Keep your room dark and cool for the night, reduce lights 2 hours before bedtime, and stick to the sleep schedule. Add to your diet as many plant-based products as possible, and listen to your body in terms of hunger and fulfillment. If you stress a lot or get nervous over trifles, consider using calming products such as herbs of any kind and activities such as yoga, meditations, and breathing. Learn to Say No Don't be afraid to politely decline additional responsibilities or projects that you can't handle without compromising your own workload or well-being. People usually take on more because they want to be noticed and advance their careers, but overload can play a bad game with you. Instead of focusing on your own tasks and doing them brilliantly by investing some time in research and applying more qualitative and thoughtful approaches, the quality of your work will only decrease, and your boss/manager/leader will be used to put more on your shoulders. By taking on too many tasks, you also risk losing the opportunity to grow, because the more tasks you have, the less time you have for education and exploration. Also remember that every task has a deadline, and every deadline is a stress, so the more tasks - the more stress. To decline additional responsibilities without damaging your relationships with leaders or managers, try this: Be very calm, polite, and appreciative. Express your gratitude and say that you are always very happy to help (but not this time, of course). Explain your current workload in very detailed and specific terms. Show the numbers, tasks, deadlines, and other responsibilities. Acknowledge your limits. Professionally explain how long it will take you to finish your current tasks and how the new one will affect the quality of your work, your overall efficiency and wellbeing. Propose alternative solutions. If it’s possible, suggest delegating the task or it’s part, doing the task later when you finish your current ones, or even changing a solution to be more simple but still effective. Prioritize Self-Care Maintaining a healthy body and mind should certainly be a top priority! If you want to have a stress-free career, you need to dedicate a lot of time each day to activities that promote physical and mental well-being, such as regular exercise, a balanced diet, good sleep, and mindfulness practices like meditation or yoga. It's very hard to get started, especially if you've never done any of these things before, but it's so worth it once you get into the habit. Pay special attention to your diet, you can even read up on nutrition and learn new recipes to speed up the process. But overall, variety of food is much more important than quantity. Also, try to learn to listen to your body and only eat food that makes you feel good. A weakness of IT workers is, of course, the spine, so in terms of physical exercise, stretching is actually much more valuable than going to the gym and lifting weights because muscle flexibility does the most to keep the spine healthy and prevent pain from prolonged sitting. So, regular stretching or yoga can help you reduce neck, back, and lower back pain while sitting, keep your spine healthy, gain body flexibility, and manage stress. Disconnect From Technology It is so difficult to think about anything else when you have only a job in your life. Providing yourself with enough "distractions" and hobbies can be very helpful to reset your brain after work and be refreshed for new challenges. It is important to consider hobbies that do not involve your devices to give your mind and body a break from constant stimulation. And try to mix up the activities that will help you live an interesting, exciting, and stress-free life. But hobbies aren't the only way to improve mental clarity. Set clear boundaries between work and personal life to prevent work from encroaching on your personal time and causing burnout. Avoid checking work emails or messages outside of work hours. In general, disconnect from technology as much as possible, allow your brain to cool down between tasks, switch out of computer activities, get out as much as possible, and reduce the internet to prevent your attention span from dropping. Make Your Work Routine Exciting If you are a regular professional, such as a developer, QA, or manager, your routine can be very boring or, on the other hand, very fast-paced and stressful. So for both options, it is nice to add some excitement to your daily tasks. Here are some tips that may help: Remember what you are doing this for - the end user (or business). Thinking about the real purpose can spark excitement and new ideas that you can propose to the team. If it’s possible, challenge yourself or even collaborate with your teammate to explore new technology. Try contributing to the open-source community. You can contribute to existing projects or create your own! It feels really good to be part of such a community, and even better when you can create something that helps you and your team solve a problem or improve a process. Probably the easiest way to get excited about what you do is to set career goals, track them, and analyze them regularly. Tracking your progress can help you stay motivated and focused. Invest in new tools, gear, or furniture. Using better-quality goods can make the daily routine not only more exciting but also more efficient. The Career is a Game The last big piece of advice is to shift your career mindset towards a game, because a career is something that you can start over at any time or even try a different one! And like in any game, career levels can be easy, medium, or super hard. But unlike in the game, where if you lose, you have to do the same thing over and over again, in life you can learn from your mistakes, change your approach immediately, and try something new. And some life lessons can be so useful that they allow you to skip a few steps and get even closer to your goal. The coolest entrepreneurs say that you cannot beat someone who is playing and having fun. So be that person, because overall, you won't be able to build a nice career unless you're happy and enjoy what you do.

How to Build a Stress-Free IT Career

Stories, News & Mentions about GETWELL

Getwell’s Stories on HackerNoon