The takeaway isn't "make long paywalls"
It's that "best practices" are just someone else's local maximum
What signals trust in San Francisco can signal a scam in Berlin
Translation ≠ localization
Both of these things are true:
1. Remote work is hard and can be a bad fit for many
2. Office culture can be great and more productive
Rather than ignoring nuance, just don't hire the person who needs office culture remotely, or vice versa.
The @nyknicks championship inspired me to build an AI basketball coach to improve my 1v1 game
Built with:
- Robloflow RF-DETR to detect players/ball/rim
- MediaPipe to capture body angles
- OpenCV to analyze and annotate the clip
For years, the hardest part of my job in Portugal was convincing brilliant people to stay.
I led engineering teams here, fighting the same gravity every time. We train world-class people - our universities turn them out every year, and the best of them leave, for the UK, Germany, the US, because that is where the companies are.
We toured universities and waved the flag to keep them, and it was never enough. The country pays to raise the talent, and the talent takes the next flight out. Some come back but many never do.
What's different today is that a company headquartered in Silicon Valley can now legally hire and pay a full team in Lisbon using @Remote. Properly employed, on local contracts, and on the right side of the tax and labor rules.
So the next person with big ambitions and a Portuguese passport does not need to leave to chase them.
This is brain drain in reverse. For the first time, opportunity can find talent wherever it was born, in every country that ever lost some of its best to somewhere else.
Got em. I poison my AGENTS.md (and other things like code comments) all over the place with prompt injections like this to find people who don't review their code and sling it off to another human. Catches folks all the time and then its an instant ban.
As I've said, I don't care if you don't review your own code. But if you're submitting code to an OSS project and crossing a human boundary, it is simple courtesy to do some human review.
Cursor could really claim TAM here given GitHub’s pace (or lack thereof) in the wake of agents.
A very interesting space to watch, as Mitchell predicted.
A few weeks ago I noticed that Linear got slower than it used to. Especially on the new Diffs feature, that we were getting ready to release, it was pretty bad. For days I was running profiles, staring at profiles, bisecting with agents from every direction.
The pattern was clear - we accessed the DOM a ton, which blocked the main threads on style recalcs and layout for 10s or 100s of milliseconds over and over.
I shipped dozens of PRs to get rid of those layout-causing calls, using pretext and whatever tricks the agents and I could come up with. It helped, but only a bit. I was getting desperate.
Hang on.. are you telling me there is a chance we never drew 0-0? That the feed was manipulated by an attacker.. and the fake feed was generated by AI?
Damn AI. Go Spain! 🇪🇸😄