Elhaam

2.5K posts

Elhaam banner
Elhaam

Elhaam

@standoutcoder

Making fast websites at https://t.co/dN1U1ZDp1Q

Joined Haziran 2022
349 Following89 Followers
Elhaam
Elhaam@standoutcoder·
@nexxeln @opencode Am I the only one who feels features in Desktop versions are coming way too quickly in comparison to the TUI?
English
0
0
0
54
nexxel
nexxel@nexxeln·
in the next release of @opencode desktop you can now see git and branch changes in the review panel
English
33
14
667
42.4K
Elhaam
Elhaam@standoutcoder·
@anuraggoel Yeah nobody needs these when you can afford to break production. Try telling doing this to a product that matters. But wait maybe they are, that's we see AWS down everyday.
English
1
0
1
54
Anurag Goel
Anurag Goel@anuraggoel·
AI is quietly deprecating GitHub. Agents do not need branches, PRs, or CI/CD rituals. They want to ship code straight to the cloud. The rsync renaissance is here. High availability. Zero bloat. Faster loops.
English
342
17
375
474.5K
Elhaam
Elhaam@standoutcoder·
@thdxr An agent raises a PR, Greptile reviews it and posts a 3/5 review. There's no way for the agent to handle this in an "agentic" way so that it goes back and forth until 5/5 is acheived. Maybe we need an event-driven integration here @greptile
English
1
0
0
50
dax
dax@thdxr·
i still don't get why we need to push code up to get an LLM review via awkward github ui hacks opencode has /review which can also do things like run your code to check things but a full time team focused on this would do it better, i just don't like the workflow they offer
English
85
9
903
59.4K
Elhaam
Elhaam@standoutcoder·
@thdxr Never had it open always, but I do look at it sometimes. Maybe it can be replaced with a focused tool for viewing relevant stuff
English
0
0
0
16
dax
dax@thdxr·
do you use the opencode sidebar
English
84
0
81
25.4K
Elhaam
Elhaam@standoutcoder·
@neetcode1 Scary We know that using Agents for everything causes skill regression, but it's increasingly feeling like that's the only option now. I thought that now, for once, we would be able to match unrealistic software timelines. But AI has pushed it into a new zone.
English
0
0
0
20
Elhaam
Elhaam@standoutcoder·
@thdxr Give padding by default, give option to customize in the conf
English
0
0
0
5
dax
dax@thdxr·
messing with tighting up opencode ui and removing the horizontal padding better? worse?
dax tweet media
English
91
0
430
44.6K
Elhaam
Elhaam@standoutcoder·
@theo I wish these companies thought about this too. Sadly this is something OpenCode sucks at too at times. Takes a massive chunk of RAM.
English
0
0
0
100
Theo - t3.gg
Theo - t3.gg@theo·
T3 Code uses half as much RAM as Claude Code. Claude Code CLI: 635.5 MB T3 Code: 350.9 MB Yes, our Electron app is 2x more efficient than a CLI written with Bun.
English
180
28
2.6K
164.8K
Kimi.ai
Kimi.ai@Kimi_Moonshot·
Congrats to the @cursor_ai team on the launch of Composer 2! We are proud to see Kimi-k2.5 provide the foundation. Seeing our model integrated effectively through Cursor's continued pretraining & high-compute RL training is the open model ecosystem we love to support. Note: Cursor accesses Kimi-k2.5 via @FireworksAI_HQ ' hosted RL and inference platform as part of an authorized commercial partnership.
English
520
1.4K
20.4K
3.5M
Elhaam
Elhaam@standoutcoder·
@karpathy The more AI tools we use, the more I realize that code quality or "clean" matters less sadly. Is this the future we are heading into? If we never "write" the code, does the "cleanliness" matter? If we do not understand the "code" we write, then how can we take ownership of it?
English
0
0
0
25
Andrej Karpathy
Andrej Karpathy@karpathy·
Thank you Sarah, my pleasure to come on the pod! And happy to do some more Q&A in the replies.
sarah guo@saranormous

Caught up with @karpathy for a new @NoPriorsPod: on the phase shift in engineering, AI psychosis, claws, AutoResearch, the opportunity for a SETI-at-Home like movement in AI, the model landscape, and second order effects 02:55 - What Capability Limits Remain? 06:15 - What Mastery of Coding Agents Looks Like 11:16 - Second Order Effects of Coding Agents 15:51 - Why AutoResearch 22:45 - Relevant Skills in the AI Era 28:25 - Model Speciation 32:30 - Collaboration Surfaces for Humans and AI 37:28 - Analysis of Jobs Market Data 48:25 - Open vs. Closed Source Models 53:51 - Autonomous Robotics and Atoms 1:00:59 - MicroGPT and Agentic Education 1:05:40 - End Thoughts

English
311
386
5.4K
1M
Elhaam retweeted
dax
dax@thdxr·
opencode 1.3.0 will no longer autoload the claude max plugin we did our best to convince anthropic to support developer choice but they sent lawyers it's your right to access services however you wish but it is also their right to block whoever they want we can't maintain an official plugin so it's been removed from github and marked deprecated on npm appreciate our partners at openai, github and gitlab who are going the other direction and supporting developer freedom
English
270
493
9K
1.1M
Elhaam
Elhaam@standoutcoder·
@alvinsng Yes, useEffect is a footgun, but some of this feels like a skill issue to me. When people not knowing a tech stack well start using ti then obviously there is something wrong.
English
0
0
3
690
Elhaam retweeted
Ujjwal Chadha
Ujjwal Chadha@ujjwalscript·
Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster. Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!" But here is the reality check we are ignoring: Code is a liability, not an asset. If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year. We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance. If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.
English
398
539
4.2K
635.9K
Chief Nerd
Chief Nerd@TheChiefNerd·
🚨 SAM ALTMAN: “We see a future where intelligence is a utility, like electricity or water, and people buy it from us on a meter.”
English
5.5K
2.7K
12.6K
26.4M
Elhaam
Elhaam@standoutcoder·
@shadcn Its better for long running tasks that require figuring out. Opus would suit this style of work better.
English
0
0
0
35
shadcn
shadcn@shadcn·
Been trying to make Codex work for me but it overthinks everything, even simple stuff. Tried different reasoning levels, no difference. It just tries too hard. Good at reviewing others work though.
English
173
13
1.2K
297.8K
Elhaam
Elhaam@standoutcoder·
@chribjel At this rate, C is an assembly wrapper, no?
English
0
0
0
13
Christoffer Bjelke
Christoffer Bjelke@chribjel·
theo, the king of wrappers t3chat -> llm wrapper t3code -> agent wrapper whats next?
English
107
5
1.5K
214.3K
Elhaam
Elhaam@standoutcoder·
@theo Was already being done by oh my opencode though.
English
0
0
0
107
Elhaam
Elhaam@standoutcoder·
This brings mist to eyes.
ThePrimeagen@ThePrimeagen

I have been thinking about this a lot. I think for a great many of engineers, the ones who did it because they loved it only to discover that money was in fact at the end of the rainbow found both the journey and the destination satisfying. In fact, I think I can argue with authority that the destination was only satisfying as the journey was difficult. The hard-fought evenings spent toiling away on an idea and codebase that slowly gives way to your vision was an incredible experience. The group of people that fell into this category of hard-fought journey and destination we will call them tinkerers. One thing tinkerers have always hated is the already known problems. The journey is clear as day. The obstacles minor inconveniences. Its purely a matter of typing the solution into the terminal. This is also why I think so many of this group goes out and does open source, or starts companies. Work largely falls into this category with few exceptions. From this reason is why I largely find UI work soul sucking. I know the solution, its a matter of just looking up the details and putting it into my editor. yawn. CSS, flex box this, grid that, put the tailwind classes in the bag. To me, the LLM software world is with little to no journey and discovery. Its more of simply taking my high level idea and just formulating it into testable, atomic chunks that can be verified. I have traded my favorite part, discovery and raw creation, with itemized list of TODOs and patience and "No Mistakes." To this, every morning from 6 to 9 I simply just hand code every thin. even UI things. It is because I want journey and discovery and raw creation. Maybe one day comes and its just so futile that I stop this. But for now, I still see such great value in this. I see such better thought through products. Because slowing down and truly thinking through everything. The architecture, the design, everything is an expression of discovery and creation. And I love it. I am sure there will come a day, maybe even in the next 6 months where I change my mind. For now, I pursue the love of the game intentionally. I do also believe that there exists people who get the same joy I got from building with tears and sweat by prompting LLMs. I am positive of it. I just don't understand how. But people love UI work. I also don't understand that.

English
0
0
0
9
Elhaam
Elhaam@standoutcoder·
This is interesting. But in woodwork, the thing you do is the art. In coding, the thing you do or make isn't, the end result is. This might apply to libraries or similar though.
Grimfrost Mage@grimfrostmage

@adamdotdev People still woodwork by hand because they enjoy it and create art with it that is hard or near impossible to do at scale. Some still paint or write by hand. Some buy old cars because they are more enjoyable to work on. Find an art project and turn off the AI.

English
0
0
0
25