Kir Maximov 🇺🇦

If you ever wanted to take a look at TeamCity but didn't want to connect your own repos, this is for you. We set up a demo instance of TeamCity that you can check out without connecting your own data: 👉 see.teamcity.com, login as guest.

New course: Spec-Driven Development with Coding Agents, built in partnership with @jetbrains, and taught by @paulweveritt. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track! deeplearning.ai/short-courses/…

I'm looking for work, so if you want an experienced devrel person/leader, if you need a technical educator, or if you want some consulting on how to help your devs work more effectively, ping me.

I used Claude Code + @TeamCity MCP to set up two CI projects from scratch -- entirely from the terminal. Created two projects, VCS roots with SSH deploy keys, build configs, versioned settings repos — all through the REST API and MCP tools. TeamCity generated the Kotlin DSL and pushed it to GitHub. The MCP integration lets you query builds, read logs, and configure projects conversationally. The setup that would normally be 30 minutes of clicking through admin UI took one session. Total: two projects, two settings repos, four deploy keys, versioned Kotlin DSL — all wired up. #TeamCity #MCP #AIAgents #DevOps

@bunopus Коллега тут run-agent.sh наваял - может тебе будет любопытно

Попробовал Pi shittycodingagent.ai Чёт не понял прикола. Вернее понял, но идейно это не для меня (пока). Из коробки нет sub-agents, plan mode, permission gates, path protection, SSH execution, sandboxing, MCP integration, custom editors, status bars, overlays Вся идея, что ты настраиваешь это для себя – а я как вайбкодер выходного дня хочу это всё прямо здесь и сейчас 🤷‍♀️ Поэтому пока сижу на cursor и gemini

Our technical lead Pavel has reviewed thousands of commits over the years. That experience helps him spot changes that work technically but don’t fit the project, and suggest better approaches. The question is: How do we teach AI agents to be like Pavel? Here's how we taught AI agents to see the bigger picture 👉 jb.gg/43k9ac

What's interesting about this CLI client - you can actually open a terminal to the remote agent that is running a build (if you have permissions, of course). #teamcity

@bunopus Welcome :)

Сменил работу, теперь Head of Engineering в JetBrains 🥳

Unlike standard MCP, where agents are limited to a fixed command set, MCP Steroid plugin for IntelliJ-based IDEs gives agents programmatic access to the full IDE via Kotlin code — refactoring, debugger, inspections, everything developers love about JetBrains. The agent writes its own code to work with IntelliJ APIs for each specific task. Result: 20–54% speedup on benchmarks. Runs headless — drop it into CI or any agentic pipeline. 🔗 mcp-steroid.jonnyzzz.com #MCP #AIAgents #JetBrains #IntelliJ #DeveloperTools #AgenticAI #Kotlin #VC #NeedFunding #MCPSteroid

Me reviewing code generated by Claude before pushing to prod

AI updates in JetBrains IDEs. Carefully delivered. Symmetrically aligned.

Checkvist + Chrome split view is indeed a nice combo.

Děkuji všem lidem, kteří i letos dorazili na Staroměstské náměstí ukázat, že stále stojíme za Ukrajinou. A že za ní budeme stát, dokud to bude potřeba.

TeamCity 2025.11 On-Prem just got better 🚀 Two quality-of-life tweaks for the IJ plugin, 13 bug fixes, 8 performance updates, and 5 security fixes. Grab the latest bug-fix update here: jb.gg/reneqv

@simongeering @teamcity I'm not entirely get the question, but almost all of the agents fetch sources from Git repositories (with some pre-fetched mirrors sometimes)

@teamcity Please if you can say; Does that use git integration or not?

At JetBrains, we build everything with TeamCity — from small plugins to full-blown IDEs. Today our internal TeamCity server hit a new record: 10,000 build agents running simultaneously 🚀 When your workload is huge, TeamCity scales with you. See how others use it in the real world: jetbrains.com/company/custom…

@kirillkovalenko @teamcity It is a 6-nodes setup, ~110Gb used memory each. Data from build agents is handled by 5 nodes, ~2000 running builds per node.

@teamcity i'm wondering what are the specs of the hardware where the TC server runs, CPU usage, memory allocation and IO metrics.

Quarter-century of IntelliJ IDEA. I made a small archive repo for the earliest versions, and the best part is the screenshots: github.com/CrazyCoder/int… Sharing in case anyone else enjoys digging through old software. #intellijidea #jetbrains

@sama A decent reply would be to send your message via a funny ad, not via a tweet. Maybe hire a good agency?

First, the good part of the Anthropic ads: they are funny, and I laughed. But I wonder why Anthropic would go for something so clearly dishonest. Our most important principle for ads says that we won’t do exactly this; we would obviously never run ads in the way Anthropic depicts them. We are not stupid and we know our users would reject that. I guess it’s on brand for Anthropic doublespeak to use a deceptive ad to critique theoretical deceptive ads that aren’t real, but a Super Bowl ad is not where I would expect it. More importantly, we believe everyone deserves to use AI and are committed to free access, because we believe access creates agency. More Texans use ChatGPT for free than total people use Claude in the US, so we have a differently-shaped problem than they do. (If you want to pay for ChatGPT Plus or Pro, we don't show you ads.) Anthropic serves an expensive product to rich people. We are glad they do that and we are doing that too, but we also feel strongly that we need to bring AI to billions of people who can’t pay for subscriptions. Maybe even more importantly: Anthropic wants to control what people do with AI—they block companies they don't like from using their coding product (including us), they want to write the rules themselves for what people can and can't use AI for, and now they also want to tell other companies what their business models can be. We are committed to broad, democratic decision making in addition to access. We are also committed to building the most resilient ecosystem for advanced AI. We care a great deal about safe, broadly beneficial AGI, and we know the only way to get there is to work with the world to prepare. One authoritarian company won't get us there on their own, to say nothing of the other obvious risks. It is a dark path. As for our Super Bowl ad: it’s about builders, and how anyone can now build anything. We are enjoying watching so many people switch to Codex. There have now been 500,000 app downloads since launch on Monday, and we think builders are really going to love what’s coming in the next few weeks. I believe Codex is going to win. We will continue to work hard to make even more intelligence available for lower and lower prices to our users. This time belongs to the builders, not the people who want to control them.

A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective - I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering": - "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight. - "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind. In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.