Joined March 2010
264 Photos and videos
Michał Czyż retweeted
Apr 4
Top Agentic Development Environments for 2026 #1 - Zed - Open Source - ACP support - Claude without their god awful harness - Project tabs - Performant - SSH tabs - Beautiful #2 - T3Code - Open Source - Good, consistent team - Claude without the god awful harness - Performant - Looks Fine #3 - CMUX - Ghostty terminal works amazing w all agents - Nice browser feature altho I don't like webkit - MORE PANES BRO MORE PANES - Tabbed projects #4 - Ghostty - Bare bones - Most performant #5 - Codex App - Feels nice I use this the most of all the "apps" - I love automations and plugins - Needs to be open sourced
78
20
548
64,171
What’s your go-to #ADE (Agentic Development Environment) setup? I'm still dailing in ...
61
AI Engineering with #DarkFactory one week in and it’s starting to feel real. Not there yet, but its getting better. Whats your experience with Dark Factory - did you already switch the lights off? 😉
25
Michał Czyż retweeted
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow. Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes. As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now. It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.
1,600
4,727
37,163
5,142,258
Michał Czyż retweeted
I’m joining OpenAI Codex to work on the future of agentic development! At Cursor, I got to see the shift from autocomplete to agents. The next step isn’t a better IDE. It’s an Agent Development Environment (ADE): systems and tools for orchestrating agents, reasoning over their outputs, and making them autonomous enough to reliably complete ambitious work. After chatting with @embirico and @thsottiaux, it was clear that Codex is the best place to realize this vision. The team has consistently shipped SOTA models for agentic coding (check out gpt-5.3-codex) and I’m pumped for the future that the new Codex App points to. What I’m most excited about is the broader mission: accelerating the knowledge work economy. All agents are coding agents, and we’re already seeing Codex used across every job function within organizations. I’m extremely grateful for my time at Cursor, working with the incredible team, and I’m proud of what we built together. I’m excited to take an even bigger swing with Codex. If you’re curious to get a glimpse of where we are headed, download the Codex App! If you want to work on this mission, please apply or reach out - we are hiring across all functions! You can just build things.
217
98
2,691
759,193
First hurdle cleared - dark factory is alive ⚫ overseer is working ...
56
Codex (app) is the first user interface that actually fits agentic engineering. The editor isn't treated as the centerpiece; diffs finally have a clear, readable home, and the terminal sits exactly where it should. Early days, but this is a strong start. Kudos to @openai and the Codex team - @OpenAIDevs
2
324
Agentic coding forces better architecture - systems that are easy to verify. Without a closed verification loop, it’s just vibe coding. With it, it becomes scalable engineering. Highly recommend watching the full interview with @steipete youtube.com/watch?v=8lF7HmQ_…
1
49
Michał Czyż retweeted
damn I should stop using markdown files in git
40
5
405
122,306
What is big-pickle and why is it ~6x slower then GPT-5.2 max? In @opencode benchmarks, Grok and GLM return meaningful review feedback, bug big-pickle return round trips the input prompt. What is I'm doing wrong? #opencode #benchmark #AI
167
Michał Czyż retweeted
millennial gamers are the best prepared generation for agentic work, they've been training for 25 years
275
641
7,448
1,529,958
AI’s biggest leverage in software isn’t code generation. It’s cheaper thinking before commitment: exploring options, pressure-testing assumptions, invalidating ideas early. Faster learning → fewer irreversible mistakes. Full take ↓ linkedin.com/pulse/ais-bigge… #AI #SoftwareEngineering #ProductDevelopment #DecisionMaking #GenAI
38
My top picks for @claudeai update: Slash command autocomplete now works anywhere you type / --tools in interactive mode to restrict which built-ins Claude can use /plan shortcut to jump straight into plan mode Fix: claude /context (and other CLI slash commands) now execute correctly (not like bash cmd) Great Job!
1
24
Michał Czyż retweeted
Jan 7
"I also get some programmers are eager to tune it out. The hype drones on, the fantastical claims are still far off, and there's uncertainty where this leaves the profession. But that's not reason to miss out on this incredible moment in human history!" world.hey.com/dhh/promoting-…
59
93
1,019
152,316
2025 is a wrap: 11,270 commits (looks like an 8-person team 😅). AI-assisted coding changed the game this year. #GitWrapped #2025 #AICoding #Ruby #DevLife #OpenSource
29
Michał Czyż retweeted
27 Dec 2025
Using a mocap suit to kick yourself in the balls with a robot is a great metaphor to close out 2025.
663
16,051
128,805
5,834,774
23 Dec 2025
Claude just called custom #command a #skill. Is that new, or did I just miss it until now? @ClaudeCodeLog (i know about agent skills) #ClaudeCode
81
20 Dec 2025
The year isn’t over. Still — these numbers feel… different. #AICoding #VibeEngineering #Ruby
44
Michał Czyż retweeted
Last quarter I rolled out Microsoft Copilot to 4,000 employees. $30 per seat per month. $1.4 million annually. I called it "digital transformation." The board loved that phrase. They approved it in eleven minutes. No one asked what it would actually do. Including me. I told everyone it would "10x productivity." That's not a real number. But it sounds like one. HR asked how we'd measure the 10x. I said we'd "leverage analytics dashboards." They stopped asking. Three months later I checked the usage reports. 47 people had opened it. 12 had used it more than once. One of them was me. I used it to summarize an email I could have read in 30 seconds. It took 45 seconds. Plus the time it took to fix the hallucinations. But I called it a "pilot success." Success means the pilot didn't visibly fail. The CFO asked about ROI. I showed him a graph. The graph went up and to the right. It measured "AI enablement." I made that metric up. He nodded approvingly. We're "AI-enabled" now. I don't know what that means. But it's in our investor deck. A senior developer asked why we didn't use Claude or ChatGPT. I said we needed "enterprise-grade security." He asked what that meant. I said "compliance." He asked which compliance. I said "all of them." He looked skeptical. I scheduled him for a "career development conversation." He stopped asking questions. Microsoft sent a case study team. They wanted to feature us as a success story. I told them we "saved 40,000 hours." I calculated that number by multiplying employees by a number I made up. They didn't verify it. They never do. Now we're on Microsoft's website. "Global enterprise achieves 40,000 hours of productivity gains with Copilot." The CEO shared it on LinkedIn. He got 3,000 likes. He's never used Copilot. None of the executives have. We have an exemption. "Strategic focus requires minimal digital distraction." I wrote that policy. The licenses renew next month. I'm requesting an expansion. 5,000 more seats. We haven't used the first 4,000. But this time we'll "drive adoption." Adoption means mandatory training. Training means a 45-minute webinar no one watches. But completion will be tracked. Completion is a metric. Metrics go in dashboards. Dashboards go in board presentations. Board presentations get me promoted. I'll be SVP by Q3. I still don't know what Copilot does. But I know what it's for. It's for showing we're "investing in AI." Investment means spending. Spending means commitment. Commitment means we're serious about the future. The future is whatever I say it is. As long as the graph goes up and to the right.
5,114
25,549
171,335
25,912,645