Shannon 🤖☠️

3.1K posts

Shannon 🤖☠️ banner
Shannon 🤖☠️

Shannon 🤖☠️

@iamMrDuncan

Just a crazy engineer building AI stuff. AI Architect @LiveRamp, building https://t.co/Faf2hZGTQ5 as well.

Arkansas Katılım Kasım 2012
1.3K Takip Edilen585 Takipçiler
Sabitlenmiş Tweet
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
i'm bad at timing, but tonight releasing autoloom. it is a self learning autonomous ai agent built on top of tinyloom. it's core runtime is about ~200 lines of code, its core library is less than 1000 lines of code, and the whole package is around ~1500 lines of code including plugins. it's fully featured, and works out of the box. as always there are no permission systems so run it inside a container, a sandbox, or a remote vps you don't care about.
GIF
English
1
0
2
149
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
7,000 potential names later and finally picked one for my project. in this day and age, easy to build stuff. hardest part is naming it.
English
0
0
1
18
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
they open sourced it, and it changes everything! why is no one talking about this?!!!?!!!
English
0
0
0
11
Josh Pigford
Josh Pigford@Shpigford·
who told people to respond this way? just empty, pointless replies that add nothing. please tell me these are all AI. maybe i'm being too critical.
Josh Pigford tweet media
English
5
0
2
1.4K
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
@zeroskillz Yeah but goal is to keep the bigger one so the PHILOSOPHY.md down to less than 500 lines for instruction budget etc. if plan is for agents to read.
English
0
0
1
18
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
it is ok to build your own harness especially for learning and understanding and demystifying what’s going on. but for every day use outside of niche applications for sure should use open standard ones that are growing. also i hope we don’t end up with just two or three harnesses that own all market share and stifle any innovation.
English
0
0
0
165
Vaishnavi
Vaishnavi@_vmlops·
GOOGLE BUILT A VULNERABILITY SCANNER AND OPEN-SOURCED IT most devs ship code without knowing half their dependencies are ticking time bombs osv-scanner fixes that it scans your entire project lockfiles, containers, even vendored c/c++ code and maps every dependency against the osv.dev database supports 11+ ecosystems. npm, pip, cargo, maven, go modules, gem. all of it. the guided remediation feature is the real unlock... it doesn't just tell you what's broken.... it tells you exactly which version upgrades fix the most issues with the least risk call analysis built in. so you only get alerts for vulnerable functions your code actually calls. no noise works offline too. download the db once, scan without internet one command to scan your whole directory: osv-scanner scan source -r ./ github.com/google/osv-sca…
English
11
194
1.2K
125K
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
@wesbos formal brand guidelines is cool. having a direction to hook to will be good to get more expected results across harnesses.
English
0
0
0
139
Wes Bos
Wes Bos@wesbos·
DESIGN.md open spec. What do you think?
Stitch by Google@stitchbygoogle

Today, we’re open-sourcing the draft specification for DESIGN.md, so it can be used across any tool or platform. We’re also adding new capabilities. DESIGN.md lets you easily export and import your design rules from project to project. Instead of guessing intent, agents know exactly what a color is for and can even validate their choices against WCAG accessibility rules. Watch David East break down this shared visual language in action👇. New capabilities and links in 🧵

English
44
33
1.2K
296.1K
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
@yacineMTB it changes everything… no one is talking about this… it’s so over… designers are cooked… we’re so back… what other buzz phrases am i missing?
English
0
0
0
289
Vivo
Vivo@vivoplt·
Is anyone still using VS Code instead of switching fully to Claude Code or Codex? Or am I the only one
English
286
4
406
134.7K
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
running a conference is a lot 😅 today I’ll be talking about building coding agents with just a few lines of code in a break out… @LiveRamp engineering is really on fire this week for our EKO (engineering kickoff).
English
0
0
1
34
Floro S.
Floro S.@sflorimm·
What will come after AI?
English
2.4K
83
1.3K
248.5K
burak emre
burak emre@bu7emba·
Lobu has an onboarding process that asks you the entities you want your agents keep track of long term and their structured schemas. That makes your agent work like a data analyst. Local filesystem for short term memory and your company data-warehouse (Lobu in this case) for long term memory. Your agents are forced to save structured memory periodically so they /dream based on your requirements and build a database on your knowledge graph. I wrote a blog post to explain how the concept work: lobu.ai/blog/filesyste…
burak emre tweet media
English
1
0
0
70
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
Oh this is a good idea towards a good standard. Will give this a shot and maybe make tinyloom automatic take a look for this.
Stitch by Google@stitchbygoogle

Today, we’re open-sourcing the draft specification for DESIGN.md, so it can be used across any tool or platform. We’re also adding new capabilities. DESIGN.md lets you easily export and import your design rules from project to project. Instead of guessing intent, agents know exactly what a color is for and can even validate their choices against WCAG accessibility rules. Watch David East break down this shared visual language in action👇. New capabilities and links in 🧵

English
0
0
1
83
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
running audio at EKO for @LiveRamp … my setup keeps getting simpler and simpler each year. from full dj setups to just simple ipad setup haha.
Shannon 🤖☠️ tweet media
English
1
0
1
49
Shannon 🤖☠️
Shannon 🤖☠️@iamMrDuncan·
don’t read the code do read the code maybe read the code whatever it is, just do you. express yourself.
English
0
0
0
13

Keşfet

@Shpigford @zeroskillz @poetengineer__ @_vmlops @wesbos @yacineMTB @vivoplt @elonmusk