if you are in software, now is the best time to learn about/pivot to hardware?? here it goes
built 8 bit computer a while ago; Want to see how our code actually works on hardware? Check it out
Working on dropdat cross-AI memory in one click.
• capture any AI chat (ChatGPT, Claude, Gemini..) as a portable capsule
• drop it back into any other AI, instantly
• MCP server → works in Claude Code, Cursor, Cline
Working on dropdat cross-AI memory in one click. • capture any AI chat (ChatGPT, Claude, Gemini..) as a portable capsule • drop it back into any other AI, instantly • MCP server → works in Claude Code, Cursor, Cline
Working on dropdat cross-AI memory in one click.
• capture any AI chat (ChatGPT, Claude, Gemini..) as a portable capsule
• drop it back into any other AI, instantly
• MCP server → works in Claude Code, Cursor, Cline
The contents of your house fit in a moving truck, why don’t you keep it in there?
Simple, you need the stuff out for easy access, same for the 10GB file, reading the contents in zipped state would make your computer run overtime.
In 2014 I was working at a company that made mobile games.
Every week we'd have a meeting where we talked about various metrics that we cared about.
One of the metrics we cared about was called "Average Revenue Per Paying User" (ARPPU).
One meeting the lead of one of the games said:
"ARPPU has increased drastically since we deployed a build last week. It was around $4 USD, but now it has increased to $15."
Everyone was very excited by this. Someone asked what they did to get ARPPU to increase so drastically.
"We don't know, all we did was fix some minor bugs and do some refactoring. Nothing should have changed."
How very myserious.
A few days later we figured out what happened.
The game allowed users to purchase currency bundles. Most people bought the low cost bundles. Which meant the ARPPU for the game was around $4 USD.
The code that handled payments had this structure:
In the latest build someone (not me) introduced a bug that caused the code to crash while processing the payment.
The code crashed after a user got the currency they purchased, but before the button was enabled again.
This meant the second time a user wanted to buy a bundle they had to buy a different bundle, likely a more expensive one.
After learning this we were sad that someone's buggy code lead to us making more money.
We fixed the bug and ARPPU went back down.
TIL: If your EC2 can ping but not curl, and all AWS configs look correct, just create a new instance; wasted 5 hours debugging wth suddenly happened to it. Some host-level networking issues aren't worth debugging ig . Fresh instance fixed it in 10 mins.