Captone

Software Engineer

[Captone @liopun_]

Using ChatGPT to master problem-solving skills
https://t.co/LeT3awxMcE

#ChatGPT #AutoGPT #GPT4All #GPT5 #OpenSource #ONEPIECE1081 #CERB #Slack

[Elon Musk @elonmusk]

“Full access” 😂

[Matt Dancho (Business Science) @mdancho84]

This GitHub is better than most $1,000 AI courses.

Chip Huyen's AI Engineering companion repo:

[Google Cloud Tech @GoogleCloudTech]

Introducing the Open Knowledge Format (OKF), an open specification that formalizes the LLM-wiki pattern into a portable, interoperable format.

AI is only as smart as the context we give it. As we build more advanced, agentic AI systems, they need accurate metadata and context to be useful. But in most organizations, that context is locked inside fragmented data catalogs, isolated wikis, scattered code comments, or the minds of senior engineers. Every time a new AI agent is built, teams are forced to solve the exact same context-assembly problem from scratch.

To solve this, we've announced OKF, a vendor-neutral, open specification that formalizes the "LLM-wiki pattern" into a portable, interoperable format. It provides a standardized way to represent the enterprise knowledge that modern AI systems rely on.

— Just markdown: readable in any editor, renderable on GitHub, indexable by any search tool
— Just files: shippable as a tarball, hostable in any git repo, mountable on any filesystem
— Just YAML frontmatter: for the small set of structured fields that need to be queryable: type, title, description, resource, tags, and timestamp

We’ve also shipped reference implementations to help you hit the ground running, including an enrichment agent for BigQuery, a static HTML visualizer, and live sample bundles on @github → https://t.co/ilhAMCrcTc

➕ Knowledge Catalog can now natively ingest OKF!

Stop reinventing data models and building bespoke integrations for every new AI tool. Here's more about how OKF works → https://t.co/FR4kJRsgEH

[✞Yคภкєє✞ ♑️ @yankeedraft]

Hey @grok What would happen if the arteries and veins in our bodies were arranged this way?

[Peter Steinberger 🦞 @steipete]

@_ARahim_ @bcherny only boomers fix typos in prompts. llms perfectly understand you even if you mistype.

[Peter Steinberger 🦞 @steipete]

Here's a simple loop: Tell codex to maintain your repos, wake up every 5 minutes and direct work to threads. That makes it easy to parallelize+steer work as needed.

I use a orchestrator skill combined with my triage+autoreview+computer use skills, so some work can land autonomously. https://t.co/FbBoJTIcfd
https://t.co/8389roVnOm

[Shann³ @shannholmberg]

what is agent looping

for the last two years we prompted agents one task at a time. that is starting to change

instead of asking an agent to build the landing page and then driving every step yourself, you set up a loop that handles discovery, planning, the work, checking, and iterating until the goal is met

looping is a setup you build. almost any agent harness can run it, it just depends on how you wire it up

at its simplest, looping is one agent working on itself:

> researches
> drafts
> checks the draft against a goal
> fixes what is weak
> runs that cycle again until the work clears the requirements

you are not prompting each step anymore. the agent repeats the cycle for you

the bigger version is a fleet looping. you give an orchestrator agent a goal, it breaks the goal into pieces, hands each piece to a specialist agent, and those specialists hand smaller jobs to their own subagents

the whole tree keeps looping through discovery, planning, execution, and verification until the goal is met

one agent looping is like a person redoing their own draft. a fleet looping is a whole team running a project end-to-end

you create a goal, and the system runs the loop until it finishes within the reqs you set

open and closed looping:

OPEN LOOPING is exploratory. it still has conditions and a goal, but you give the agent or the fleet a wide space to move in. it can try different paths, discover things, build something you did not fully spec out

this is the exciting end, it is what Peter and others are doing, and tbh it is where I want to spend more time

the catch is cost, an open loop with real room to explore burns an insane amount of tokens. for the 90 percent of people without an unlimited budget it is not runnable yet, and pointed at projects with a loose standard it turns into a slop machine

CLOSED LOOPING is bounded. a human designs the end-to-end path first:

> clear goal
> defined steps
> an eval at each step
> a point where it stops or hands back to you (and feeds back performance data)

the agents still loop, but inside framework you built. it gets better every run because each pass feeds the next, and it runs on a normal budget because the path is tight.

for most marketing work, closed is the one that pays off today.

> the orchestrator owns the goal
> the specialists own the steps
> the subagents do the narrow work
> an eval gate make sure its not slop

[Mark Carney @MarkJCarney]

We just launched Canada’s new AI Strategy: AI For All. 

We’re taking control of our future — with AI that’s governed by Canadian values, AI that’s accountable to Canadians, and AI that serves all Canadians.

[Andrew Curran @AndrewCurran_]

Canada launched its national AI strategy this morning, and if you live in Canada the federal government may fund, provide compute to, and possibly even take a stake in your idea. They also plan to provide access to AI agents for every post-secondary student, which sounds like a nice contract for somebody.

I've had an idea for something agents will subscribe to, so I might do this. but I'm going to see how far I can go with Chatty and Claude myself first.

[Polymarket @Polymarket]

NEW: AI consultant reveals a client accidentally spent $500,000,000.00 in a single month after failing to set employee limits on Claude usage.

[Kevin Naughton Jr. @KevinNaughtonJr]

here's my prediction for the top 10 companies hiring software engineers in ~2030:

[GitHub Projects Community @GithubProjects]

|￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣|
| Don't Push To Production On Friday|
|＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿|
😎
|\👐
/ \
━━━━━┓ ＼＼
┓┓┓┓┓┃
┓┓┓┓┓┃ ヽ😩ノ
┓┓┓┓┓┃ 　 /　
┓┓┓┓┓┃ ノ)　
┓┓┓┓┓┃
^^^^^^^^Production^^^^^^^

[Gergely Orosz @GergelyOrosz]

Meta laying off 10% of staff when revenue is at an all-time high, revenue growth is a beast (33% YoY!!), profits at an all-time high:

just depressing

These layoffs are not because Meta needs to lay off, but because Zuck wanted to lay off for whatever reason

[Grummz @Grummz]

Github HACKED.

The internal repository has been breached.

Hacker group claims to have this data, including 4,000 private repositories, and is offering to sell it for minimum 50k or the highest bidder.

[Astra 💫 @GideonToba]

Canada is seeking top talents all the time, what’s wrong with the ones already in the country?
Provide an ambience that allows professionals in Canada to easily transition and you won’t need to keep asking outsiders to come 👍🏾

[Guillermo Rauch @rauchg]

Here's my update to the broader community about the ongoing incident investigation. I want to give you the rundown of the situation directly.

A Vercel employee got compromised via the breach of an AI platform customer called https://t.co/7PY6gGtzgI that he was using. The details are being fully investigated.

Through a series of maneuvers that escalated from our colleague’s compromised Vercel Google Workspace account, the attacker got further access to Vercel environments.

Vercel stores all customer environment variables fully encrypted at rest. We have numerous defense-in-depth mechanisms to protect core systems and customer data. We do have a capability however to designate environment variables as “non-sensitive”. Unfortunately, the attacker got further access through their enumeration.

We believe the attacking group to be highly sophisticated and, I strongly suspect, significantly accelerated by AI. They moved with surprising velocity and in-depth understanding of Vercel.

At the moment, we believe the number of customers with security impact to be quite limited. We’ve reached out with utmost priority to the ones we have concerns about. All of our focus right now is on investigation, communication to customers, enhancement of security measures, and sanitization of our environments. We’ve deployed extensive protection measures and monitoring. We’ve analyzed our supply chain, ensuring Next.js, Turbopack, and our many open source projects remain safe for our community.

The recommendation for all Vercel customers is to follow the Security Bulletin closely (https://t.co/BLVnic9fJC). My advice to everyone is to follow the best practices of security response: secret rotation, monitoring access to your Vercel environments and linked services, and ensuring the proper use of the sensitive env variables feature.

In response to this, and to aid in the improvement of all of our customers’ security postures, we’ve already rolled out new capabilities in the dashboard, including an overview page of environment variables, and a better user interface for sensitive env var creation and management. As always, I’m totally open to your feedback.

We’re working with elite cybersecurity firms, industry peers, and law enforcement. We’ve reached out to Context to assist in understanding the full scale of the incident, in an effort to protect other organizations and the broader internet. I also want to thank the Google Mandiant team for their active engagement and assistance.

It’s my mission to turn this attack into the most formidable security response imaginable. It’s always been a top priority for me. Vercel employs some of the most dedicated security researchers and security-minded engineers in the world. I commit to keeping you updated and rolling out extensive improvements and defenses so you, our customers and community, can have the peace of mind that Vercel always has your back.

[⌭ ROSS @rossark0]

Consumer apps don’t go viral because of features.

They go viral because they make people feel cool for sharing them.

Design for status.

[Veloria 🌊 @veloriahq]

She's not confused about you, bro.

She's confused about why you're still trying when she's giving you zero effort.

Take the hint.

[Noctara @rumilyrics]

The smartest are quiet. The happiest are private.

[Sam Lambert @samlambert]

there is no better life for me than solving difficult problems with people that are smart, direct, kind, and funny.