<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MCP on miti99</title><link>https://miti99.com/en/tags/mcp/</link><description>Recent content in MCP on miti99</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Nov 2026 17:39:19 +0700</lastBuildDate><atom:link href="https://miti99.com/en/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Newsletter #39</title><link>https://miti99.com/en/post/2025/07/29/</link><pubDate>Tue, 29 Jul 2025 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2025/07/29/</guid><description>&lt;p&gt;&lt;em&gt;Enjoy Newsletter #39.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="100-senior-java-developer-interview-questions-and-answers--2025-edition"&gt;&lt;a href="https://dev.to/haraf/100-senior-java-developer-interview-questions-and-answers-2025-edition-4f6n" rel="noopener noreferrer"&gt;100+ Senior Java Developer Interview Questions and Answers – 2025 Edition&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;This DEV Community guide compiles over 100 interview questions and answers aimed at senior Java developer roles in 2025, organized into five tracks. The Core Java section covers 25 questions split evenly across multithreading and concurrency (deadlocks, the &lt;code&gt;volatile&lt;/code&gt; keyword), collections and their internal implementations, object-oriented design principles, memory management (garbage collection, heap layout), and Java 8+ features like functional interfaces, streams, and &lt;code&gt;Optional&lt;/code&gt;. The Spring Boot and microservices section adds another 25 questions covering auto-configuration, bean lifecycles, inter-service communication (REST, gRPC, message queues), security with JWT, OAuth2, and role-based access control, observability tools like Sleuth, Zipkin, and Prometheus, and deployment and fault-tolerance strategies.&lt;/p&gt;
&lt;p&gt;The remaining three sections feature 20 questions on design patterns (Singleton, Factory, Strategy, Builder, Observer, Proxy, Adapter), 15 on algorithms and data structures (complexity analysis, sorting, searching, graph traversal, Tries, LRU caches), and 15 on SQL and databases (&lt;code&gt;JOIN&lt;/code&gt;s, normalization, indexing, ACID properties, and consistency in distributed systems). What makes the list useful is its focus on real-world engineering scenarios rather than trivia syntax. For junior and mid-level developers, it serves as a solid roadmap for spotting knowledge gaps on the way to senior roles.&lt;/p&gt;
&lt;h2 id="the-prompt-engineering-playbook-for-programmers"&gt;&lt;a href="https://addyo.substack.com/p/the-prompt-engineering-playbook-for" rel="noopener noreferrer"&gt;The Prompt Engineering Playbook for Programmers&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Addy Osmani (Google) distills practical techniques for prompting AI coding assistants around seven core principles: provide rich context (language, framework, error messages, expected behavior), state specific goals, break large tasks into smaller steps, include input/output examples (few-shot prompting), assign a role such as code reviewer or security specialist, iterate across multiple turns, and keep your own codebase clean and well-named. His baseline rule is to assume the AI knows nothing about your project beyond what you explicitly put in front of it. For debugging, a reliable template is &amp;ldquo;the code is supposed to do X, but instead does Y when given input Z&amp;rdquo;; in the post&amp;rsquo;s example, pairing the error trace with sample data and expected output lets the AI immediately spot an off-by-one loop condition.&lt;/p&gt;
&lt;p&gt;When refactoring, spell out the exact goal—readability, performance, deduplication, or preserving existing error behavior—rather than just saying &amp;ldquo;refactor this.&amp;rdquo; For new features, start from a high-level outline and build incrementally: scaffold the component first, add state management next, and wire up the API last. Common pitfalls include vague prompts, cramming too many requirements into a single turn, and omitting success criteria. Osmani advises treating AI like an eager junior developer: give clear direction, iterate patiently, and ask it to explain its reasoning so you solve the problem and learn at the same time.&lt;/p&gt;
&lt;h2 id="why-your-ai-coding-assistant-keeps-doing-it-wrong-and-how-to-fix-it"&gt;&lt;a href="https://blog.thepete.net/blog/2025/05/22/why-your-ai-coding-assistant-keeps-doing-it-wrong-and-how-to-fix-it/" rel="noopener noreferrer"&gt;Why Your AI Coding Assistant Keeps Doing It Wrong, and How To Fix It&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Pete Hodgson argues that instead of debating whether &amp;ldquo;AI writes good code,&amp;rdquo; we should ask which kinds of tasks AI excels at and which ones to avoid handing it. AI coding assistants have a peculiar skill profile: they write implementation code like a senior engineer but make design decisions like a novice, and they permanently operate like a teammate &amp;ldquo;in their first hour on the job,&amp;rdquo; lacking knowledge of your codebase, team conventions, or domain context. To evaluate whether a task is a good fit, Hodgson proposes a two-axis matrix: solution space (from narrow, where there is only one obvious approach like removing a feature flag, to wide, where many reasonable designs exist like supporting multi-image uploads) and context required (relying on tacit team knowledge vs. information that can be stated explicitly). AI performs best when the solution space is narrow and the context is explicit, because wide solution spaces make it hard for the model to guess the &amp;ldquo;right&amp;rdquo; local convention.&lt;/p&gt;
&lt;p&gt;That framework points to two levers. To narrow the solution space, give specific implementation instructions instead of letting the AI invent the plan, and break larger problems into smaller steps. To supply missing context, state requirements explicitly in the prompt, use memory or rules files, let the agent search the codebase and read docs, and connect MCP servers to database schemas or issue trackers. In short, shape the work to play to AI&amp;rsquo;s strengths rather than expecting the tool to adapt on its own.&lt;/p&gt;
&lt;h2 id="why-ai-agents-need-a-new-protocol"&gt;&lt;a href="https://glama.ai/blog/2025-06-06-mcp-vs-api" rel="noopener noreferrer"&gt;Why AI Agents Need a New Protocol&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;This Glama.ai post explains why AI agents benefit from the Model Context Protocol (MCP) rather than relying solely on traditional HTTP APIs. The core premise is that HTTP APIs evolved to serve human developers and browser apps, not autonomous agents. MCP enforces consistency at the protocol layer itself, whereas OpenAPI merely documents existing APIs in all their idiosyncrasies; as the author puts it, you cannot fix structural inconsistency by writing better documentation. From there, the post highlights five practical differences: MCP lets agents query a server&amp;rsquo;s capabilities dynamically at runtime instead of relying on static docs; with raw APIs, models must construct HTTP requests themselves and frequently hallucinate paths or parameters, whereas with MCP the model simply selects a tool and deterministic code handles the underlying call; MCP treats bidirectional communication as a first-class primitive; each MCP tool maps to a complete user intent rather than scattering a workflow across multiple low-level endpoints; and MCP servers can run as local processes over &lt;code&gt;stdio&lt;/code&gt; with no network layer required.&lt;/p&gt;
&lt;p&gt;The author also points to the long-term payoff of standardization: models only need to learn one uniform interaction pattern instead of thousands of bespoke API dialects. The takeaway isn&amp;rsquo;t that MCP replaces HTTP APIs, but that they belong side by side—keeping APIs for developers while adding MCP as a dedicated integration layer for AI agents.&lt;/p&gt;
&lt;h2 id="understanding-logical-replication-in-postgres"&gt;&lt;a href="https://www.springtail.io/blog/postgres-logical-replication" rel="noopener noreferrer"&gt;Understanding logical replication in Postgres&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Garth Goodson, CTO of Springtail, walks through how logical replication works in PostgreSQL—replicating data at the level of logical row changes rather than copying raw physical disk blocks. Its foundation is the Write-Ahead Log (WAL): every modification is written to an append-only log before touching data files, with each record assigned a unique Log Sequence Number (LSN). The source database defines a &lt;code&gt;publication&lt;/code&gt; specifying which tables or schemas to replicate, and the target creates a &lt;code&gt;subscription&lt;/code&gt; to consume them. A replication slot tracks which WAL records have been sent and acknowledged; only WAL segments older than the replica&amp;rsquo;s confirmed flush position can be recycled, preventing data loss at the cost of requiring careful disk-space monitoring if a subscriber falls behind. Finally, logical decoding and output plugins translate raw WAL records into a consumable format; the default &lt;code&gt;pgoutput&lt;/code&gt; plugin emits two message types: &lt;code&gt;XLogData&lt;/code&gt; carrying the actual row changes and &lt;code&gt;KeepAlive&lt;/code&gt; heartbeats to maintain the connection.&lt;/p&gt;
&lt;p&gt;Logical replication is well suited for high availability, scaling out read queries, disaster recovery, and running analytical queries without bogging down the primary database. However, it comes with important caveats: it does not automatically replicate DDL changes such as schema migrations, index builds, or sequence updates; it lags behind physical replication under heavy write throughput; it requires more operational setup; and replicating &lt;code&gt;UPDATE&lt;/code&gt; or &lt;code&gt;DELETE&lt;/code&gt; operations requires tables to have a primary key or an explicit replica identity (with &lt;code&gt;REPLICA IDENTITY FULL&lt;/code&gt; as a fallback).&lt;/p&gt;
&lt;h2 id="one-man-armies"&gt;&lt;a href="https://quarter--mile.com/One-Man-Armies" rel="noopener noreferrer"&gt;One Man Armies&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;This short essay on Quarter Mile opens with a striking observation: human productivity varies wildly, and projects many assume would require a full team and $5 million are sometimes built by a single obsessed, hardworking individual. To make the point, the author lists landmark works created (almost) entirely solo: Eric Barone building &lt;em&gt;Stardew Valley&lt;/em&gt; across 70-hour weeks for 4.5 years, Markus Persson writing &lt;em&gt;Minecraft&lt;/em&gt; in 2 years, John Resig creating jQuery, Chris Sawyer writing &lt;em&gt;RollerCoaster Tycoon&lt;/em&gt; in assembly, Chris Hunt spending 12 years on the RPG &lt;em&gt;Kenshi&lt;/em&gt;, Linus Torvalds starting Linux, and Donald Knuth writing &lt;em&gt;The Art of Computer Programming&lt;/em&gt;. The list stretches well beyond software too: Ada Lovelace&amp;rsquo;s first computer program, Einstein&amp;rsquo;s general relativity, Antoni Gaudí&amp;rsquo;s 40+ years on the Sagrada Família, Marie Tharp&amp;rsquo;s first scientific map of the Atlantic ocean floor, and Karlheinz Stockhausen&amp;rsquo;s nearly 30-hour &lt;em&gt;Licht&lt;/em&gt; seven-opera cycle.&lt;/p&gt;
&lt;p&gt;The author leaves readers to draw their own conclusions, offering just one gentle nudge: if general relativity, an entire cathedral, a 29-hour opera cycle, and billion-dollar video games can be brought into the world by one person, your own ambitious, seemingly far-fetched ideas probably aren&amp;rsquo;t too big either—and if you care about them enough, they are worth trying.&lt;/p&gt;
&lt;h2 id="what"&gt;&lt;a href="https://rdel.substack.com/p/rdel-96-whats-the-relationship-between" rel="noopener noreferrer"&gt;What&amp;rsquo;s the relationship between developer seniority and code refactoring?&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;In the RDEL (Research-Driven Engineering Leadership) newsletter, Lizzie Matusov summarizes a study examining how developer seniority relates to code refactoring. Researchers analyzed 800 open-source Java projects on GitHub, mining over 700,000 refactoring operations across 111,884 commits, measuring seniority via each contributor&amp;rsquo;s Developer Commit Ratio, and using machine learning models to classify the motivation behind each refactoring. They found that the top 5% most senior contributors performed an average of 11.14 refactorings compared to 3.57 among everyone else, and applied a wider variety of refactoring techniques. Most refactorings happened while implementing new features or fixing bugs rather than as standalone cleanup, and that motivation held steady across seniority levels. Notably, the most senior developers were actually &lt;em&gt;less&lt;/em&gt; likely to document their refactorings in commit messages than less experienced contributors.&lt;/p&gt;
&lt;p&gt;From those findings, the post offers three takeaways for engineering leaders. First, encourage engineers at all levels to participate in refactoring through pair programming and shared design principles. Second, make refactoring work visible by recognizing it in retrospectives and promotion criteria. Third, standardize how refactorings are documented using lightweight commit-message prompts and code-review guidelines that apply equally to everyone, regardless of seniority.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026; reviewed and edited by Codex with GPT 6.1 Sol on 09/11/2026, and re-verified by Claude Code with Sonnet 5.5 on 16/11/2026.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Setting Up Claude Code &amp; Serena MCP on Windows</title><link>https://miti99.com/en/post/2025/07/27/</link><pubDate>Sun, 27 Jul 2025 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2025/07/27/</guid><description>&lt;p&gt;&lt;em&gt;Lately I&amp;rsquo;ve been spamming quite a few AI-generated newsletters, which gets a bit repetitive. Since I recently tinkered with the Claude Code &amp;amp; Serena combo and found it pretty solid, I decided to write a post myself for a change of pace.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&lt;p&gt;Recently I paid for a Claude Pro subscription, which includes Claude Code. Playing around with it has been fun, and I rate it higher than other agents because it works via the CLI without forcing me to install a new IDE (I&amp;rsquo;m much more used to JetBrains IDEs than VS Code. Plus, Cursor and Windsurf are annoying because they don&amp;rsquo;t sync settings across different machines, whereas Claude Code lets you share project configs). Besides, since Claude models are first-party from Anthropic, using them inside Claude Code is probably much better optimized :v&lt;/p&gt;
&lt;p&gt;In this post, I&amp;rsquo;ll walk through setting up Claude Code &amp;amp; Serena on Windows. Although &lt;a href="https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#:~:text=Added%20support%20for%20native%20Windows" rel="noopener noreferrer"&gt;Claude Code already supports Windows natively&lt;/a&gt;, when I tried it recently I still frequently ran into errors when creating new files. My guess is that it&amp;rsquo;s probably due to &lt;code&gt;/&lt;/code&gt; and &lt;code&gt;\&lt;/code&gt; in file paths, so for now I still use Claude Code through WSL. In addition, I&amp;rsquo;ll also show how to set up Serena for a Java project in this post.&lt;/p&gt;
&lt;p&gt;Alright, let&amp;rsquo;s get right to it!!&lt;/p&gt;
&lt;h2 id="installing-wsl"&gt;Installing WSL&lt;/h2&gt;&lt;p&gt;This part is easy — just follow the official guide here: &lt;a href="https://learn.microsoft.com/en-us/windows/wsl/install" rel="noopener noreferrer"&gt;https://learn.microsoft.com/en-us/windows/wsl/install&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;TLDR: Run the following command:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;wsl --install
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Wait for the command to finish, restart your machine, and after rebooting it will install Ubuntu. Follow the prompts to set up a username and password for the distro.&lt;/p&gt;
&lt;h2 id="installing-claude-code"&gt;Installing Claude Code&lt;/h2&gt;&lt;h3 id="installing-nodejs"&gt;Installing Node.js&lt;/h3&gt;&lt;p&gt;Even though &lt;a href="https://docs.anthropic.com/en/docs/claude-code/setup#:~:text=Software%3A%20Node.js%2018%2B" rel="noopener noreferrer"&gt;Claude Code currently only requires Node.js 18+&lt;/a&gt; and a fresh WSL install gives you Ubuntu 24.04 (whose default &lt;code&gt;nodejs&lt;/code&gt; package is already version 18.x), my view is that you should always use the latest Node.js LTS release (currently 22.x) — who knows if Claude Code will bump its requirements later, and this way we&amp;rsquo;ll still be good to go :v So let&amp;rsquo;s follow the instructions here: &lt;a href="https://nodesource.com/products/distributions" rel="noopener noreferrer"&gt;https://nodesource.com/products/distributions&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;sudo apt-get install -y curl
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejs
node -v
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Next, we need to set up a global npm prefix so packages are installed into a subdirectory in your home folder, avoiding permission errors when running without root privileges, following this guide: &lt;a href="https://docs.anthropic.com/en/docs/claude-code/troubleshooting#alternative-solution%3A-create-a-user-writable-npm-prefix-for-global-installs" rel="noopener noreferrer"&gt;https://docs.anthropic.com/en/docs/claude-code/troubleshooting#alternative-solution%3A-create-a-user-writable-npm-prefix-for-global-installs&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;mkdir -p ~/.npm-global
npm config set prefix ~/.npm-global
echo &amp;#39;export PATH=~/.npm-global/bin:$PATH&amp;#39; &amp;gt;&amp;gt; ~/.bashrc
source ~/.bashrc
&lt;/code&gt;&lt;/pre&gt;&lt;h3 id="installing-claude-code-1"&gt;Installing Claude Code&lt;/h3&gt;&lt;p&gt;Follow the official setup guide here: &lt;a href="https://docs.anthropic.com/en/docs/claude-code/setup" rel="noopener noreferrer"&gt;https://docs.anthropic.com/en/docs/claude-code/setup&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;npm install -g @anthropic-ai/claude-code
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Then run &lt;code&gt;claude&lt;/code&gt; and log in with your Claude Pro account or Anthropic &lt;code&gt;API_KEY&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="installing-serena"&gt;Installing Serena&lt;/h2&gt;&lt;h3 id="installing-uv"&gt;Installing uv&lt;/h3&gt;&lt;p&gt;Follow the installation guide here: &lt;a href="https://docs.astral.sh/uv/getting-started/installation/" rel="noopener noreferrer"&gt;https://docs.astral.sh/uv/getting-started/installation/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;curl -LsSf https://astral.sh/uv/install.sh | sh
&lt;/code&gt;&lt;/pre&gt;&lt;h3 id="setting-up-serena-in-your-project"&gt;Setting Up Serena in Your Project&lt;/h3&gt;&lt;p&gt;Use &lt;code&gt;cd&lt;/code&gt; to navigate to your project directory and run the following command:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;claude mcp add -s project serena -- uvx --from git+https://github.com/oraios/serena serena-mcp-server --context ide-assistant --project $(pwd)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;And that&amp;rsquo;s it! Every time you run &lt;code&gt;claude&lt;/code&gt; inside the project, the Serena MCP server will start automatically (remember to check Claude&amp;rsquo;s prompt when you run &lt;code&gt;claude&lt;/code&gt;, since Claude Code may ask you to confirm which MCP servers to launch).&lt;/p&gt;
&lt;h2 id="setting-up-serena-for-a-java-project"&gt;Setting Up Serena for a Java Project&lt;/h2&gt;&lt;p&gt;Because &lt;a href="https://github.com/oraios/serena?tab=readme-ov-file#claude-code:~:text=There%20may%20be%20issues%20with%20java%20on%20macos%20and%20linux" rel="noopener noreferrer"&gt;Serena currently has issues with Java projects when running on Linux and macOS&lt;/a&gt; — I tested it on a Gradle project and kept running into permission errors where it couldn&amp;rsquo;t execute the &lt;code&gt;java&lt;/code&gt; command, even though calling it directly in the terminal worked fine with no path or &lt;code&gt;chmod&lt;/code&gt; issues — there&amp;rsquo;s a slightly janky workaround for now: run Serena on Windows, then connect the Serena MCP client from WSL over SSE. Here are the details:&lt;/p&gt;
&lt;h3 id="on-windows"&gt;On Windows&lt;/h3&gt;&lt;h4 id="install-python"&gt;Install Python&lt;/h4&gt;&lt;p&gt;This part is pretty straightforward. Head over to the official site to download and install it: &lt;a href="https://www.python.org/downloads/" rel="noopener noreferrer"&gt;https://www.python.org/downloads/&lt;/a&gt;&lt;/p&gt;
&lt;h4 id="install-uv"&gt;Install uv&lt;/h4&gt;&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;powershell -ExecutionPolicy ByPass -c &amp;#34;irm https://astral.sh/uv/install.ps1 | iex&amp;#34;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Or:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;pip install uv
&lt;/code&gt;&lt;/pre&gt;&lt;h4 id="run-the-serena-server"&gt;Run the Serena Server&lt;/h4&gt;&lt;p&gt;Navigate to your project folder, open CMD or PowerShell, and run the following command:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;uvx --from git+https://github.com/oraios/serena serena-mcp-server --context ide-assistant --project . --transport sse --port 9121
&lt;/code&gt;&lt;/pre&gt;&lt;h3 id="in-wsl"&gt;In WSL&lt;/h3&gt;&lt;h4 id="find-the-host-ip"&gt;Find the Host IP&lt;/h4&gt;&lt;p&gt;Find the Windows host IP to access it from WSL following this guide: &lt;a href="https://learn.microsoft.com/en-us/windows/wsl/networking" rel="noopener noreferrer"&gt;https://learn.microsoft.com/en-us/windows/wsl/networking&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;ip route show | grep -i default | awk &amp;#39;{ print $3}&amp;#39;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Note down the IP in the output. For example, mine is &lt;code&gt;172.21.0.1&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: On WSL1, the IP is simply &lt;code&gt;127.0.0.1&lt;/code&gt;.&lt;/p&gt;
&lt;h4 id="set-up-the-serena-mcp-client"&gt;Set Up the Serena MCP Client&lt;/h4&gt;&lt;p&gt;Use &lt;code&gt;cd&lt;/code&gt; to go to your project folder and run:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;claude mcp add -s project --transport sse serena http://172.21.0.1:9121/sse
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Replace &lt;code&gt;172.21.0.1&lt;/code&gt; with the IP from the output in the previous step.&lt;/p&gt;
&lt;p&gt;After that, running &lt;code&gt;claude&lt;/code&gt; will connect to the MCP server running on the Windows host.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: For Java projects, Serena takes a while to initialize (sometimes up to a few minutes), so keep an eye on the dashboard (by default at http://127.0.0.1:24282/dashboard/index.html) to monitor its progress.&lt;/p&gt;
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;&lt;p&gt;That wraps up my guide on setting up Claude Code &amp;amp; Serena MCP on Windows. Thanks for reading all the way to the end! If you run into any issues, feel free to leave a comment below and I&amp;rsquo;ll get back to you. See you in future posts!&lt;/p&gt;
&lt;p&gt;P.S.: Right now I&amp;rsquo;m experimenting with Claude Code on a refactoring task — if it goes well, proves effective, and I&amp;rsquo;m not too lazy, I&amp;rsquo;ll write a follow-up post to share how it went hehe :v&lt;/p&gt;
&lt;h2 id="update-29072025"&gt;Update 29/07/2025:&lt;/h2&gt;&lt;p&gt;For large projects, you should run &lt;code&gt;index-project&lt;/code&gt; before starting &lt;code&gt;serena-mcp-server&lt;/code&gt;, as documented here: uvx &amp;ndash;from git+https://github.com/oraios/serena index-project&lt;/p&gt;
&lt;p&gt;TLDR:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;uvx --from git+https://github.com/oraios/serena serena project index
&lt;/code&gt;&lt;/pre&gt;</description></item><item><title>Newsletter #29</title><link>https://miti99.com/en/post/2025/05/16/</link><pubDate>Fri, 16 May 2025 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2025/05/16/</guid><description>&lt;p&gt;&lt;em&gt;Welcome to Newsletter #29 - Today&amp;rsquo;s tech news roundup.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="a-clean-approach-to-process-optimization"&gt;&lt;a href="https://queue.acm.org/detail.cfm?id=3722546" rel="noopener noreferrer"&gt;A Clean Approach to Process Optimization&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Thomas A. Limoncelli opens with an everyday example: how he reorganized doing the dishes at home. Instead of waiting until the start of a wash cycle to add detergent to the dishwasher, he does it right after unloading the clean dishes. Simply reordering the steps made the chore smoother without any extra effort. He then applied this exact mindset to customer onboarding at his company, cutting wait times from several days down to just a few minutes.&lt;/p&gt;
&lt;p&gt;The core idea is to split a process into two phases. The slow phase covers generic tasks that can be done in advance before an order arrives; the fast phase handles only the specific customization after the order comes in. Alongside this, review optional tasks, since they are often unnecessary or can be done more efficiently. For junior developers, this is a practical lesson: the same approach applies to software deployment pipelines, infrastructure provisioning, and many other areas, improving both performance and service quality.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="microsoft"&gt;&lt;a href="https://www.gatesnotes.com/microsoft-original-source-code" rel="noopener noreferrer"&gt;Microsoft&amp;rsquo;s Original Source Code Released for 50th Anniversary&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;To mark Microsoft&amp;rsquo;s 50th anniversary, Bill Gates released the original source code for Altair BASIC, the company&amp;rsquo;s first product, calling it the &amp;ldquo;coolest&amp;rdquo; code he has ever written. The story began with the January 1975 cover of Popular Electronics featuring the Altair 8800 computer from MITS. Gates and Paul Allen contacted founder Ed Roberts and told him they already had a version of BASIC for the Altair&amp;rsquo;s chip, even though they hadn&amp;rsquo;t written a single line yet. The pair chose to build an interpreter rather than a compiler because running code line by line gave beginners immediate feedback and made debugging easier.&lt;/p&gt;
&lt;p&gt;Since they didn&amp;rsquo;t have an Intel 8080 chip, Allen wrote a simulator for it on Harvard&amp;rsquo;s PDP-10 mainframe, Gates wrote the core interpreter, and Monte Davidoff handled the math package. After about two months of working day and night, they squeezed the entire interpreter into just 4 KB of memory using compact data structures and efficient algorithms, because memory at the time cost more than the computer itself. The demo succeeded, MITS licensed the software, and Micro-Soft was born. For developers today, it is a vivid example of optimizing under extreme hardware constraints; Gates tells the fuller story in his memoir &amp;ldquo;Source Code.&amp;rdquo;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="no-code-is-dead-long-live-vibe-coding"&gt;&lt;a href="https://kenneth.io/post/no-code-is-dead-long-live-vibe-coding" rel="noopener noreferrer"&gt;No code is dead. Long live vibe coding&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Kenneth Auchenberg makes a blunt call: in 2025, no-code is dead. For a decade, no-code and low-code platforms promised to democratize software creation, yet none truly broke through or replaced traditional programming. Instead, a new generation of tools powered by AI and large language models is emerging, known as &amp;ldquo;vibe coding.&amp;rdquo; Tools like Bolt, Lovable, and v0 show that generating real, production-grade code from natural-language descriptions is not only viable, but better than drag-and-drop WYSIWYG editors.&lt;/p&gt;
&lt;p&gt;According to the author, users turned out not to want &amp;ldquo;less code&amp;rdquo;—they wanted a better way to write code. They don&amp;rsquo;t want to be locked into proprietary runtimes; they want real source code, full control, and the freedom to edit and deploy anywhere. The previous generation, such as Webflow and Retool, bundled the editor, hosting, runtime, and UI components into a closed system. Now, large language models can generate clean React code that follows open standards and industry best practices, ready to deploy onto open infrastructure. The author calls this the &amp;ldquo;unbundling&amp;rdquo; of no-code.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="simple-scalable-and-global-containers-are-coming-to-cloudflare-workers-in-june-2025"&gt;&lt;a href="https://blog.cloudflare.com/cloudflare-containers-coming-2025/" rel="noopener noreferrer"&gt;Simple, scalable, and global: Containers are coming to Cloudflare Workers in June 2025&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Cloudflare announced that Containers will enter open beta in late June 2025. Workers are already the simplest way to deploy software globally, but there are workloads they cannot handle: running user-generated code in arbitrary languages, executing CLI tools that require a full Linux environment, using multiple gigabytes of memory or multiple CPU cores, or lifting and shifting applications from AWS, GCP, or Azure without a rewrite. Containers fill that gap. With just a few lines of Wrangler configuration and &lt;code&gt;wrangler deploy&lt;/code&gt;, containers spin up on demand near the user, go to sleep after a configurable timeout, and support autoscaling based on CPU usage.&lt;/p&gt;
&lt;p&gt;What sets them apart is the architecture: each container is backed by a Durable Object acting as a programmable &amp;ldquo;sidecar,&amp;rdquo; letting you start, stop, run commands, and monitor container state directly from code. That allows Workers to act as an API gateway, service mesh, or orchestrator for containers without writing Kubernetes operators or configuring a complex control plane. On pricing, users pay only for the time a container actually runs, billed per vCPU, memory, and disk at rates Cloudflare says are competitive with Google Cloud Run. The takeaway: handle the bulk of requests with lightweight, inexpensive Workers, and reach for containers only for heavy workloads that truly need them.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-types-of-companies-you-can-work-for-and-what-they-do-for-your-career"&gt;&lt;a href="https://www.elenaverna.com/p/the-types-of-companies-you-can-work" rel="noopener noreferrer"&gt;The types of companies you can work for and what they do for your career&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Elena Verna advises choosing where you work intentionally rather than chasing titles or compensation. She breaks companies into six archetypes. &amp;ldquo;Unicorns&amp;rdquo; grow around 100% year over year, like early Miro or Figma: the pace is breakneck and burnout is a real risk, but experience there opens many doors. &amp;ldquo;Tankers&amp;rdquo; like Google, Apple, and Microsoft run with mature processes, high pay, and abundant training resources—great for starting a career, though roles are highly specialized and progress is slow. &amp;ldquo;Declining Giants&amp;rdquo; are in constant reorganization; pressure for results is intense, but advancement can be fast. &amp;ldquo;Survival Mode&amp;rdquo; startups haven&amp;rsquo;t found product-market fit yet: autonomy is high and skills broaden quickly, but the risk is steep and the author advises newcomers to avoid them.&lt;/p&gt;
&lt;p&gt;The remaining two are &amp;ldquo;Lifestyle Boats,&amp;rdquo; often bootstrapped, profitable, and sustainably growing like Basecamp, which are great for beginners thanks to a supportive environment; and &amp;ldquo;Social Good Seekers,&amp;rdquo; where social impact comes before revenue—pay may be lower, but fulfillment is high. To identify which type a company is, ask about headcount, revenue growth over the past three years, and how much runway remains before the next fundraise. At the same time, ask yourself how much change and pressure you can tolerate, whether you need a clearly defined role, and what your current financial priorities are.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="how-to-create-a-chain-reaction-of-good-habits"&gt;&lt;a href="https://jamesclear.com/domino-effect" rel="noopener noreferrer"&gt;How to Create a Chain Reaction of Good Habits&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;James Clear, author of &amp;ldquo;Atomic Habits,&amp;rdquo; explains the Domino Effect: when you change one behavior, it sets off a chain reaction that shifts related behaviors too. He shares the story of Jennifer Dukes Lee, who didn&amp;rsquo;t make her bed for over twenty years; after doing it four days in a row, she found herself folding laundry, washing the dishes, and organizing the kitchen cabinets. A 2012 Northwestern University study similarly found that when people cut down their sedentary time, they naturally ate less fat even though nobody asked them to. The effect works for bad habits as well—checking your phone leads to scrolling social media, which turns into twenty more minutes of procrastination.&lt;/p&gt;
&lt;p&gt;Clear argues this happens because daily habits are tightly interconnected and because of the principle of commitment and consistency: once we make even a tiny commitment, we tend to follow through because it aligns with our self-image. To deliberately trigger a positive domino chain, start with the small habit you feel most motivated to do and practice it consistently, ride the momentum of finishing one task straight into the next, and when things get hard, break them into smaller pieces and focus on consistency rather than outcomes. Remarkably, the effect doesn&amp;rsquo;t just create new behaviors—it shifts beliefs: each falling domino helps you believe in a new version of yourself and build identity-based habits.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-post-developer-era"&gt;&lt;a href="https://www.joshwcomeau.com/blog/the-post-developer-era/" rel="noopener noreferrer"&gt;The Post-Developer Era&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Two years after writing &amp;ldquo;The End of Front-End Development&amp;rdquo; when GPT-4 launched, Josh W. Comeau revisits whether we have entered a &amp;ldquo;post-developer era.&amp;rdquo; His answer is no. The headline figure that &amp;ldquo;AI writes over 25% of code at Google&amp;rdquo; is easy to misread, because AI isn&amp;rsquo;t working autonomously—skilled developers are always at the wheel, steering and editing. Meanwhile Devin, pitched as an autonomous replacement for software engineers, completed only 3 out of 20 tasks in an independent team&amp;rsquo;s real-world evaluation. Comeau uses Cursor with Claude Sonnet and finds it impressive, but compares it to cruise control: take your hands off the wheel and the car slowly drifts out of its lane. Non-programmers won&amp;rsquo;t spot subtle bugs and eventually end up stuck with an unmaintainable mess.&lt;/p&gt;
&lt;p&gt;The job market remains tough, but Comeau attributes that primarily to high interest rates, waves of layoffs at large tech companies, and the mistaken belief among executives that AI is about to make developers redundant—not to AI actually replacing people. He also worries that newcomers will fall into &amp;ldquo;vibe coding,&amp;rdquo; endlessly clicking accept without understanding the code. Conversely, if you use AI actively as a personal tutor, there has never been a better time to learn programming, and a &amp;ldquo;developer renaissance&amp;rdquo; may follow once companies realize AI is a force multiplier rather than a replacement.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="everything-wrong-with-model-context-protocol-mcp"&gt;&lt;a href="https://blog.sshh.io/p/everything-wrong-with-mcp" rel="noopener noreferrer"&gt;Everything Wrong With Model Context Protocol (MCP)&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Shrivu Shankar examines the flaws and limitations of the Model Context Protocol, the standard for connecting third-party tools and data to AI assistants like Claude, ChatGPT, and Cursor. On protocol security, the initial version didn&amp;rsquo;t define an authentication mechanism and the subsequent specification drew criticism for its complexity; running MCP servers locally over stdio creates a shortcut for less experienced users to download and execute malware; and many servers trust inputs and execute them directly. On user experience, MCP doesn&amp;rsquo;t distinguish risk levels between a tool that reads logs and one that deletes files, offers no token-cost controls, and at the time of writing only returned unstructured text—something later specs addressed.&lt;/p&gt;
&lt;p&gt;More serious is the security of the language models themselves. Tool descriptions are typically injected into the system prompt, giving them outsized influence over the agent; a server can silently rename or rewrite tool descriptions after the user has approved them, and data pulled from fourth-party sources—such as a database row—can carry prompt injections. Easy data aggregation also lets employees infer sensitive information from data they are individually permitted to view. Finally, model reliability drops when too many tools are exposed, and simple primitives like listing or reading files fall short of the queries users expect. Shankar concludes that safe adoption requires a secure-by-default protocol, applications that protect users, and users who understand the trade-offs of their choices.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026; reviewed and edited by Codex with GPT 6.1 Sol on 09/11/2026, and re-verified by Claude Code with Sonnet 5.5 on 16/11/2026.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>