Delali

5.9K posts

Delali banner
Delali

Delali

@delali

Founder @delalify • Building @conjoincloud

Earth Sumali Ağustos 2012
13 Sinusundan207 Mga Tagasunod
Delali
Delali@delali·
@ChaitanyaOnTech There is no change when Apple does it. Apple typically waits for the right time, after all the pioneers have publicly run their experiments.
English
0
0
0
105
Delali
Delali@delali·
@mattpocockuk I would disagree with this. Depending on the complexity of the project or situation you're grilling, /grill-(me/with-docs) can take time. But it's super helpful because you're always in the loop. You can spot mistakes before it makes it.
English
0
0
1
48
Matt Pocock
Matt Pocock@mattpocockuk·
Considering an /auto-grill skill which you'd run during a grilling session 1. Run when you feel like you and the agent are on the same page 2. It continues the grilling but always accepts its own recommendation 3. If you disagree, you manually interrupt it Worth a try?
English
117
11
560
35K
Delali nag-retweet
News from Google
News from Google@NewsFromGoogle·
The Google Threat Intelligence Group has detected the first known instance of a threat actor using an AI-developed zero-day exploit in the wild. While the attackers planned a wide-scale strike, our proactive counter-discovery may have prevented that from happening. This finding is part of our new report on AI-powered threats.
English
308
1.7K
13.9K
5.1M
Delali nag-retweet
Seb ⚛️ ThisWeekInReact.com
Seb ⚛️ ThisWeekInReact.com@sebastienlorber·
TL;DR for open-source maintainers 🚫 NEVER use "pull_request_target" workflows 🚫 NEVER use shared caches in your publish pipeline Combining these 2 in particular is extremely dangerous I've repeated this countless times over the years, but another reminder is always useful
Seb ⚛️ ThisWeekInReact.com tweet media
TANSTACK@tan_stack

SECURITY ADVISORY — TanStack npm packages A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package. Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down. Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys. If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised: • Rotate cloud, GitHub, and SSH credentials immediately • Audit cloud audit logs for the last several hours • Pin to a prior known-good version and reinstall from a clean lockfile Detection — the malicious manifest contains: "optionalDependencies": { "@tanstack/setup": "github:tanstack/router#79ac49ee..." } Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root). Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level. Full technical breakdown, complete package and version list, and rolling status updates: github.com/TanStack/route… Credit to the security researcher for responsible disclosure.

English
26
221
1.7K
220.6K
Delali
Delali@delali·
@Rasmic Everyone is overestimating AI. 😒
English
0
0
1
26
Micky
Micky@Rasmic·
The Classic CEO playbook >profitable and growing >layoffs employees >blames AI not the fact that they overhired >regular folk hate AI because AI is blamed
English
7
2
54
2.6K
Massimo
Massimo@Rainmaker1973·
No gas, no noise, just pure efficiency. This man and his scythe are unstoppable.
English
1.7K
1.6K
25.5K
5.8M
Delali
Delali@delali·
@TEDTalks @anilkseth AI is not and will never be conscious. We must never forget about that. It's a tool that when used carefully, can drive a lot of innovation, but not at the expense of our own intelligence.
English
0
0
0
27
TED Talks
TED Talks@TEDTalks·
"Many experts think that conscious AI is possible. I think they're wrong." Watch neuroscientist @anilkseth's full TED Talk here: t.ted.com/0NR6eGI
English
104
225
930
137.5K
Delali
Delali@delali·
We have overestimated AI's capability.
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
0
0
1
21
Delali
Delali@delali·
@brian_armstrong I work with AI a lot. But “Non-technical teams are now shipping production code” is really scary imo. They are not even experimenting, but shipping PRODUCTION code? Are we there yet?
English
0
0
0
330
Brian Armstrong
Brian Armstrong@brian_armstrong·
This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian
English
5.3K
2.4K
20.1K
23.5M
Delali
Delali@delali·
@mcuban You're correct. AI behaves like that because of its stochastic nature. To “guess” the next token, it needs to add a little randomness to its calculation every time. This is what makes it appear smart, but also why it assumes it's output making it unreliable for high-stakes work.
English
0
0
0
23
Mark Cuban
Mark Cuban@mcuban·
I’m coming to the conclusion that the biggest challenge for Enterprise AI, and AI in general , as of now, is that it’s still impossible to make sure that everyone gets the same answer to the same question, every time. Which is a great response to the doomers. AI doesn’t know the consequences of its output. Judgement and the ability to challenge AI output is becoming increasingly necessary, and valuable. Which makes domain knowledge more valuable by the second. Am I wrong ?
English
1.9K
446
6.2K
1.5M
Aaron
Aaron@aaronp613·
Apple accidentally left Claude.md files in today's Apple Support app update (v5.13)
Aaron tweet mediaAaron tweet media
English
283
1K
13.6K
2.6M
Cursor
Cursor@cursor_ai·
We’re introducing the Cursor SDK so you can build agents with the same runtime, harness, and models that power Cursor. Run agents from CI/CD pipelines, create automations for end-to-end workflows, or embed agents directly inside your products.
English
413
826
8.8K
3M
Delali
Delali@delali·
@steren Thanks. Signed up a few days ago.
English
0
0
0
7
Steren
Steren@steren·
A 2-minute highlight of my #GoogleCloudNext video: "What's new in Cloud Run?"
English
3
7
48
2.8K
Delali
Delali@delali·
@shadcn Honestly, cursor pointer on buttons, especially, should be the default. If anyone does not want it, they should be able to override it easily.
English
0
0
3
436
Delali
Delali@delali·
@steren What’s the recommended pattern to pass files/data into a sandbox and retrieve richer outputs (files, artefacts, structured data, etc.) beyond just the stdout from the sandbox? Also, does it support dynamic dependency installs (pip/apt) inside the ephemeral env?
English
1
0
0
48
Delali
Delali@delali·
@steren This is awesome. I've been waiting for this for a while now. Time to benchmark.
English
0
0
0
114
Steren
Steren@steren·
Announcing Cloud Run sandboxes: Secure on-the-fly code execution: Spin up ephemeral, isolated sandboxes from within Cloud Run resources. Safely execute agent-generated code, scripts, or Chromium.
Steren tweet media
English
17
42
321
140K
Steren
Steren@steren·
In 2025, the number of Cloud Run external monthly active developers and applications doubled. If you are running AI Agents, vibe coded apps, AI inference, or scalable apps, there's something new for you at Next ‘26:
English
6
13
120
19.1K
Delali
Delali@delali·
The 60-second delay isn’t expected S3 lag. For me, it directly breaks WAL visibility and durability across instances. Writes batch before hitting the authoritative S3 bucket, so readers on other mounts (or direct S3 backups) see stale data for up to a minute. WAL is also incompatible with NFS-style shared memory (see #implementation_of_shared_memory_for_the_wal_index" target="_blank" rel="nofollow noopener">sqlite.org/wal.html#imple…). I have practically confirmed these edge cases in my tests.
English
0
0
0
20
Delali
Delali@delali·
True. But functl() on NFS has documented quirks. It's still a risk one should know about. The 60s delay is actually a big issue for me. I work on distributed SQLite, and I encounter weird behaviour with the SQLite WAL on S3 Files (explanation in the comment below). This does not affect just S3 Files, but anyone trying to use it to run SQLite should be aware of the major issues.
English
1
0
0
71
伊津野 英克
伊津野 英克@hidekatsu_izuno·
@delali Thank you for your information. It seems that running SQLite is not very practical after all.
English
1
0
1
19
伊津野 英克
伊津野 英克@hidekatsu_izuno·
s3 filesへのランダムアクセス更新どうなんのかな。 close時に同期かな? だったらsqliteの読み書きくらいできそうだけれど。
日本語
1
0
1
148