The Sunk Cost Fallacy in Software Development
The Sunk Cost Fallacy is when we continue investing in something primarily because we've already invested so much, rather than because it's the best decision going forward.
What it looks like in programming:
"We've already spent 6 months building this custom authentication system. Yes, it has security issues and is hard to maintain, but we can't refactor it entirely now - think of all the work we've already put in!"
The rational decision should ignore past costs (they're "sunk" and can't be recovered) and focus only on:
- Future costs
- Expected benefits
- Alternative options
Real-world example:
Your team spent 3 months developing a custom state management solution for your React app. It's complex, buggy, and new developers struggle to understand it. Redux would solve your problems, but your tech lead says: "We've invested too much time in our solution to abandon it now."
This is the fallacy at work. The time already spent is gone regardless of what you choose next. The right question is: "Which option gives us the best outcome from this point forward?"
How to avoid it?
1. Regularly reassess projects with fresh eyes
2. Be willing to pivot when better options come to mind
3. Focus on future value, not past investment
4. Document decisions to recognize when conditions change
Good engineers know when to build, but great engineers know when to abandon something.
The Sunk Cost Fallacy is when we continue investing in something primarily because we've already invested so much, rather than because it's the best decision going forward.
What it looks like in programming:
"We've already spent 6 months building this custom authentication system. Yes, it has security issues and is hard to maintain, but we can't refactor it entirely now - think of all the work we've already put in!"
The rational decision should ignore past costs (they're "sunk" and can't be recovered) and focus only on:
- Future costs
- Expected benefits
- Alternative options
Real-world example:
Your team spent 3 months developing a custom state management solution for your React app. It's complex, buggy, and new developers struggle to understand it. Redux would solve your problems, but your tech lead says: "We've invested too much time in our solution to abandon it now."
This is the fallacy at work. The time already spent is gone regardless of what you choose next. The right question is: "Which option gives us the best outcome from this point forward?"
How to avoid it?
1. Regularly reassess projects with fresh eyes
2. Be willing to pivot when better options come to mind
3. Focus on future value, not past investment
4. Document decisions to recognize when conditions change
Good engineers know when to build, but great engineers know when to abandon something.
if() function in CSS:The CSS if() function provides a concise way to express conditional values. It accepts a series of condition-value pairs, delimited by semicolons. The function evaluates each condition sequentially and returns the value associated with the first true condition. If none of the conditions evaluate to true, the function returns an empty token stream.
https://developer.chrome.com/blog/new-in-chrome-137#if
This media is not supported in your browser
VIEW IN TELEGRAM
I left a server online with VNC wide open to see how it would be interacted with. This is one of the more interesting interactions:
sauce
TLDR: facebook (and yandex) android apps would listen on a localhost web address and then websites with their javascript code would tell the browser to connect to it, correlating long-lived sessions in the apps with even incognito sessions in web browsers
they no longer do this since June 3rd, but the method is worth noting
https://localmess.github.io/
they no longer do this since June 3rd, but the method is worth noting
https://localmess.github.io/
Forwarded from Anton Rosenberg
Переписка хранится в нереляционной СУБД собственной разработки text-engine, файлы данных которой на дисках шифруются, сами диски тоже шифруются. Но у самого Telegram, конечно, есть и те, и другие ключи (и Павел это подтверждал в скобках в своей статье от августа 2017 года "Почему Telegram не использует шифрование end-to-end по умолчанию"). Посторонний человек, вынувший диск из сервера, расшифровать данные не сможет, но на уровне работающей базы данных сообщения действительно не зашифрованы. Так как я занимался вопросами анти-спама, у меня к ним доступ был.
Do It by Code
Переписка хранится в нереляционной СУБД собственной разработки text-engine, файлы данных которой на дисках шифруются, сами диски тоже шифруются. Но у самого Telegram, конечно, есть и те, и другие ключи (и Павел это подтверждал в скобках в своей статье от августа…
Translation:
#telegram #db
The data is stored in a non-relational DBMS of our own design, text-engine, whose data files on disks are encrypted, and the disks themselves are also encrypted.
But Telegram itself, of course, has both keys (and Pavel confirmed this in brackets in his article from August 2017 "Why Telegram Doesn't Use End-to-End Encryption by Default").
An outsider who removes the disk from the server will not be able to decrypt the data, but at the level of the running database, the messages are indeed not encrypted. Since I was working on anti-spam issues, I had access to them.
#telegram #db
What is EDR?
dark-kill
https://github.com/SaadAhla/dark-kill
Endpoint Detection and Response (EDR), also referred to as endpoint detection and threat response (EDTR), is an endpoint security solution that continuously monitors end-user devices to detect and respond to cyber threats like ransomware and malware.
EDR is defined as a solution that "records and stores endpoint-system-level behaviors, uses various data analytics techniques to detect suspicious system behavior, provides contextual information, blocks malicious activity, and provides remediation suggestions to restore affected systems."
dark-kill
A user-mode code and its rootkit that will Kill EDR Processes permanently by leveraging the power of Process Creation Blocking Kernel Callback Routine registering and ZwTerminateProcess.
https://github.com/SaadAhla/dark-kill
Do It by Code
partially
for example this link doesn't work:
https://blog.cloudflare.com/post-mortem-on-cloudflare-control-plane-and-analytics-outage/
but cf pages and cf reverse-proxies are working fine
https://blog.cloudflare.com/post-mortem-on-cloudflare-control-plane-and-analytics-outage/
but cf pages and cf reverse-proxies are working fine
pyrogram.errors.exceptions.forbidden_403.Forbidden: Telegram says: [403 Forbidden] - [403 RECAPTCHA_CHECK_signup__6LfsY8EqAAAAAJ4jvMOeSyq6zRPYxnVR4HQDPIhm] (caused by "auth.SendCode")
Root Cause of the June 12, 2025 Google Cloud Outage
Summary:
- On May 29, 2025, a new Service Control feature was added for quota policy checks.
- This feature did not have appropriate error handling, nor was it feature flag protected.
- On June 12, 2025, a policy with unintended blank fields was inserted and replicated globally within seconds.
- The blank fields caused a null pointer which caused the binaries to go into a crash loop.
"If this had been flag protected, the issue would have been caught in staging."
^ Kinda reminds me of the CrowdStrike incident.
Do It by Code
Starlink User Terminal Teardown Article, Comments
During device initialization, if the system identifies itself as a user terminal, the initialization script automatically writes 41 SSH public keys into /root/.ssh/authorized_keys. Notably, port 22 on the UTA remains open to the local network at all times. Having such a large number of unknown login keys on a user product certainly raises eyebrows.
🤖 MIT just completed the first brain scan study of ChatGPT users & the results are terrifying.
Turns out, AI isn't making us more productive. It's making us cognitively bankrupt.
🧵 https://fxtwitter.com/itsalexvacca/status/1935343874421178762
📝 "ChatGPT users had the lowest brain engagement and 'consistently underperformed at neural, linguistic, and behavioral levels.' Over the course of several months, ChatGPT users got lazier with each subsequent essay, often resorting to copy-and-paste by the end of the study."
Turns out, AI isn't making us more productive. It's making us cognitively bankrupt.
🧵 https://fxtwitter.com/itsalexvacca/status/1935343874421178762
📝 "ChatGPT users had the lowest brain engagement and 'consistently underperformed at neural, linguistic, and behavioral levels.' Over the course of several months, ChatGPT users got lazier with each subsequent essay, often resorting to copy-and-paste by the end of the study."
🧵 Thread • FxTwitter
Alex Vacca (@itsalexvacca)
BREAKING: MIT just completed the first brain scan study of ChatGPT users & the results are terrifying.
Turns out, AI isn't making us more productive. It's making us cognitively bankrupt.
Here's what 4 months of data revealed:
(hint: we've been measuring…
Turns out, AI isn't making us more productive. It's making us cognitively bankrupt.
Here's what 4 months of data revealed:
(hint: we've been measuring…
Please open Telegram to view this post
VIEW IN TELEGRAM
X (formerly Twitter)
Officer's Notes (@officer_secret) on X
It looks like !!! @coinmarketcap is hacked…
When you browse, it asks to connect wallet and then asks for ERC20 approvals. Do not approve and use @RevokeCash if you accidentally did!
When you browse, it asks to connect wallet and then asks for ERC20 approvals. Do not approve and use @RevokeCash if you accidentally did!