Robert Hoffmann

41.3K posts

Robert Hoffmann banner
Robert Hoffmann

Robert Hoffmann

@itechnologynet

Tech Lover (Psychology, Marketing, Biotech). Product Owner / R&D Software Engineer (PSPO/PSM certified)̬̤̣̮̩̱̭ Dev, UX, AI

France 🇫🇷 🇺🇸 🇩🇪 เข้าร่วม Ocak 2009
375 กำลังติดตาม5.7K ผู้ติดตาม
ทวีตที่ปักหมุด
Robert Hoffmann
Robert Hoffmann@itechnologynet·
Found my old CV to be kinda mehh So made it into an app 😎 i-technology.net
English
1
1
8
9.2K
Cointelegraph
Cointelegraph@Cointelegraph·
🚨 NOW: OpenAI plans to merge ChatGPT, Codex, and its browser into a single desktop "superapp" aimed at simplifying the user experience, WSJ reports.
Cointelegraph tweet mediaCointelegraph tweet media
English
149
91
896
59.8K
Robert Hoffmann
Robert Hoffmann@itechnologynet·
Visual understanding and browsing is currently out (not stopped, just slowed) Everything is now, markdown for agents, web mcp, ag-ui, ... Playwright uses accessibility for browsing not vision Give the agents the tools they need, and you might be surprised by what they can pull off.. True vision/navigation will come later
English
0
0
0
4
Ed Andersen
Ed Andersen@edandersen·
Software engineers will not be trusted to spend 50% of their salary on variable opex costs with no guarantee of productivity, unless they are executive level. this is a pipe dream to sell GPUs
TFTC@TFTC21

Jensen Huang: "If that $500,000 engineer did not consume at least $250,000 worth of tokens, I am going to be deeply alarmed. This is no different than a chip designer who says 'I'm just going to use paper and pencil. I don't think I'm going to need any CAD tools.'"

English
51
46
922
33.6K
Robert Hoffmann รีทวีตแล้ว
Robert Hoffmann
Robert Hoffmann@itechnologynet·
Something funny is happening with AI ..all the stuff Dev's knew they should be doing, but didn't, because of time/monetary constraints Are the things turning out to be the most important : ▶️ specs ▶️ docs ▶️ testing ▶️ accessibility
GIF
English
0
1
2
346
Robert Hoffmann
Robert Hoffmann@itechnologynet·
@Rahll @LanYunfeng64 And its not because of the models, it's because of the tooling loops, memory, and tool calls, are the main reason productivity jumped : so those are the ones you need to focus on, not pure prompting
English
1
0
0
31
Robert Hoffmann
Robert Hoffmann@itechnologynet·
@Rahll @LanYunfeng64 A few months ago, i would have said no, of course not ..maybe 30-50% But these days, i can ship stuff in a month that would have taken me 6-8 months to ship the same level of complexity/cleanness So yeah, depends
English
1
0
0
40
Reid Southen
Reid Southen@Rahll·
Wait wait wait waaait a second.... He's saying he wants his $500,000 engineer to actually cost him $750,000 by using $250,000 worth of AI tokens. Wasn't AI supposed to make things cheaper, not cost 50% more?
TFTC@TFTC21

Jensen Huang: "If that $500,000 engineer did not consume at least $250,000 worth of tokens, I am going to be deeply alarmed. This is no different than a chip designer who says 'I'm just going to use paper and pencil. I don't think I'm going to need any CAD tools.'"

English
153
287
3.7K
118.7K
Robert Hoffmann
Robert Hoffmann@itechnologynet·
This is mucho marketing... That said, if your best engineers are the ones that benefit the most from burning tokens, wouldn't you want them to have as many as possible? ... I'm pretty sure this includes all the ci/cd/automation pipelines that engineer will be putting in place, and burning tokens, not just them prompting in some ide/cli
English
0
0
0
32
Ed Andersen
Ed Andersen@edandersen·
@MightyMogomra Why do something in 2 minutes yourself when you could watch an agent click around for 30 minutes and maybe get it wrong
English
3
1
29
978
Robert Hoffmann
Robert Hoffmann@itechnologynet·
@zquestz @svpino Of course you'll wanna know who committed what ...but the naming conventions is up to the team to choose ...not some vendor slapping a watermark on it
English
0
0
0
3
Robert Hoffmann
Robert Hoffmann@itechnologynet·
@zquestz @svpino Everything in software should be a choice, and it's up to each team to impose their workflow And all the model providers allow changing this x.com/i/status/20349…
Robert Hoffmann@itechnologynet

@svpino @zquestz That attribution stuff is months old as ppl responsible for triaging pull requests have been banning AI committed stuff Also, everything should be a choice And yeah, even codex has it : commit_attribution developers.openai.com/codex/config-r…

English
1
0
0
4
Santiago
Santiago@svpino·
No, I don't think AI should be thanked, credited for its work, celebrated, chastised, or treated as anything other than a tool. Should we start crediting Visual Studio Code on every commit? Should we also credit Python? How about crediting Apple for their computers, which made that particular commit possible?
Josh Ellithorpe@zquestz

@svpino So you don't believe an AI should be credited for their work? What about in an age when AGI exists?

English
29
4
104
9.2K
Santiago
Santiago@svpino·
@zquestz I don't want to hide anything. I simply want full control of my commit messages. I'm replying to your suggestion that Claude attribution should be mandatory for code written by Claude. I disagree with that.
English
2
0
1
139
Robert Hoffmann รีทวีตแล้ว
Thariq
Thariq@trq212·
We just released Claude Code channels, which allows you to control your Claude Code session through select MCPs, starting with Telegram and Discord. Use this to message Claude Code directly from your phone.
English
1.2K
1.7K
18.6K
3.6M
SemiAnalysis
SemiAnalysis@SemiAnalysis_·
Olympian Gold Medalist Alysa Liu, recently went viral for her Teen Vogue rant on OpenAI Codex. “I can see why Sam Altman open sourced Codex. Clearly the experience is significantly worse than Claude Code. I was unable to feel the AGI using Codex. As oppose to using Claude Code, I felt the enlightenment coming and support UBI ”
SemiAnalysis tweet mediaSemiAnalysis tweet media
English
49
38
962
159K
trent.sol
trent.sol@trentdotsol·
if foundation wants to vibe code shitty copypasta of things that already exist to use their "distribution" to "benefit" the ecosystem, right here > 12. All of the top wallets are still closed source. No progress made there, and seems like no one cares.
Noah 🎈@redacted_noah

It's been about a year, so I think it'd be fun to look back and see which of these complaints has been solved. 1. IDL infrastructure is even more of a mess now. There's now two sources of truth, the original PDA and now a metadata program. Unfortunately, the metadata program was built without first class support for IDL versioning. So, next time IDLs change major versions, expect more pain. 2. Parsing historical programs given the lack of IDL versioning/history is still a problem now, and with the added metadata program it's now slightly worse. 3. The read layer has improved substantially. Most rpc providers heavily index gPA, so it's not as bad (still bad). Indexers have gotten unbelievably reliable now, such that I trust running an entire UI off of indexed data. It's heavier, you have devops costs, but at least it works and you can customize to your heart's content. 4. Running an API powered by indexers is still somewhat pricey 5. Transaction sending and landing is more or less solved. I haven't had to think about this in months. Smooth as butter. 6. Anchor has gotten faster and they've fixed a lot of the issues that blow out memory. There's still a lot of improvements to be made here, and new frameworks/anchor v2 are coming. 7. CPI depth limit is set to be increased. So this will not be an issue for much longer. 8. TX size limits are set to be increased. So this will not be an issue for much longer. 9. Rent costs have gone down because SOL price shit the bed. Yay? They are also going to actually cut rent costs soon™ 10. All of the cNFT issues described still exist. These have mostly been solved by just not using cNFTs. Use core or token metadata nfts instead. 11. Errors have, for the most part, gotten better. There are still quite a few useless errors, though. 12. All of the top wallets are still closed source. No progress made there, and seems like no one cares. 13. Rust anchor client still sucks. 14. Explorers still have issues, but thanks to claude I built my own that solves most of the issues (explorer.chewing.glass) 15. The base RPC spec still sucks, but if you're okay with vendor lock-in, Helius has a ton of useful APIs. Transaction history. Ability to only fetch accounts that have changed since a given slot. Etc. 16. I actually haven't had a dependency hell issue in a few months, I also haven't upgraded anything. Maybe it's getting better? 17. I haven't had issues with preflight disabled transactions in a while. Not sure if they fixed these issues, or I just started simulating more often. 18. Running programs on a cron is largely fixed. I wrote tuktuk for this, and it's been running reliably for almost a year. Largely things seem to be getting better. I've noticed that a lot of the pain goes away if you shove all of your solana-related stuff into an API, and use that API from your various clients web2 style. You can leverage indexers for complex queries. You can change your program and IDLs without breaking all clients. You can record your own transaction history. Etc. I always had a dream that blockchain dev was a way to avoid devops costs and burden by running everything on decentralized infrastructure. We seem to have moved far from this ideal, web3 is just web2 with another kind of database. Doesn't look great for protocols outliving their parent companies, but as we've seen that almost never happens anyway.

English
10
1
41
4.2K
Robert Hoffmann รีทวีตแล้ว
AlexandrIA
AlexandrIA@AleRVG·
Uncharted Life 2.0 🦠 ⚙️ Midjourney + Topaz
English
96
364
3.1K
330.1K