Joined April 2010
26 Photos and videos
How do you manage MCP servers across multiple agents?
1
2
47
Apr 21
need to look into this
With all the recent codebase security vulnerabilities, running this Claude Code prompt is more important than ever. If you've ever vibe-coded a project, use this Claude prompt to conduct a deep audit of your codebase. Analyses API key exposures, critical errors, and more:
1
38
Sladjan retweeted
With all the recent codebase security vulnerabilities, running this Claude Code prompt is more important than ever. If you've ever vibe-coded a project, use this Claude prompt to conduct a deep audit of your codebase. Analyses API key exposures, critical errors, and more:
25
41
440
33,411
Apr 21
How do you keep track of important conversations on X? I mean, we cannot be online all the time. Is there a way to catch relevant topics?
2
3
43
Apr 21
Reminder
Totally agree. Often, you can't figure out what you need to build until you build the wrong thing and get it in front of actual users. Good news is that it's easier than ever to get *something* built and in front of actual users.
4
Apr 20
lol yeah, Codex is always #1 on this list
i'm gonna get trauma from this screen especially because "paused" doesn't really mean paused, and "Resume" is just there for decoration - it literally does nothing
15
Apr 20
Just recently saw this, and plan to subscribe
iximiuz Labs usage keeps growing - we're on track to set another monthly record of solved challenges. People who discovered the platform love using it to practice Linux, Docker, Kubernetes, and networking. Now we need more people to become aware of iximiuz Labs. And you can help! Tell your friends and colleagues about the platform, send the link to your manager and the CTO. And in return, get a month of free Premium for every 2 friends you invite. Win-win!
1
1
386
Apr 19
Time to sleep, but new reset in 25 mins  🥳
46
Apr 19
Agreed if we are talking about pure coding, I think 2 is max to be fully present and productive. But we can spin multiple agents to stress test the feature from different angles. Another thing is analyzing our feature and comparing it to best practices, finding issues, gaps etc. Today I ran a stress test session with Codex for 4 hours, while having 2 coding sessions for 2 features.
OVERRATED: running tons of agents in parallel; working on too many things at once; perpetual context-switching; opening lots of low-quality PRs that may never land. UNDERRATED: using one or two agents at a time; focusing on the task in front of you; thinking deeply; finishing stuff; making your code works in prod.
46
Apr 19
Great idea, I would also recommend trying the superpowers plugin, both for Claude Code and Codex. Sometimes I iterate daily on questions and planning before giving spec and plan to an agent to produce code.
A tip, especially if you're newer to building with Codex: Before you plan a build in Codex, talk it out first. Sit down and have a conversation about what you want to build. Ask questions. Clarify the details. Work through every unknown you have about the project before you ever touch a plan. If you have multiple paths you can take, pull on the threads, so to speak. You should be part of the process, dont let the agent make every decision for you. Most people jump straight into planning mode and then wonder why the agent keeps going off track. The problem usually isn't the agent... A great tool for this is the AskQuestion tool. It lets Codex pause and ask YOU questions, turning it into a back-and-forth brainstorming partner instead of a one-shot mind reader. Enable it in default Codex mode with: codex features enable default_mode_request_user_input Let it drill you on edge cases. Let it poke holes in your assumptions. Solidify your ideas. THEN plan. (Side note, whoever named that committed a felony.)
132
Apr 19
What hobbies do you have? To provide my brain enough space to grow and not be tied only to work, I started growing a tangerine. Next is lemon and orange, which will be bit challenging in our climate Tangerine going strong, still bit cold days with couple morning frosty so keeping it inside by the window.
20
Apr 19
"agents are insanely good at tasks with clear inputs and outputs. content drafts, data extraction, competitor analysis. like 90% as good as a human, 50x faster" Totally agree on this.
Apr 19
ngl I've been mass-testing AI agents across all my products for the last 2 weeks tried to replace entire workflows. customer support, content generation, SEO audits, social scheduling here's what I found: agents are insanely good at tasks with clear inputs and outputs. content drafts, data extraction, competitor analysis. like 90% as good as a human, 50x faster but they still completely fall apart when context matters. when you need taste. when the answer is "it depends" I watched an agent confidently give a user the wrong Outrank plan recommendation 3 times in a row because it optimized for the metric instead of the actual need so painful to watch 😅 my take: the best AI-native products in 2026 won't be "fully automated" anything they'll be the ones that figure out the exact moment to hand control back to a human that handoff is the whole product
46
Apr 19
America wasn't discovered, it was built. Did you watch The men who built America? I highly recommend it. I see AI comparing to steel from that time and it is changing how we live and work. Some will earn big buck with it, some will fail, but in the end our lives will be improved. Oil, steel, electricity, internal combustion engine, internet, mobile phone, AI. Probably missed some, for example I don't see crypto currencies on this level as human changing tech(prove me wrong?) Curious to hear your opinion on this @ivanburazin
27
Apr 18
Do you track X analytics? Why yes? Why not?
1
2
47
Apr 18
morning standup with your gang
26
Apr 17
How many agents are you using? As most of the people started with Claude Code, then added Codex, yesterday started messing around GLM(trying to save some money lol). Anyway, I think the future is in some form of abstraction where agents from different vendors are specialized for something. For example, I currently chit-chat with Claude Code(Opus 4.6/7) to build a good plan. Then use Codex to revise the plan and execute. Today GLM execution on well detailed plan.
47
Apr 15
What general rules do you ask your agents to follow? Not necessary claude.md/agents.md stuff, but also when you start implementing the plan? I noticed better results when I started the implementation asking the agent to follow these rules: - Be concise and pragmatic. Always first plan and think before coding - Stick to software principles like SOLID, KISS, DRY, and YAGNI - Do not take shortcuts and cut corners, plan must be followed step by step, byte by byte - Never reinvent the wheel. If there a library for something we can download and use, use it. E.g. monaco editor for code snippets, use it, don't reinvent the wheel and build from scratch. - Don't leave unused, dead code after you do your work - The more we test and verify the better - Files and folders named logically - Split files into folders based on logic and domain, aim for <10 files per folder - Aim for <100 LOC (if possible per file)
1
40
Apr 15
When making a plan, use the Superpowers plugin with Codex or Claude Code. But that is not enough. When the initial plan draf is done, ask it a simple question "What do you think?" And then do it 10 times if needed. It will self-reflect, find issues in the plan, and fix them. You will usually see 10 issues found, then 7, then 4 etc After hammering it enough, the plan will be much better, just by using "What do you think?" Treat the agent as a human, not a machine.
76
Apr 15
I think the key is not Codex vs Claude Code vs < preferred agent>. We need to use them all together, exploiting their strength in different situations. This morning, Codex was stuck on something simple for multiple iterations. Claude Code found the issue in 1 go. A couple of days ago, it was backwards. I see people complaining that Codex is not producing good UI. Ok, we can use Claude Code for that. Currently, if I want to chat more, I use Claude Code. Make a spec and plan. Then, if it is a long-running plan, I put Codex to work on that same plan.
48