Employees can log into work from the comfort of their couch while raking it in as a nurse practitioner, sales associate or therapist.

Here are the top 10 side hustles that still allow you to work from home and earn up to $56 an hour—as firms like AT&T ban it | Fortune

In what spells more bad news for avid advocates of remote work, telecom giant AT&T has joined other high-profile RTO enforcers such as Amazon in mandating a five-days-a-week return to the office, starting January.

15 Companies Now Hiring Remote Jobs For 2025

Opening the roof at AT&T Stadium before Monday night's Texans-Cowboys game suddenly became dangerous.

Monday Night Football: Metal fragment falls from AT&T Stadium roof after opening before Texans-Cowboys game - Yahoo Sports

The Latest News and Updates in brought to you by the team at WTRF:

AT&T is providing extra safety support for families this Cybersecurity 
Awareness Month

IntelBroker claims the breach impacts Microsoft, SAP, AT&T, Verizon, T-Mobile US, and more

Cisco confirms ongoing probe into alleged data breach • The Register

According to Nvidia, AT&T is teaming with Quantiphi to create a conversational AI platform to assist employees with software development and financial services tasks.

Nvidia highlights AI software and services at D.C. AI Summit

Realty Income, AT&T, and Opera look like undervalued income plays.

3 Dividend Stocks That Are Screaming Buys in October

AT&T

PALO ALTO, USA, January 30th, 2025/CyberNewsWire/--SquareX discloses a new attack technique that shows how malicious extensions can be used to completely hijack the browser, and eventually, the whole device. Browser extensions have been under the spotlight in enterprise security news recently due to the wave of OAuth attacks on Chrome extension developers and data exfiltration attacks. However, until now, due to the limitations browser vendors place on the extension subsystem and extensions, it was thought to be impossible for extensions to gain full control of the browser, much less the device. SquareX researchers Dakshitaa Babu, Arpit Gupta, Sunkugari Tejeswara Reddy and Pankaj Sharma debunked this belief by demonstrating how attackers can use malicious extensions to escalate privileges to conduct a full browser and device takeover, all with minimal user interaction. Critically, the malicious extension only requires read/write capabilities present in the majority of browser extensions on the Chrome Store, including common productivity tools like Grammarly, Calendly and Loom, desensitizing users from granting these permissions. This revelation suggests that virtually any browser extension could potentially serve as an attack vector if created or taken over by an attacker. To the best of our understanding, extensions submitted to the Chrome Store requesting these capabilities are not put through additional security scrutiny at the time of this writing. The browser syncjacking attack can be broken up into three parts: how the extension silently adds a profile managed by the attacker, hijacks the browser and eventually gains full control of the device. Profile Hijacking The attack begins with an employee installing any browser extension - this could involve publishing one that masquerades as an AI tool or taking over existing popular extensions that may have up to millions of installations in aggregate. The extension then “silently” authenticates the victim into a Chrome profile managed by the attacker’s Google Workspace. This is all done in an automated manner in a background window, making the whole process almost imperceptible to the victim. Once this authentication occurs, the attacker has full control over the newly managed profile in the victim’s browser, allowing them to push automated policies such as disabling safe browsing and other security features. Using a very clever social engineering attack that exploits trusted domains, the adversary can then further escalate the profile hijacking attack to steal passwords from the victim’s browser. For example, the malicious extension can open and modify Google’s official support page on how to sync user accounts to prompt the victim to perform the sync with just a few clicks. Once the profile is synced, attackers have full access to all credentials and browsing history stored locally. As this attack only leverages legitimate sites and has no visible sign that it has been modified by the extension, it will not trigger any alarm bells in any security solutions monitoring the network traffic. Browser Takeover To achieve a full browser takeover, the attacker essentially needs to convert the victim’s Chrome browser into a managed browser. The same extension monitors and intercepts a legitimate download, such as a Zoom update, and replaces it with the attacker’s executable, which contains an enrollment token and registry entry to turn the victim’s Chrome browser into a managed browser. Thinking that they downloaded a Zoom updater, the victim executes the file, which ends up installing a registry entry that instructs the browser to become managed by the attacker’s Google Workspace. This allows the attacker to gain full control over the victim’s browser to disable security features, install additional malicious extensions, exfiltrate data and even silently redirect users to phishing sites. This attack is extremely potent as there is no visual difference between a managed and unmanaged browser. For a regular user, there is no telltale sign that a privilege escalation has occurred unless the victim is highly security aware and goes out of their way to regularly inspect their browser settings and look for associations with an unfamiliar Google Workspace account. Device Hijacking With the same downloaded file above, the attacker can additionally insert registry entries required for the malicious extension to message native apps. This allows the extension to directly interact with local apps without further authentication. Once the connection is established, attackers can use the extension in conjunction with the local shell and other available native applications to secretly turn on the device camera, capture audio, record screens and install malicious software - essentially providing full access to all applications and confidential data on the device. The browser syncjacking attack exposes a fundamental flaw in the way remote-managed profiles and browsers are managed. Today, anyone can create a managed workspace account tied to a new domain and a browser extension without any form of identity verification, making it impossible to attribute these attacks. Unfortunately, most enterprises currently have zero visibility into the browser - most do not have managed browsers or profiles, nor any visibility to the extensions employees are installing often based on trending tools and social media recommendations. What makes this attack particularly dangerous is that it operates with minimal permissions and nearly no user interaction, requiring only a subtle social engineering step using trusted websites - making it almost impossible for employees to detect. While recent incidents like the Cyberhaven breach have already compromised hundreds, if not thousands of organizations, those attacks required relatively complex social engineering to operate. The devastatingly subtle nature of this attack - with an extremely low threshold of user interaction - not only makes this attack extremely potent, but also sheds light on the terrifying possibility that adversaries are already using this technique to compromise enterprises today. Unless an organization chooses to completely block browser extensions via managed browsers, the browser syncjacking attack will completely bypass existing blacklists and permissions-based policies. SquareX’s founder Vivek Ramachandran says “This research exposes a critical blind spot in enterprise security. Traditional security tools simply can't see or stop these sophisticated browser-based attacks. What makes this discovery particularly alarming is how it weaponizes seemingly innocent browser extensions into complete device takeover tools, all while flying under the radar of conventional security measures like EDRs and SASE/SSE Secure Web Gateways. A Browser Detection-Response solution isn't just an option anymore - it's a necessity. Without visibility and control at the browser level, organizations are essentially leaving their front door wide open to attackers. This attack technique demonstrates why security needs to 'shift up' to where the threats are actually happening: in the browser itself.” SquareX has been conducting pioneering security research on browser extensions, including the DEF CON 32 talk Sneaky Extensions: The MV3 Escape Artists that revealed multiple MV3 compliant malicious extensions. This research team was also the first to discover and disclose the OAuth attack on Chrome extension developers one week before the Cyberhaven breach. SquareX was also responsible for the discovery of Last Mile Reassembly attacks, a new class of client-side attacks that exploits architectural flaws and completely bypasses all Secure Web Gateway solutions. Based on this research, SquareX’s industry-first Browser Detection and Response solution protects enterprises against advanced extension-based attacks including device hijacking attempts by conducting dynamic analysis on all browser extension activity at runtime, providing a risk score to all active extensions across the enterprise and further identifying any attacks that they may be vulnerable to. For more information about the browser syncjacking attack, additional findings from this research are available at sqrx.com/research. About SquareX SquareX helps organizations detect, mitigate and threat-hunt client-side web attacks happening against their users in real time. SquareX's industry-first Browser Detection and Response (BDR) solution, takes an attack-focused approach to browser security, ensuring enterprise users are protected against advanced threats like malicious QR Codes, Browser-in-the-Browser phishing, macro-based malware and other web attacks encompassing malicious files, websites, scripts, and compromised networks. Additionally, with SquareX, enterprises can provide contractors and remote workers with secure access to internal applications, enterprise SaaS, and convert the browsers on BYOD / unmanaged devices into trusted browsing sessions. Contact Head of PR Junice Liew SquareX junice@sqrx.com This story was distributed as a release by Cybernewswire under HackerNoon’s Business Blogging Program. Learn more about the program here PALO ALTO, USA, January 30th, 2025/CyberNewsWire/--SquareX discloses a new attack technique that shows how malicious extensions can be used to completely hijack the browser, and eventually, the whole device. Browser extensions have been under the spotlight in enterprise security news recently due to the wave of OAuth attacks on Chrome extension developers and data exfiltration attacks. However, until now, due to the limitations browser vendors place on the extension subsystem and extensions, it was thought to be impossible for extensions to gain full control of the browser, much less the device. SquareX researchers Dakshitaa Babu, Arpit Gupta, Sunkugari Tejeswara Reddy and Pankaj Sharma debunked this belief by demonstrating how attackers can use malicious extensions to escalate privileges to conduct a full browser and device takeover, all with minimal user interaction. SquareX SquareX Critically, the malicious extension only requires read/write capabilities present in the majority of browser extensions on the Chrome Store, including common productivity tools like Grammarly, Calendly and Loom, desensitizing users from granting these permissions. This revelation suggests that virtually any browser extension could potentially serve as an attack vector if created or taken over by an attacker. To the best of our understanding, extensions submitted to the Chrome Store requesting these capabilities are not put through additional security scrutiny at the time of this writing. The browser syncjacking attack can be broken up into three parts: how the extension silently adds a profile managed by the attacker, hijacks the browser and eventually gains full control of the device. Profile Hijacking The attack begins with an employee installing any browser extension - this could involve publishing one that masquerades as an AI tool or taking over existing popular extensions that may have up to millions of installations in aggregate. The extension then “silently” authenticates the victim into a Chrome profile managed by the attacker’s Google Workspace. This is all done in an automated manner in a background window, making the whole process almost imperceptible to the victim. Once this authentication occurs, the attacker has full control over the newly managed profile in the victim’s browser, allowing them to push automated policies such as disabling safe browsing and other security features. Using a very clever social engineering attack that exploits trusted domains, the adversary can then further escalate the profile hijacking attack to steal passwords from the victim’s browser. For example, the malicious extension can open and modify Google’s official support page on how to sync user accounts to prompt the victim to perform the sync with just a few clicks. Once the profile is synced, attackers have full access to all credentials and browsing history stored locally. As this attack only leverages legitimate sites and has no visible sign that it has been modified by the extension, it will not trigger any alarm bells in any security solutions monitoring the network traffic. Browser Takeover To achieve a full browser takeover, the attacker essentially needs to convert the victim’s Chrome browser into a managed browser. The same extension monitors and intercepts a legitimate download, such as a Zoom update, and replaces it with the attacker’s executable, which contains an enrollment token and registry entry to turn the victim’s Chrome browser into a managed browser. Thinking that they downloaded a Zoom updater, the victim executes the file, which ends up installing a registry entry that instructs the browser to become managed by the attacker’s Google Workspace. This allows the attacker to gain full control over the victim’s browser to disable security features, install additional malicious extensions, exfiltrate data and even silently redirect users to phishing sites. This attack is extremely potent as there is no visual difference between a managed and unmanaged browser. For a regular user, there is no telltale sign that a privilege escalation has occurred unless the victim is highly security aware and goes out of their way to regularly inspect their browser settings and look for associations with an unfamiliar Google Workspace account. Device Hijacking With the same downloaded file above, the attacker can additionally insert registry entries required for the malicious extension to message native apps. This allows the extension to directly interact with local apps without further authentication. Once the connection is established, attackers can use the extension in conjunction with the local shell and other available native applications to secretly turn on the device camera, capture audio, record screens and install malicious software - essentially providing full access to all applications and confidential data on the device. The browser syncjacking attack exposes a fundamental flaw in the way remote-managed profiles and browsers are managed. Today, anyone can create a managed workspace account tied to a new domain and a browser extension without any form of identity verification, making it impossible to attribute these attacks. Unfortunately, most enterprises currently have zero visibility into the browser - most do not have managed browsers or profiles, nor any visibility to the extensions employees are installing often based on trending tools and social media recommendations. What makes this attack particularly dangerous is that it operates with minimal permissions and nearly no user interaction, requiring only a subtle social engineering step using trusted websites - making it almost impossible for employees to detect. While recent incidents like the Cyberhaven breach have already compromised hundreds, if not thousands of organizations, those attacks required relatively complex social engineering to operate. The devastatingly subtle nature of this attack - with an extremely low threshold of user interaction - not only makes this attack extremely potent, but also sheds light on the terrifying possibility that adversaries are already using this technique to compromise enterprises today. Unless an organization chooses to completely block browser extensions via managed browsers, the browser syncjacking attack will completely bypass existing blacklists and permissions-based policies. SquareX’s founder Vivek Ramachandran says “This research exposes a critical blind spot in enterprise security. Traditional security tools simply can't see or stop these sophisticated browser-based attacks. What makes this discovery particularly alarming is how it weaponizes seemingly innocent browser extensions into complete device takeover tools, all while flying under the radar of conventional security measures like EDRs and SASE/SSE Secure Web Gateways. A Browser Detection-Response solution isn't just an option anymore - it's a necessity. Without visibility and control at the browser level, organizations are essentially leaving their front door wide open to attackers. This attack technique demonstrates why security needs to 'shift up' to where the threats are actually happening: in the browser itself.” SquareX’s founder Vivek Ramachandran says “This research exposes a critical blind spot in enterprise security. Traditional security tools simply can't see or stop these sophisticated browser-based attacks. What makes this discovery particularly alarming is how it weaponizes seemingly innocent browser extensions into complete device takeover tools, all while flying under the radar of conventional security measures like EDRs and SASE/SSE Secure Web Gateways. A Browser Detection-Response solution isn't just an option anymore - it's a necessity. Without visibility and control at the browser level, organizations are essentially leaving their front door wide open to attackers. This attack technique demonstrates why security needs to 'shift up' to where the threats are actually happening: in the browser itself.” Vivek Ramachandran Vivek Ramachandran SquareX has been conducting pioneering security research on browser extensions, including the DEF CON 32 talk Sneaky Extensions: The MV3 Escape Artists that revealed multiple MV3 compliant malicious extensions. Sneaky Extensions: The MV3 Escape Artists Sneaky Extensions: The MV3 Escape Artists This research team was also the first to discover and disclose the OAuth attack on Chrome extension developers one week before the Cyberhaven breach . SquareX was also responsible for the discovery of Last Mile Reassembly attacks, a new class of client-side attacks that exploits architectural flaws and completely bypasses all Secure Web Gateway solutions. OAuth attack on Chrome extension developers OAuth attack on Chrome extension developers Cyberhaven breach Cyberhaven breach Last Mile Reassembly Last Mile Reassembly Based on this research, SquareX’s industry-first Browser Detection and Response solution protects enterprises against advanced extension-based attacks including device hijacking attempts by conducting dynamic analysis on all browser extension activity at runtime, providing a risk score to all active extensions across the enterprise and further identifying any attacks that they may be vulnerable to. For more information about the browser syncjacking attack, additional findings from this research are available at sqrx.com/research . sqrx.com/research sqrx.com/research About SquareX SquareX helps organizations detect, mitigate and threat-hunt client-side web attacks happening against their users in real time. SquareX SquareX SquareX's industry-first Browser Detection and Response (BDR) solution, takes an attack-focused approach to browser security, ensuring enterprise users are protected against advanced threats like malicious QR Codes, Browser-in-the-Browser phishing, macro-based malware and other web attacks encompassing malicious files, websites, scripts, and compromised networks. Additionally, with SquareX, enterprises can provide contractors and remote workers with secure access to internal applications, enterprise SaaS, and convert the browsers on BYOD / unmanaged devices into trusted browsing sessions. Contact Head of PR Junice Liew SquareX junice@sqrx.com This story was distributed as a release by Cybernewswire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Cybernewswire under HackerNoon’s Business Blogging Program. Learn more about the program here here here

SquareX Discloses “Browser Syncjacking” , a New Attack Technique That Puts Millions At Risk

SquareX onthul "Browser Syncjacking", 'n nuwe aanvalstegniek wat miljoene in gevaar stel

SquareX раскрывае «сінджэк браўзера», новую тэхніку атакі, якая ставіць пад пагрозу мільёны

SquareX revela “Browser Syncjacking”, una nueva técnica de ataque que pone en riesgo a millones de personas

SquareX révèle le « Browser Syncjacking », une nouvelle technique d’attaque qui met des millions de personnes en danger

SquareX חושפת את "סינכרון דפדפן", טכניקת התקפה חדשה שמעמידה מיליונים בסיכון

SquareX、数百万人を危険にさらす新たな攻撃手法「ブラウザシンクジャッキング」を公開

SquareX миллиондаған адамдарға қауіп төндіретін «браузерлерді синхрондау» жаңа шабуыл әдісін ашады.

SquareX លាតត្រដាង "Browser Syncjacking" ដែលជាបច្ចេកទេសវាយប្រហារថ្មីដែលដាក់ហានិភ័យរាប់លាន

SquareX onthult ‘Browser Syncjacking’, een nieuwe aanvalstechniek die miljoenen mensen in gevaar brengt

SquareX odhaľuje „synchronizáciu prehliadača“, novú techniku útoku, ktorá ohrozuje milióny ľudí

SquareX, Milyonlarca Kişiyi Tehlikeye Sokan Yeni Bir Saldırı Tekniği Olan "Tarayıcı Senkronizasyon Saldırısı"nı Açıkladı

I-SquareX Idalula “Ukuvumelanisa Kwesiphequluli”, Indlela Entsha Yokuhlasela Ebeka Izigidi Engcupheni

BigQuery and Attribution Models Can Reveal What Really Drives E-Commerce Success

AI Agents Could Be Running Your Security Operations Center (SOC) To Prevent Attacks

Hackers are particularly good at one thing: Hacking. But hackers are particularly bad at another thing: Sports. Hackers who invest physical effort into their well-being are the minority. They use their bodies to perform organic duties, everything else falls into a clearly defined role model between brain and brain-container. The image of a pale, over-sugared and anti-social loner who invents Bitcoin at night in a disused factory in front of a fap station with 16 screens corresponds to the hacker’s ideal, but one thing usually becomes a problem with the hacker’s ideal: That the goal is to make the structure-porn that circulates in the hacker’s brain a reality, but structure-porn rarely succeeds on the first attempt. For structure-porn to get delivered successfully, many manual repetitions are necessary, and hackers hate repeating themselves. Hackers usually work with a puzzle-solving approach. The puzzle is considered as finished as soon as it has been solved. Solving the puzzle a second time is stupid because it has already been solved. I asked myself: Couldn’t a new approach be to solve the puzzle over and over again? To repeat the puzzle in an endless loop, like a bodybuilder in the gym works through his training program over and over again and builds up physical wealth, while hackers almost never build up physical wealth and become weaker and weaker under the increasing weights of technological progress? Maybe I’m a bit crazy, but with the staggering progress of large language models, Devin AI, and inference with increasing levels of education, I like to think that a Shaolin approach could countermeasure weak codebases. That is: Write the same piece of code a million times. I suggest an approach that I stole from the gym. The approach is called Repetition and goes like this: Write code.
Delete the code written in Step 1.
Repeat. We learn through repetition. The same principle applied in machine- and deep learning: the learning curve moves towards the optimum by Gradient Descent, in literature often represented by a ball rolling into a valley. The ball starts on a slope and will roll down the slope due to gravity. At the bottom of the valley, the ball has reached its optimum. It converged on the best possible configuration of its available resources. When we put our intentions into action, we create momentum. If we keep creating momentum in a repeated manner, our cognition will gradually converge to the best possible configuration. Millions of repetitions later, and the novice has become a master. Because this “essay” is about hackers, I prefer to say: wizards with cognitive abs. This is not an attempt to force you to go to the gym; I’m just forcing you to remember the motivations that inspired you to choose excellence. Delete what you have achieved and achieve it again. And again, and again, and again. Maybe your bachelor’s thesis is still lying around somewhere? Rewrite it. Bill Gates hates this trick, but it might work. Bill Gates said in an interview that he looks for lazy engineers during the recruiting process at Microsoft. His statement really excited the lazy engineers. In programming classes, we repeated the D.R.Y. mantra hundreds of times - in computer science classes, as well as in professional literature. “Don’t repeat yourself,” they said. “Abstract, refactor, but keep your points of truth on a short leash,” they said, but I think there is a bit of delusion in this. Most coders out there have swallowed the blue pill, so they prefer to code the easy, 3rd-partied way. I see the cause of modern software degeneration to be exactly here. The IT industry has always been driven by competition. Netscape vs Microsoft, Playstation vs XBox, Windows vs Linux … Not to mention the many thousands of start-up entrepreneurs who try to win every year. And while global climate policy melts the ice of Antarctica into mush layer by layer, the skillset of contemporary software development is melting into mush as well - layer by layer. As if the competition eats itself just for the sake of staying competitive. Break Fast and Move Things The modern programming style treats libraries and APIs like first-class citizens. I sometimes find myself wondering whether what I am developing is still my own work or just a Lego technology meta-object cobbled together from 3rd party software. We computer people call it Abstraction. It means something like “standing on the shoulders of giants” and claims that it is wiser to build on existing technology rather than reinventing the wheel every time. This implies that the modern IT landscape stands on a foundation that it does not understand. This one Adonis guy in the outdoor pool with abs and a 1-to-n relationship between himself and the ladies accumulated his physical wealth through repetition. He climbed the train again and again because pains -> gains. I think we lost the connection to painful programming, and therefore, the stamina to finish groundbreaking endeavors. Regain it. Hackers are particularly good at one thing: Hacking. But hackers are particularly bad at another thing: Sports. Hackers who invest physical effort into their well-being are the minority. They use their bodies to perform organic duties, everything else falls into a clearly defined role model between brain and brain-container. The image of a pale, over-sugared and anti-social loner who invents Bitcoin at night in a disused factory in front of a fap station with 16 screens corresponds to the hacker’s ideal, but one thing usually becomes a problem with the hacker’s ideal: That the goal is to make the structure-porn that circulates in the hacker’s brain a reality, but structure-porn rarely succeeds on the first attempt. For structure-porn to get delivered successfully, many manual repetitions are necessary, and hackers hate repeating themselves. That the goal is to make the structure-porn that circulates in the hacker’s brain a reality, but structure-porn rarely succeeds on the first attempt. For structure-porn to get delivered successfully, many manual repetitions are necessary, and hackers hate repeating themselves. Hackers usually work with a puzzle-solving approach. The puzzle is considered as finished as soon as it has been solved. Solving the puzzle a second time is stupid because it has already been solved. I asked myself: Couldn’t a new approach be to solve the puzzle over and over again? To repeat the puzzle in an endless loop, like a bodybuilder in the gym works through his training program over and over again and builds up physical wealth, while hackers almost never build up physical wealth and become weaker and weaker under the increasing weights of technological progress? Maybe I’m a bit crazy, but with the staggering progress of large language models, Devin AI, and inference with increasing levels of education, I like to think that a Shaolin approach could countermeasure weak codebases. That is: Write the same piece of code a million times. I suggest an approach that I stole from the gym. The approach is called Repetition and goes like this: Repetition Write code. Delete the code written in Step 1. Repeat. Write code. Delete the code written in Step 1. Repeat. We learn through repetition. The same principle applied in machine- and deep learning: the learning curve moves towards the optimum by Gradient Descent , in literature often represented by a ball rolling into a valley. The ball starts on a slope and will roll down the slope due to gravity. At the bottom of the valley, the ball has reached its optimum. It converged on the best possible configuration of its available resources. Gradient Descent When we put our intentions into action, we create momentum. If we keep creating momentum in a repeated manner, our cognition will gradually converge to the best possible configuration. Millions of repetitions later, and the novice has become a master. Because this “essay” is about hackers, I prefer to say: wizards with cognitive abs. This is not an attempt to force you to go to the gym; I’m just forcing you to remember the motivations that inspired you to choose excellence. Delete what you have achieved and achieve it again. And again, and again, and again. Maybe your bachelor’s thesis is still lying around somewhere? Rewrite it. Bill Gates hates this trick, but it might work. Bill Gates said in an interview that he looks for lazy engineers during the recruiting process at Microsoft. His statement really excited the lazy engineers. In programming classes, we repeated the D.R.Y. mantra hundreds of times - in computer science classes, as well as in professional literature. “Don’t repeat yourself,” they said. “Abstract, refactor, but keep your points of truth on a short leash,” they said, but I think there is a bit of delusion in this. Most coders out there have swallowed the blue pill, so they prefer to code the easy, 3rd-partied way. I see the cause of modern software degeneration to be exactly here. The IT industry has always been driven by competition. Netscape vs Microsoft, Playstation vs XBox, Windows vs Linux … Not to mention the many thousands of start-up entrepreneurs who try to win every year. And while global climate policy melts the ice of Antarctica into mush layer by layer, the skillset of contemporary software development is melting into mush as well - layer by layer. As if the competition eats itself just for the sake of staying competitive. Break Fast and Move Things The modern programming style treats libraries and APIs like first-class citizens. I sometimes find myself wondering whether what I am developing is still my own work or just a Lego technology meta-object cobbled together from 3rd party software. We computer people call it Abstraction . It means something like “standing on the shoulders of giants” and claims that it is wiser to build on existing technology rather than reinventing the wheel every time. This implies that the modern IT landscape stands on a foundation that it does not understand. Abstraction This one Adonis guy in the outdoor pool with abs and a 1-to-n relationship between himself and the ladies accumulated his physical wealth through repetition. He climbed the train again and again because pains -> gains. I think we lost the connection to painful programming, and therefore, the stamina to finish groundbreaking endeavors. Regain it.

Attention Hackers - Work on Yourself

Today on X (formerly Twitter), Skycoin founder Brandon Smietana formally demanded a public apology and retraction from Condé Nast and its flagship media, The New Yorker. The demand follows the publication of an article titled “Pumpers, Dumpers, and Shills: The Skycoin Saga” in August 2021, which Smietana alleges is filled with false claims and fabrications. “Today, I am demanding a formal, public apology and retraction from Condé Nast and its flagship media, The New Yorker, for their defamatory article, Pumpers, Dumpers, and Shills: The Skycoin Saga. These allegations have threatened my and my company’s reputation, while putting my family’s safety at risk! This isn’t just about me and my personal vendettas — this is about holding the media accountable! No one should have the power to fabricate stories and put profits over integrity. It has been years since the article’s publication, and many of its claims have been proven false. Yet, the article remains. After all of this time, The New Yorker has failed to apologize to me for publishing its damaging words.” False Claims in “The Skycoin Saga” The article, written by Morgan Peck, highlights the need for accountability in the media. To start, Peck recounts accusations of Smietana’s involvement in dumping the Skycoin. Immediately after Binance listed the token, its price sank. Sell-offs ran rampant. With its community demanding answers, the project’s Chinese marketing team kidnapped Smietana. The kidnapping happened because Harrison Gevritz and Adam Young of EWA were attempting to take over Skycoin as a company by pressuring Brandon to sell it to them or risk it being destroyed under their actions. Brandon Smietana was released shortly later. Peck falsely stated that these kidnappers were let go without serving prison time. Peck ignored public records and criminal filings from China that confirmed each perpetrator was arrested, confessed, and was sentenced to prison, while the “orchestrators” remain the ones unpunished. Moreover, Peck’s article includes fabricated quotes from key witnesses such as Michael Terpin. When reached out to by The New Yorker fact-checker Anna Boots, Terpin noted such discrepancies. Regardless, the published article retained these false quotes. As detailed by Bitcoinist, The New Yorker sent Smietana 198 questions as a part of their fact-checking process. “I did my best to answer them as well as I could,” he said. “I gave her the documents, and she agreed and said, ‘This statement is untrue. And yet, she published it. She put the same statement in the article that she admitted to me she knew to be false.” Peck’s defamatory article slanders ’s reputation — and Skycoin’s as a byproduct — and mitigates the founder’s positive effects on the crypto space. For example, Smietana went to the Shanghai Supreme Court, the highest court in the country, and won the first case in China to declare Bitcoin legal property — a landmark case he carried out while under court and police protection. This legal victory was significant not just for Smietana but for cryptocurrency as a whole. The recognition of Bitcoin as a legal asset broke through China’s strict regulatory policies, bringing the asset legitimacy in the eyes of an otherwise stringent government. It leaves one to wonder why Peck and The New Yorker would ignore such important information. The Personal Impact on Smietana Smietana’s personal life has greatly suffered from Peck’s misreporting. To this day, Smietana’s family are the targets of various harassment campaigns, including death threats and persecution from The Daily Stormer, a neo-Nazi media. The Daily Stormer continued where The New Yorker left off, accusing Smietana of hiring “assassins” to eliminate Bradford Stephens, a former member of the Skycoin marketing team. Peck published her article in 2021. It’s 2024 now, and its resonance continues to plague Smietana and his family. This isn’t to mention the damage to Skycoin’s credibility, which has forced the company to overcome hurdles to attract new customers. Systemic Failures at Condé Nast These issues point to a broader ethical problem at Condé Nast. In addition to the hit piece on Smietana, the mass media company has been accused of workplace discrimination, editorial manipulation, and union disputes. In fact, there is evidence that Peck and her affiliates had been bribed to write such a hit piece. Shortly after Skycoin paid Peck for a promotional piece, the journalist contacted Smietana, asking for additional money during the COVID-19 pandemic. Smietana declined. It is believed that Peck sought funds from those who had grievances against Smietana. In 2023, Smietana learned of naysayers paying Peck to defame him. Bribery would explain Peck’s ignorance of the facts — ones that Boots and Terpin highlighted long before publication. It’s worth noting that Boots later resigned from her fact-checker position. Smietana’s case is not isolated. It highlights the need for media accountability and journalistic integrity, showing the real consequences of defamation and unverified information. When outlets known for their integrity publish misinterpreted stories, the effects can be devastating for those involved, and those effects extend to the industries and companies they work for. Overall, Smietana’s demand for an apology concerns more than his personal problems. Influential figures within the crypto industry are often under fire from the traditional media, which misrepresents cryptocurrencies and presents them in a negative light. This case serves as yet another reminder of the power and influence these outlets carry and the harm they so easily produce. Today on X (formerly Twitter), Skycoin founder Brandon Smietana formally demanded a public apology and retraction from Condé Nast and its flagship media, The New Yorker. The demand follows the publication of an article titled “Pumpers, Dumpers, and Shills: The Skycoin Saga” in August 2021, which Smietana alleges is filled with false claims and fabrications. demanded demanded “Today, I am demanding a formal, public apology and retraction from Condé Nast and its flagship media, The New Yorker, for their defamatory article, Pumpers, Dumpers, and Shills: The Skycoin Saga. These allegations have threatened my and my company’s reputation, while putting my family’s safety at risk! “Today, I am demanding a formal, public apology and retraction from Condé Nast and its flagship media, The New Yorker, for their defamatory article, Pumpers, Dumpers, and Shills: The Skycoin Saga. These allegations have threatened my and my company’s reputation, while putting my family’s safety at risk! “Today, I am demanding a formal, public apology and retraction from Condé Nast and its flagship media, The New Yorker, for their defamatory article, Pumpers, Dumpers, and Shills: The Skycoin Saga. These allegations have threatened my and my company’s reputation, while putting my family’s safety at risk! This isn’t just about me and my personal vendettas — this is about holding the media accountable! No one should have the power to fabricate stories and put profits over integrity. It has been years since the article’s publication, and many of its claims have been proven false. Yet, the article remains. After all of this time, The New Yorker has failed to apologize to me for publishing its damaging words.” This isn’t just about me and my personal vendettas — this is about holding the media accountable! No one should have the power to fabricate stories and put profits over integrity. It has been years since the article’s publication, and many of its claims have been proven false. Yet, the article remains. After all of this time, The New Yorker has failed to apologize to me for publishing its damaging words.” This isn’t just about me and my personal vendettas — this is about holding the media accountable! No one should have the power to fabricate stories and put profits over integrity. It has been years since the article’s publication, and many of its claims have been proven false. Yet, the article remains. After all of this time, The New Yorker has failed to apologize to me for publishing its damaging words.” False Claims in “The Skycoin Saga” The article, written by Morgan Peck, highlights the need for accountability in the media. To start, Peck recounts accusations of Smietana’s involvement in dumping the Skycoin. Immediately after Binance listed the token, its price sank. Sell-offs ran rampant. With its community demanding answers, the project’s Chinese marketing team kidnapped Smietana. The kidnapping happened because Harrison Gevritz and Adam Young of EWA were attempting to take over Skycoin as a company by pressuring Brandon to sell it to them or risk it being destroyed under their actions. Brandon Smietana was released shortly later. Peck falsely stated that these kidnappers were let go without serving prison time. Peck ignored public records and criminal filings from China that confirmed each perpetrator was arrested, confessed, and was sentenced to prison, while the “orchestrators” remain the ones unpunished. confirmed confirmed Moreover, Peck’s article includes fabricated quotes from key witnesses such as Michael Terpin. When reached out to by The New Yorker fact-checker Anna Boots, Terpin noted such discrepancies. Regardless, the published article retained these false quotes. The New Yorker As detailed by Bitcoinist , The New Yorker sent Smietana 198 questions as a part of their fact-checking process. “I did my best to answer them as well as I could,” he said. “I gave her the documents, and she agreed and said, ‘This statement is untrue. And yet, she published it. She put the same statement in the article that she admitted to me she knew to be false.” Bitcoinist Bitcoinist The New Yorker Peck’s defamatory article slanders ’s reputation — and Skycoin’s as a byproduct — and mitigates the founder’s positive effects on the crypto space. For example, Smietana went to the Shanghai Supreme Court, the highest court in the country, and won the first case in China to declare Bitcoin legal property — a landmark case he carried out while under court and police protection. This legal victory was significant not just for Smietana but for cryptocurrency as a whole. The recognition of Bitcoin as a legal asset broke through China’s strict regulatory policies, bringing the asset legitimacy in the eyes of an otherwise stringent government. It leaves one to wonder why Peck and The New Yorker would ignore such important information. The New Yorker The Personal Impact on Smietana Smietana’s personal life has greatly suffered from Peck’s misreporting. To this day, Smietana’s family are the targets of various harassment campaigns, including death threats and persecution from The Daily Stormer , a neo-Nazi media. The Daily Stormer The Daily Stormer continued where The New Yorker left off, accusing Smietana of hiring “assassins” to eliminate Bradford Stephens, a former member of the Skycoin marketing team. The Daily Stormer The New Yorker Peck published her article in 2021. It’s 2024 now, and its resonance continues to plague Smietana and his family. This isn’t to mention the damage to Skycoin’s credibility, which has forced the company to overcome hurdles to attract new customers. Systemic Failures at Condé Nast These issues point to a broader ethical problem at Condé Nast. In addition to the hit piece on Smietana, the mass media company has been accused of workplace discrimination , editorial manipulation, and union disputes. workplace discrimination workplace discrimination In fact, there is evidence that Peck and her affiliates had been bribed to write such a hit piece. Shortly after Skycoin paid Peck for a promotional piece, the journalist contacted Smietana, asking for additional money during the COVID-19 pandemic. Smietana declined. It is believed that Peck sought funds from those who had grievances against Smietana. In 2023, Smietana learned of naysayers paying Peck to defame him. Bribery would explain Peck’s ignorance of the facts — ones that Boots and Terpin highlighted long before publication. It’s worth noting that Boots later resigned from her fact-checker position. Smietana’s case is not isolated. It highlights the need for media accountability and journalistic integrity, showing the real consequences of defamation and unverified information. When outlets known for their integrity publish misinterpreted stories , the effects can be devastating for those involved, and those effects extend to the industries and companies they work for. Overall, Smietana’s demand for an apology concerns more than his personal problems. Influential figures within the crypto industry are often under fire from the traditional media, which misrepresents cryptocurrencies and presents them in a negative light. misinterpreted stories This case serves as yet another reminder of the power and influence these outlets carry and the harm they so easily produce. This case serves as yet another reminder of the power and influence these outlets carry and the harm they so easily produce.

The New Yorker's Attack on Skycoin: A Case Study in Media Bias

The Frame Defines the Picture I recently encountered a fascinating graphic puzzle. Trying to solve it brought to mind a concept frequently discussed in problem-solving and critical thinking. The puzzle is shown below. What is your answer? Problem-solving methods span a spectrum from unstructured to highly structured. Some individuals dive straight into the problem, while others may devise a detailed plan of action. There are also those who adopt a hybrid approach. Unstructured problem-solvers would’ve delved in and then realized — we need to understand what a “date” means. Structured problem-solvers would’ve probably questioned the term “date” first, and then decided upon the solution. Whichever route you took, you would at some time, and in some form, question the concept of “date.” You would’ve questioned the essential term or definition. In doing that, you would’ve automatically questioned the assumptions and concepts associated with the term. You would also have realized that your solution depends significantly on how you interpret the concept of a “date.” “There is no single right answer or path forward, but there is one right way to frame the problem.” — Clayton Christensen (Harvard Professor) What is a “date”? According to the dictionary, a date is: a social or romantic appointment or engagement. Clarifying the key term establishes the essential foundation for addressing the problem. Based on our context, we can further adapt this theoretical definition to a more practical version. The concept of a “date” may be interpreted as more romantic than social, or the other way around. Once the foundation is established, you can delve into the specifics with that knowledge as your guide. Examine the graphics — the handbags, suitors, settings, menu cards, etc. — to uncover additional clues and assumptions. Iterating this knowledge through various scenarios will lead to a solution. Could you reach a solution without defining “date”? Potentially. Such a solution, however, will not be cohesive or defensible. You will struggle to demonstrate the logic chain that underpins your answer. Plus, anyone else will also be able to convince you with their answer; an equivocal solution is not really a solution. This puzzle demonstrates that grasping key terms and definitions lays a strong groundwork for problem-solving. It’s akin to a concealed superpower. By discerning the crucial definition, you reveal underlying assumptions. These two influence how you frame the problem. How we frame the problem directly impacts the solution. Definitions + Assumptions = FrameFrame → Solution. So, next time you’re faced with a problem, pause for a moment. Understand the key definition(s). Think critically. Determine fundamentals. Unearth assumptions. Only then, attempt a solution. This may appear counterintuitive compared to our instinct to delve in, but it produces more cohesive solutions and is quicker than one anticipates. If you enjoyed this post, you will like my book 📗 Smart Problem Solving which provides practical guidance on problem-solving. The Frame Defines the Picture I recently encountered a fascinating graphic puzzle. Trying to solve it brought to mind a concept frequently discussed in problem-solving and critical thinking. The puzzle is shown below. What is your answer? Problem-solving methods span a spectrum from unstructured to highly structured. Some individuals dive straight into the problem, while others may devise a detailed plan of action. There are also those who adopt a hybrid approach. Unstructured problem-solvers would’ve delved in and then realized — we need to understand what a “date” means. Structured problem-solvers would’ve probably questioned the term “date” first, and then decided upon the solution. Whichever route you took, you would at some time, and in some form, question the concept of “date.” Whichever route you took, you would at some time, and in some form, question the concept of “date.” You would’ve questioned the essential term or definition. essential In doing that, you would’ve automatically questioned the assumptions and concepts associated with the term. You would also have realized that your solution depends significantly on how you interpret the concept of a “date.” “There is no single right answer or path forward, but there is one right way to frame the problem.” — Clayton Christensen (Harvard Professor) “There is no single right answer or path forward, but there is one right way to frame the problem.” — Clayton Christensen (Harvard Professor) Clayton Christensen Clayton Christensen What is a “date”? According to the dictionary, a date is: a social or romantic appointment or engagement. What is a “date”? According to the dictionary, a date is: a social or romantic appointment or engagement. Clarifying the key term establishes the essential foundation for addressing the problem. Clarifying the key term establishes the essential foundation for addressing the problem. Based on our context, we can further adapt this theoretical definition to a more practical version. The concept of a “date” may be interpreted as more romantic than social, or the other way around. Once the foundation is established, you can delve into the specifics with that knowledge as your guide. Examine the graphics — the handbags, suitors, settings, menu cards, etc. — to uncover additional clues and assumptions. Iterating this knowledge through various scenarios will lead to a solution. Could you reach a solution without defining “date”? Potentially. Such a solution, however, will not be cohesive or defensible. You will struggle to demonstrate the logic chain that underpins your answer. Plus, anyone else will also be able to convince you with their answer; an equivocal solution is not really a solution. This puzzle demonstrates that grasping key terms and definitions lays a strong groundwork for problem-solving. It’s akin to a concealed superpower. By discerning the crucial definition, you reveal underlying assumptions. These two influence how you frame the problem. How we frame the problem directly impacts the solution. Definitions + Assumptions = FrameFrame → Solution. Definitions + Assumptions = Frame Frame → Solution. So, next time you’re faced with a problem, pause for a moment. Understand the key definition(s). Think critically. Determine fundamentals. Unearth assumptions. Only then, attempt a solution. This may appear counterintuitive compared to our instinct to delve in, but it produces more cohesive solutions and is quicker than one anticipates. If you enjoyed this post, you will like my book 📗 Smart Problem Solving which provides practical guidance on problem-solving. If you enjoyed this post, you will like my book 📗 Smart Problem Solving which provides practical guidance on problem-solving. Smart Problem Solving Smart Problem Solving Smart Problem Solving

Pay Special Attention to Definitions When Solving a Problem

Authors:
(1) Diwen Xue, University of Michigan;
(2) Reethika Ramesh, University of Michigan;
(3) Arham Jain, University of Michigan;
(4) Arham Jain, Merit Network, Inc.;
(5) J. Alex Halderman, University of Michigan;
(6) Jedidiah R. Crandall, Arizona State University/Breakpointing Bad;
(7) Roya Ensaf, University of Michigan. Table of Links Abstract and 1 Introduction 2 Background & Related Work 3 Challenges in Real-world VPN Detection 4 Adversary Model and Deployment 5 Ethics, Privacy, and Responsible Disclosure 6 Identifying Fingerprintable Features and 6.1 Opcode-based Fingerprinting 6.2 ACK-based Fingerprinting 6.3 Active Server Fingerprinting 6.4 Constructing Filters and Probers 7 Fine-tuning for Deployment and 7.1 ACK Fingerprint Thresholds 7.2 Choice of Observation Window N 7.3 Effects of Packet Loss 7.4 Server Churn for Asynchronous Probing 7.5 Probe UDP and Obfuscated OpenVPN Servers 8 Real-world Deployment Setup 9 Evaluation & Findings and 9.1 Results for control VPN flows 9.2 Results for all flows 10 Discussion and Mitigations 11 Conclusion 12 Acknowledgement and References Appendix 11 Conclusion We have demonstrated that OpenVPN, even with widely applied obfuscation techniques, can be reliably detected and blocked at-scale by network-based adversaries. Inspired by previous real-world censorship events, we designed a twophase system that performs passive filtering followed by active probing to fingerprint OpenVPN flows. We evaluated the practicality of our approach in partnership with a mid-size ISP, and we were able to identify the majority of vanilla and obfuscated OpenVPN flows with only negligible false positives, which supports that the techniques we describe would be practical even for adversaries averse to collateral damage. Users worldwide rely on VPNs to protect their security and privacy and to escape Internet censorship, yet the ease of fingerprinting OpenVPN traffic and the commodification of DPI technologies bring monitoring and blocking of popular VPN services within reach for almost any network operator. We propose several short-term mitigations that can help defend against these threats, but in the long term, we urge VPN providers to adopt more resilient and better standardized obfuscation approaches. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Diwen Xue, University of Michigan; (2) Reethika Ramesh, University of Michigan; (3) Arham Jain, University of Michigan; (4) Arham Jain, Merit Network, Inc.; (5) J. Alex Halderman, University of Michigan; (6) Jedidiah R. Crandall, Arizona State University/Breakpointing Bad; (7) Roya Ensaf, University of Michigan. Authors: Authors: (1) Diwen Xue, University of Michigan; (2) Reethika Ramesh, University of Michigan; (3) Arham Jain, University of Michigan; (4) Arham Jain, Merit Network, Inc.; (5) J. Alex Halderman, University of Michigan; (6) Jedidiah R. Crandall, Arizona State University/Breakpointing Bad; (7) Roya Ensaf, University of Michigan. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 Background & Related Work 2 Background & Related Work 3 Challenges in Real-world VPN Detection 3 Challenges in Real-world VPN Detection 4 Adversary Model and Deployment 4 Adversary Model and Deployment 5 Ethics, Privacy, and Responsible Disclosure 5 Ethics, Privacy, and Responsible Disclosure 6 Identifying Fingerprintable Features and 6.1 Opcode-based Fingerprinting 6 Identifying Fingerprintable Features and 6.1 Opcode-based Fingerprinting 6.2 ACK-based Fingerprinting 6.2 ACK-based Fingerprinting 6.3 Active Server Fingerprinting 6.3 Active Server Fingerprinting 6.4 Constructing Filters and Probers 6.4 Constructing Filters and Probers 7 Fine-tuning for Deployment and 7.1 ACK Fingerprint Thresholds 7 Fine-tuning for Deployment and 7.1 ACK Fingerprint Thresholds 7.2 Choice of Observation Window N 7.2 Choice of Observation Window N 7.3 Effects of Packet Loss 7.3 Effects of Packet Loss 7.4 Server Churn for Asynchronous Probing 7.4 Server Churn for Asynchronous Probing 7.5 Probe UDP and Obfuscated OpenVPN Servers 7.5 Probe UDP and Obfuscated OpenVPN Servers 8 Real-world Deployment Setup 8 Real-world Deployment Setup 9 Evaluation & Findings and 9.1 Results for control VPN flows 9 Evaluation & Findings and 9.1 Results for control VPN flows 9.2 Results for all flows 9.2 Results for all flows 10 Discussion and Mitigations 10 Discussion and Mitigations 11 Conclusion 11 Conclusion 12 Acknowledgement and References 12 Acknowledgement and References Appendix Appendix 11 Conclusion We have demonstrated that OpenVPN, even with widely applied obfuscation techniques, can be reliably detected and blocked at-scale by network-based adversaries. Inspired by previous real-world censorship events, we designed a twophase system that performs passive filtering followed by active probing to fingerprint OpenVPN flows. We evaluated the practicality of our approach in partnership with a mid-size ISP, and we were able to identify the majority of vanilla and obfuscated OpenVPN flows with only negligible false positives, which supports that the techniques we describe would be practical even for adversaries averse to collateral damage. Users worldwide rely on VPNs to protect their security and privacy and to escape Internet censorship, yet the ease of fingerprinting OpenVPN traffic and the commodification of DPI technologies bring monitoring and blocking of popular VPN services within reach for almost any network operator. We propose several short-term mitigations that can help defend against these threats, but in the long term, we urge VPN providers to adopt more resilient and better standardized obfuscation approaches. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

OpenVPN Detection Risks: Scaling Attacks and Calls for Stronger Obfuscation

Relationships at work are important since we are social animals - early experiences with human connection shape how we interact with others as adults, including at work. In the age of AI agents, human connection is what sets us apart, emphasizing empathy, creativity, and nuanced understanding of each other. Strong relationships are key in collaboration, driving innovation, and enabling well-rounded discussions that AI cannot replicate (yet?). Moreover, your relationship patterns can influence your career decisions, work performance, and more so it’s useful to understand them. 1 Attachment Theory Origin and Relationships at Work Attachment theory, initially developed by John Bowlby in the mid-20th century, is a powerful tool to understand how we connect with others. Originally, the theory focused on understanding infant-mother relationships and how early emotional bonds influence development. Mary Ainsworth expanded on Bowlby’s work with her famous Strange Situation experiments, revealing that children exhibit different attachment styles—secure, avoidant, and anxious—depending on their experiences with caregivers. To better understand the experiment, you can watch the video recording below. Warning: it can be distressing for some people so take a deep breath before watching. https://youtu.be/woQhp28ndik?si=Dvl0aMo4WA7GQXb1&embedable=true How is this related to work? Well, over time, attachment theory has evolved. Researchers like Cindy Hazan and Phillip Shaver applied the theory to adult romantic relationships, demonstrating how the attachment patterns formed in childhood influence how we bond in adult relationships. Whether avoidant, anxious, or secure, these early patterns affect the way we love, trust, and interact with others throughout our lives. But attachment theory isn’t just relevant to personal relationships, it relates to relationships at work too. Today, its application has broadened to include fields such as healthcare, management, and organizational behaviors, thanks to scholars like Mario Mikulincer with Phillip Shaver. It turns out, our attachment tendencies—especially insecurity in attachment—can deeply impact how we behave at work and influence our satisfaction and performance in the workplace. 2 Attachment Insecurity and Its Impact on Relationships at Work Attachment insecurity, characterized by patterns of avoidance or anxiety, can cause several issues in workplace dynamics according to a meta-analysis of the existing research. These attachment tendencies, which stem from early life experiences, influence how we form relationships with colleagues, handle stress, and perceive feedback from supervisors. Here’s a breakdown of the workplace challenges that arise due to attachment insecurity: (You might want to take a deep breath again) 2.1 Excessive Independence Do you prefer working alone and often shy away from collaborating with others? This tendency is common in those with attachment avoidance. If you are avoidantly attached, you may resist relying on others and avoid interpersonal closeness in professional settings. While independence can be valuable, excessive independence can create feelings of isolation and lack of support. How do you feel about asking for help? Over time, these feelings can lead to burnout or dissatisfaction, as working in isolation without support structures may cause individuals to feel disconnected from their teams. Eventually, this environment fosters thoughts of leaving the job altogether. 2.2 Trust Issues and Strained Relationships at Work Attachment avoidance also often leads to trust issues at work. When people struggle to trust or rely on colleagues and supervisors, the workplace can become a challenging and even hostile environment. People with high avoidance may find themselves disengaged, unable to form strong team bonds, or feel uncomfortable working under leadership. This lack of trust can make it difficult to thrive in collaborative environments. As mentioned in the previous point, this can lead to thoughts of quitting as the workplace begins to feel increasingly unwelcoming. 2.3 Job Dissatisfaction For those with attachment anxiety, the need for constant validation can be overwhelming. At work, this translates into a desire for continual praise and reassurance about performance. Without it, there could be a growing feeling of job dissatisfaction. Emotional needs go unmet, leading to feelings of inadequacy and concern over whether they’re performing well enough. This dissatisfaction can build up over time, particularly if managers don’t regularly acknowledge the employee's contributions. Those with attachment anxiety may also feel more stressed and vulnerable to burnout as they continuously seek [positive] feedback that never feels sufficient. 2.4 High-Stress Levels and Burnout Both attachment anxiety and avoidance are linked to heightened stress in the workplace. Anxiously attached individuals often struggle with the fear of rejection and worry about how their efforts are perceived. This need for constant reassurance can lead to burnout, as individuals feel pressured to meet perceived expectations. On the other hand, avoidant individuals may cope with workplace stress by overworking or avoiding difficult conversations, such as performance reviews, to maintain their distance. This avoidance leads to overload, as tasks pile up and go unresolved. In both cases, stress levels rise, contributing to an unsustainable work-life balance (or integration). 3 Understanding Your Triggers From Relationships at Work If you relate to any of these descriptions, take time to reflect on the situations and interactions at work that might trigger your thoughts of leaving the job and similar reactions. Attachment theory teaches us that our early experiences shape how we approach relationships, including those at work. Our thoughts and emotions act as signals, helping us understand what matters most to us. Sometimes, those signals can be influenced by past experience and it can be difficult to understand your patterns realistically. In that case, it could be helpful to discuss your patterns with a psychotherapist. By understanding your specific attachment patterns, you can make more informed decisions about your career and relationships at work. Once you’re aware of these patterns, you can use tools like SWOT analysis to evaluate whether staying in your current role aligns with your values and needs—or whether it’s time to move on to a new opportunity. 💡 Thank you for making it here. If you enjoyed reading this story you might like my weekly posts on Instagram too. Relationships at work are important since we are social animals - early experiences with human connection shape how we interact with others as adults, including at work. In the age of AI agents, human connection is what sets us apart, emphasizing empathy, creativity, and nuanced understanding of each other. Strong relationships are key in collaboration, driving innovation, and enabling well-rounded discussions that AI cannot replicate (yet?). Moreover, your relationship patterns can influence your career decisions, work performance, and more so it’s useful to understand them. 1 Attachment Theory Origin and Relationships at Work Attachment theory , initially developed by John Bowlby in the mid-20th century, is a powerful tool to understand how we connect with others. Originally, the theory focused on understanding infant-mother relationships and how early emotional bonds influence development. theory John Bowlby Mary Ainsworth expanded on Bowlby’s work with her famous Strange Situation experiments, revealing that children exhibit different attachment styles—secure, avoidant, and anxious—depending on their experiences with caregivers. To better understand the experiment, you can watch the video recording below. Mary Ainsworth Strange Situation Warning: it can be distressing for some people so take a deep breath before watching. Warning: https://youtu.be/woQhp28ndik?si=Dvl0aMo4WA7GQXb1&embedable=true https://youtu.be/woQhp28ndik?si=Dvl0aMo4WA7GQXb1&embedable=true How is this related to work? Well, over time, attachment theory has evolved. Researchers like Cindy Hazan and Phillip Shaver applied the theory to adult romantic relationships, demonstrating how the attachment patterns formed in childhood influence how we bond in adult relationships. Whether avoidant, anxious, or secure, these early patterns affect the way we love, trust, and interact with others throughout our lives. Cindy Hazan and Phillip Shaver Cindy Hazan and Phillip Shaver But attachment theory isn’t just relevant to personal relationships, it relates to relationships at work too. Today, its application has broadened to include fields such as healthcare, management, and organizational behaviors, thanks to scholars like Mario Mikulincer with Phillip Shaver. relationships at work Mario Mikulincer It turns out, our attachment tendencies—especially insecurity in attachment—can deeply impact how we behave at work and influence our satisfaction and performance in the workplace. It turns out, our attachment tendencies—especially insecurity in attachment—can deeply impact how we behave at work and influence our satisfaction and performance in the workplace. 2 Attachment Insecurity and Its Impact on Relationships at Work Attachment insecurity , characterized by patterns of avoidance or anxiety , can cause several issues in workplace dynamics according to a meta-analysis of the existing research. These attachment tendencies, which stem from early life experiences, influence how we form relationships with colleagues, handle stress, and perceive feedback from supervisors. Here’s a breakdown of the workplace challenges that arise due to attachment insecurity: Attachment insecurity avoidance anxiety meta-analysis relationships with colleagues, handle stress, and perceive feedback (You might want to take a deep breath again) 2.1 Excessive Independence 2.1 Excessive Independence Do you prefer working alone and often shy away from collaborating with others? This tendency is common in those with attachment avoidance. If you are avoidantly attached, you may resist relying on others and avoid interpersonal closeness in professional settings. While independence can be valuable, excessive independence can create feelings of isolation and lack of support. How do you feel about asking for help? Over time, these feelings can lead to burnout or dissatisfaction, as working in isolation without support structures may cause individuals to feel disconnected from their teams. Eventually, this environment fosters thoughts of leaving the job altogether. 2.2 Trust Issues and Strained Relationships at Work Attachment avoidance also often leads to trust issues at work. When people struggle to trust or rely on colleagues and supervisors, the workplace can become a challenging and even hostile environment. People with high avoidance may find themselves disengaged, unable to form strong team bonds, or feel uncomfortable working under leadership. This lack of trust can make it difficult to thrive in collaborative environments. As mentioned in the previous point, this can lead to thoughts of quitting as the workplace begins to feel increasingly unwelcoming. 2.3 Job Dissatisfaction For those with attachment anxiety, the need for constant validation can be overwhelming. At work, this translates into a desire for continual praise and reassurance about performance. Without it, there could be a growing feeling of job dissatisfaction. Emotional needs go unmet, leading to feelings of inadequacy and concern over whether they’re performing well enough. This dissatisfaction can build up over time, particularly if managers don’t regularly acknowledge the employee's contributions. Those with attachment anxiety may also feel more stressed and vulnerable to burnout as they continuously seek [positive] feedback that never feels sufficient. 2.4 High-Stress Levels and Burnout Both attachment anxiety and avoidance are linked to heightened stress in the workplace . Anxiously attached individuals often struggle with the fear of rejection and worry about how their efforts are perceived. This need for constant reassurance can lead to burnout, as individuals feel pressured to meet perceived expectations. heightened stress in the workplace On the other hand, avoidant individuals may cope with workplace stress by overworking or avoiding difficult conversations , such as performance reviews, to maintain their distance. This avoidance leads to overload, as tasks pile up and go unresolved. In both cases, stress levels rise, contributing to an unsustainable work-life balance (or integration). overworking or avoiding difficult conversations 3 Understanding Your Triggers From Relationships at Work If you relate to any of these descriptions, take time to reflect on the situations and interactions at work that might trigger your thoughts of leaving the job and similar reactions. Attachment theory teaches us that our early experiences shape how we approach relationships, including those at work. Our thoughts and emotions act as signals , helping us understand what matters most to us. act as signals Sometimes, those signals can be influenced by past experience and it can be difficult to understand your patterns realistically. In that case, it could be helpful to discuss your patterns with a psychotherapist. By understanding your specific attachment patterns, you can make more informed decisions about your career and relationships at work. Once you’re aware of these patterns, you can use tools like SWOT analysis to evaluate whether staying in your current role aligns with your values and needs—or whether it’s time to move on to a new opportunity. 💡 SWOT analysis Thank you for making it here. If you enjoyed reading this story you might like my weekly posts on Instagram too. Thank you for making it here. If you enjoyed reading this story you might like my weekly posts on Instagram too. weekly posts on Instagram Instagram

Why Are Relationships at Work Important? Meet the Attachment Theory

JavaScript is currently one of the most popular programming languages, according to many platforms. However, does popularity equate to being the most advanced or beloved language? It lacks certain constructs that are considered integral parts of other languages, such as an extensive standard library, immutability, and macros. But there is one detail that, in my opinion, doesn't receive enough attention - generators. In this article, I want to explain possible use cases for iterators and generators and how they improve the verbosity of one's code. I hope that after reading this article, the following piece of code will make all sense: while (true) {
    const data = yield getNextChunk();
    const processed = processData(data);
    try {
        yield sendProcessedData(processed);
        showOkResult();
    } catch (err) {
        showError();
    }
} This is the first part of a series: Iterators and Generators. Iterators So, an iterator is an interface that provides sequential access to data. As you can see, the definition doesn't mention anything about data structures or memory. Indeed, a sequence of null values can be represented as an iterator without occupying any memory space. Let's have a few examples: Array is probably the first thing that comes to mind when you think about iterators. It's a data structure that stores a sequence of values in memory. It's also an iterator because it provides sequential access to its elements. const arr = [1, 2, 3];
for (const item of arr) {
    console.log(item);
} The same goes for strings. They are stored in memory as a sequence of characters and provide sequential access to them. const str = 'abc';
for (const char of str) {
    console.log(char);
} Let's look at the following function example: const fn = () => Math.random(); This function can be considered an iterator because it provides sequential access to random numbers. Okay, why do we need iterators at all if arrays, one of the language's basic data structures, allow us to work with data both sequentially and in arbitrary order? Let's imagine that we need an iterator that implements a sequence of natural numbers, Fibonacci numbers, or any other infinite sequence. It would be difficult to store an infinite sequence in an array. We would need a mechanism for gradually populating the array with data and removing old data to prevent filling up the entire memory of the process. This unnecessary complexity adds extra implementation and maintenance overhead, whereas a solution without an array can be achieved in just a few lines of code: const getNaturalRow = () => {
    let current = 0;
    return () => ++current;
}; Iterators can also be used to represent data retrieved from an external channel, such as a WebSocket. In JavaScript, any object that has a next() method, which returns a structure with value (the current iterator value) and done (a flag indicating the end of the sequence), is considered an iterator. This convention is described in the ECMAScript language standard. Such an object implements the Iterator interface. Let's rewrite the previous example in this format: const getNaturalRow = () => {
    let current = 0;
    return {
        next: () => ({ value: ++current, done: false }),
    };
}; In JavaScript, there is also the Iterable interface. It represents an object that has an @@iterator method (accessible via Symbol.iterator constant) that returns an iterator. Objects that implement this interface can be iterated using the for..of loop. Let's rewrite our example once again, this time as an Iterable implementation: const naturalRowIterator = {
    [Symbol.iterator]: () => ({
        _current: 0,
        next() { return {
            value: ++this._current,
            done: this._current > 3,
       }},
   }),
}

for (num of naturalRowIterator) {
    console.log(num);
}
// output: 1, 2, 3 As you can see, we had to make flag "done" to change at some point, otherwise the loop would be infinite. Generators The next stage in the evolution of iterators was the introduction of generators. They provide syntactic sugar that allows values of an iterator to be returned as if they were the result of a function. A generator is a function declared with an asterisk function* and returns an iterator. The iterator itself is not explicitly returned; instead, the function yields values of the iterator using the yield keyword. When the function completes its execution, the iterator is considered done (subsequent next method calls will return { done: true, value: undefined }. function* naturalRowGenerator() {
    let current = 1;
    while (current <= 3) {
        yield current;
        current++;
    }
}

for (num of naturalRowGenerator()) {
    console.log(num);
}
// output: 1, 2, 3 Even in this simple example, the main nuance of generators is apparent: the code inside a generator function does not execute synchronously. The execution of a generator code occurs incrementally as a result of next method calls on the corresponding iterator. Let's examine how the generator code executes using the previous example. We will use a special cursor to mark where the execution of the generator is paused. At the moment of calling naturalRowGenerator, an iterator is created. function* naturalRowGenerator() {
    ▷let current = 1;
    while (current <= 3) {
        yield current;
        current++;
    }
} Next, when we call the next method three times, or in our case, iterate through the loop three times, the cursor is positioned after the yield statement. function* naturalRowGenerator() {
    let current = 1;
    while (current <= 3) {
        yield current; ▷
        current++;
    }
} For all subsequent next calls, as well as after exiting the loop, the generator completes its execution. The result of subsequent next calls will be { value: undefined, done: true }. Passing parameters to iterators Let's imagine that we need to add the functionality to reset the current counter and start counting from the beginning in our iterator of natural numbers. naturalRowIterator.next() // 1
naturalRowIterator.next() // 2
naturalRowIterator.next(true) // 1
naturalRowIterator.next() // 2 It's clear, how to handle such a parameter in a custom iterator, but what about generators? It turns out that generators support parameter passing! function* naturalRowGenerator() {
    let current = 1;
    while (true) {
        const reset = yield current;
        if (reset) {
          current = 1;
        } else {
          current++;
        }
    }
} The passed parameter becomes available as the result of the yield operator. Let's try to clarify this using the cursor approach. At the moment of creating the iterator, nothing has changed. Now, let's stop after the first next method call: function* naturalRowGenerator() {
    let current = 1;
    while (true) {
        const reset = ▷yield current;
        if (reset) {
          current = 1;
        } else {
          current++;
        }
    }
} The cursor is positioned after returning from the yield operator. With the next next call, the value passed into the function will set the value of the reset variable. But what happens to the value passed in the very first next call? It goes nowhere! If you need to pass an initial value to the generator, you can do so through the generator's arguments. Here's an example: function* naturalRowGenerator(start = 1) {
    let current = start;
    while (true) {
        const reset = yield current;
        if (reset) {
          current = start;
        } else {
          current++;
        }
    }
}

const iterator = naturalRowGenerator(10);
iterator.next() // 10
iterator.next() // 11
iterator.next(true) // 10 Conclusion We have explored the concept of iterators and their implementation in JavaScript. Additionally, we have learned about generators, a syntactic construct for conveniently implementing iterators. Although I provided examples in this article with numeric sequences, iterators in JavaScript can solve a wide range of tasks. They can represent any data sequence and even many finite-state machines. In the next article, I would like to discuss how generators can be used to build asynchronous processes (coroutines, goroutines, CSP, etc.). JavaScript is currently one of the most popular programming languages, according to many platforms. However, does popularity equate to being the most advanced or beloved language? It lacks certain constructs that are considered integral parts of other languages, such as an extensive standard library, immutability, and macros. But there is one detail that, in my opinion, doesn't receive enough attention - generators. In this article, I want to explain possible use cases for iterators and generators and how they improve the verbosity of one's code. I hope that after reading this article, the following piece of code will make all sense: while (true) {
    const data = yield getNextChunk();
    const processed = processData(data);
    try {
        yield sendProcessedData(processed);
        showOkResult();
    } catch (err) {
        showError();
    }
} while (true) {
    const data = yield getNextChunk();
    const processed = processData(data);
    try {
        yield sendProcessedData(processed);
        showOkResult();
    } catch (err) {
        showError();
    }
} This is the first part of a series: Iterators and Generators. Iterators So, an iterator is an interface that provides sequential access to data. As you can see, the definition doesn't mention anything about data structures or memory. Indeed, a sequence of null values can be represented as an iterator without occupying any memory space. Let's have a few examples: Array is probably the first thing that comes to mind when you think about iterators. It's a data structure that stores a sequence of values in memory. It's also an iterator because it provides sequential access to its elements. const arr = [1, 2, 3];
for (const item of arr) {
    console.log(item);
} const arr = [1, 2, 3];
for (const item of arr) {
    console.log(item);
} The same goes for strings. They are stored in memory as a sequence of characters and provide sequential access to them. const str = 'abc';
for (const char of str) {
    console.log(char);
} const str = 'abc';
for (const char of str) {
    console.log(char);
} Let's look at the following function example: const fn = () => Math.random(); const fn = () => Math.random(); This function can be considered an iterator because it provides sequential access to random numbers. Okay, why do we need iterators at all if arrays, one of the language's basic data structures, allow us to work with data both sequentially and in arbitrary order? Let's imagine that we need an iterator that implements a sequence of natural numbers, Fibonacci numbers, or any other infinite sequence. It would be difficult to store an infinite sequence in an array. We would need a mechanism for gradually populating the array with data and removing old data to prevent filling up the entire memory of the process. This unnecessary complexity adds extra implementation and maintenance overhead, whereas a solution without an array can be achieved in just a few lines of code: const getNaturalRow = () => {
    let current = 0;
    return () => ++current;
}; const getNaturalRow = () => {
    let current = 0;
    return () => ++current;
}; Iterators can also be used to represent data retrieved from an external channel, such as a WebSocket. In JavaScript, any object that has a next() method, which returns a structure with value (the current iterator value) and done (a flag indicating the end of the sequence), is considered an iterator. This convention is described in the ECMAScript language standard . Such an object implements the Iterator interface. Let's rewrite the previous example in this format: ECMAScript language standard const getNaturalRow = () => {
    let current = 0;
    return {
        next: () => ({ value: ++current, done: false }),
    };
}; const getNaturalRow = () => {
    let current = 0;
    return {
        next: () => ({ value: ++current, done: false }),
    };
}; In JavaScript, there is also the Iterable interface. It represents an object that has an @@iterator method (accessible via Symbol.iterator constant) that returns an iterator. Objects that implement this interface can be iterated using the for..of loop. Let's rewrite our example once again, this time as an Iterable implementation: Iterable @@iterator Symbol.iterator for..of const naturalRowIterator = {
    [Symbol.iterator]: () => ({
        _current: 0,
        next() { return {
            value: ++this._current,
            done: this._current > 3,
       }},
   }),
}

for (num of naturalRowIterator) {
    console.log(num);
}
// output: 1, 2, 3 const naturalRowIterator = {
    [Symbol.iterator]: () => ({
        _current: 0,
        next() { return {
            value: ++this._current,
            done: this._current > 3,
       }},
   }),
}

for (num of naturalRowIterator) {
    console.log(num);
}
// output: 1, 2, 3 As you can see, we had to make flag "done" to change at some point, otherwise the loop would be infinite. Generators The next stage in the evolution of iterators was the introduction of generators. They provide syntactic sugar that allows values of an iterator to be returned as if they were the result of a function. A generator is a function declared with an asterisk function* and returns an iterator. The iterator itself is not explicitly returned; instead, the function yields values of the iterator using the yield keyword. When the function completes its execution, the iterator is considered done (subsequent next method calls will return { done: true, value: undefined } . function* yield next { done: true, value: undefined } function* naturalRowGenerator() {
    let current = 1;
    while (current <= 3) {
        yield current;
        current++;
    }
}

for (num of naturalRowGenerator()) {
    console.log(num);
}
// output: 1, 2, 3 function* naturalRowGenerator() {
    let current = 1;
    while (current <= 3) {
        yield current;
        current++;
    }
}

for (num of naturalRowGenerator()) {
    console.log(num);
}
// output: 1, 2, 3 Even in this simple example, the main nuance of generators is apparent: the code inside a generator function does not execute synchronously . The execution of a generator code occurs incrementally as a result of next method calls on the corresponding iterator. Let's examine how the generator code executes using the previous example. We will use a special cursor to mark where the execution of the generator is paused. does not execute synchronously next At the moment of calling naturalRowGenerator, an iterator is created. function* naturalRowGenerator() {
    ▷let current = 1;
    while (current <= 3) {
        yield current;
        current++;
    }
} function* naturalRowGenerator() {
    ▷let current = 1;
    while (current <= 3) {
        yield current;
        current++;
    }
} Next, when we call the next method three times, or in our case, iterate through the loop three times, the cursor is positioned after the yield statement. next function* naturalRowGenerator() {
    let current = 1;
    while (current <= 3) {
        yield current; ▷
        current++;
    }
} function* naturalRowGenerator() {
    let current = 1;
    while (current <= 3) {
        yield current; ▷
        current++;
    }
} For all subsequent next calls, as well as after exiting the loop, the generator completes its execution. The result of subsequent next calls will be { value: undefined, done: true } . next next { value: undefined, done: true } Passing parameters to iterators Let's imagine that we need to add the functionality to reset the current counter and start counting from the beginning in our iterator of natural numbers. naturalRowIterator.next() // 1
naturalRowIterator.next() // 2
naturalRowIterator.next(true) // 1
naturalRowIterator.next() // 2 naturalRowIterator.next() // 1
naturalRowIterator.next() // 2
naturalRowIterator.next(true) // 1
naturalRowIterator.next() // 2 It's clear, how to handle such a parameter in a custom iterator, but what about generators? It turns out that generators support parameter passing! function* naturalRowGenerator() {
    let current = 1;
    while (true) {
        const reset = yield current;
        if (reset) {
          current = 1;
        } else {
          current++;
        }
    }
} function* naturalRowGenerator() {
    let current = 1;
    while (true) {
        const reset = yield current;
        if (reset) {
          current = 1;
        } else {
          current++;
        }
    }
} The passed parameter becomes available as the result of the yield operator. Let's try to clarify this using the cursor approach. At the moment of creating the iterator, nothing has changed. Now, let's stop after the first next method call: next function* naturalRowGenerator() {
    let current = 1;
    while (true) {
        const reset = ▷yield current;
        if (reset) {
          current = 1;
        } else {
          current++;
        }
    }
} function* naturalRowGenerator() {
    let current = 1;
    while (true) {
        const reset = ▷yield current;
        if (reset) {
          current = 1;
        } else {
          current++;
        }
    }
} The cursor is positioned after returning from the yield operator. With the next next call, the value passed into the function will set the value of the reset variable. But what happens to the value passed in the very first next call? It goes nowhere! If you need to pass an initial value to the generator, you can do so through the generator's arguments. Here's an example: next reset next function* naturalRowGenerator(start = 1) {
    let current = start;
    while (true) {
        const reset = yield current;
        if (reset) {
          current = start;
        } else {
          current++;
        }
    }
}

const iterator = naturalRowGenerator(10);
iterator.next() // 10
iterator.next() // 11
iterator.next(true) // 10 function* naturalRowGenerator(start = 1) {
    let current = start;
    while (true) {
        const reset = yield current;
        if (reset) {
          current = start;
        } else {
          current++;
        }
    }
}

const iterator = naturalRowGenerator(10);
iterator.next() // 10
iterator.next() // 11
iterator.next(true) // 10 Conclusion We have explored the concept of iterators and their implementation in JavaScript. Additionally, we have learned about generators, a syntactic construct for conveniently implementing iterators. Although I provided examples in this article with numeric sequences, iterators in JavaScript can solve a wide range of tasks. They can represent any data sequence and even many finite-state machines. In the next article, I would like to discuss how generators can be used to build asynchronous processes (coroutines, goroutines, CSP, etc.).

Stories, News & Mentions about ATT

Att’s Stories on HackerNoon

Att's News & Mentions