Serhii Vasylenko
banner
devdosvid.blog
Serhii Vasylenko
@devdosvid.blog
Staff Software Engineer @Grammarly | Infrastructure & DevEx | AWS | Security Automation | Also blogging at https://devDosvid.blog
With IaC rooted so deep into infra management with its declarative and deterministic behavior, using agentic CLI tool that is never deterministic feels quite unnatural now.
June 30, 2025 at 10:08 PM
Oh thanks for watching! 💚 In short words, it’s a combination of support from leadership and real value for the teams (by co-creating templates with devs). Of course not 100% use them but we “softly” close the possibilities of custom setups making them exceptional. So majority accepted it well.
May 20, 2025 at 12:23 PM
Should we expect a podcast? This would be an amazing duet!
May 19, 2025 at 1:12 PM
Well, there is an AI CEO as well; I bet we can gather a full staff with those tools so they could launch a startup 😀
May 4, 2025 at 9:56 PM
So far, the one perk I know to improve the decision-making capabilities — is to use the sequential thinking MCP from Anthropic. This adds up to the total “thinking” time but results are generally better and decision making is more reliable.
github.com/modelcontext...
servers/src/sequentialthinking at 93a9e036bfd801096b8cb545ebe9e089cb282893 · modelcontextprotocol/servers
Model Context Protocol Servers. Contribute to modelcontextprotocol/servers development by creating an account on GitHub.
github.com
May 4, 2025 at 12:38 PM
Nice article; thanks for sharing! That one about “blind copy-paste coding” is a good sign indeed, but it kind of contradicts those agentic features when an assistant can make code changes for you. Anyway, I believe over-reliance on AI makes one a weaker engineer in the long run.
May 2, 2025 at 10:09 AM
IMO, there is nothing shocking in that as long as it is the human then who reads that code and commits/pushes to git. I write a lot of code with AI but I read and adjust that code then. AI coding is a powerful instrument but it does not mean that we remove all the guardrails we have.
April 30, 2025 at 11:09 AM
Wonder how it could do the changes described (it’s clear that it did modify TF files code) and at the same time had issues with other tf files. 😀
April 29, 2025 at 1:40 PM
😄 Not only at large ones. What I observed, though, is that people magically find the ways to contribute if they *really* need the change. If not, they are OK to wait. Or even to abandon the idea. But the outmost blocker is docs or large code base which is less of an issue nowadays with AI tools.
April 28, 2025 at 6:50 PM
I also see how it gains popularity in secops tooling too. But then, of course, this ML > AI popularity evolution is the most prominent and well deserved. Wonder if Go will get some boost besides cloud-native solutions and utilities-for-any-kind.
April 28, 2025 at 6:39 PM
Sunday is good for cats, not for releases :-D
April 27, 2025 at 8:33 PM
You’re now now just one step away from using some automation for these queries to send you an alert if the response crosses some threshold. MCP-SRE basically 😄
April 6, 2025 at 8:11 AM
Seems like instead of focusing on the genuine customer pain and making a real value and the purpose of the apps from that, a lot of companies are adding AI as a “magic solution to everything” and putting that fact on a spotlight with lower focus on discovering real customer pains or needs.
March 6, 2025 at 10:12 AM
Some punch about JavaScript vibes and Electron-ish ubiquitous could be here, but I’ll just say that I feel your pain 😅
February 5, 2025 at 9:42 AM