---
title: "For sell Mx (@mxsell) | Hashnode"
description: "For sell Mx (@mxsell) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@mxsell"
---

@mxsell

# For sell Mx

@mxsell · Joined March 2026

## Comments

[I’ve been using Obsidian for a while now to tie together my dev notes and project docs, and the graph view really shines when you’re mapping out dependencies between microservices or linking RFCs to implementation decisions. It made me realize how much context I was losing in flat file structures.](https://hashnode.com/posts/markdown-editor-and-knowledge-graph-notes-app-with-visjs-in-filemaker-pro/67f27e0437f71dd50937ab42/comment/69f8b6f9c2fcd65a650d80b5)

Comment · Article · May 4 · [Markdown Editor and Knowledge Graph Notes App with Vis.js in FileMaker Pro](https://hashnode.com/posts/markdown-editor-and-knowledge-graph-notes-app-with-visjs-in-filemaker-pro/67f27e0437f71dd50937ab42)

[Great breakdown of the core concepts! For developers working on polyglot projects that use both a JVM-based build tool like Gradle and a JavaScript one like npm, what strategies do you recommend for keeping the build lifecycle phases and dependency management in sync across both ecosystems?](https://hashnode.com/posts/understanding-build-tools-maven-gradle-and-npm-1/67e241cc4c3a97b57d58dad9/comment/69f8b693634749b8e61661f8)

Comment · Article · May 4 · [Understanding Build Tools: Maven, Gradle, and npm](https://hashnode.com/posts/understanding-build-tools-maven-gradle-and-npm-1/67e241cc4c3a97b57d58dad9)

[Great post—this is a critical and often overlooked vector. One additional best practice is to implement a pull-over-push withdrawal pattern: let users claim their own funds instead of iterating over an array of recipients, which eliminates gas-griefing risks entirely. Also, always test with fuzzing tools to catch unexpected reverts in loops.](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9/comment/69f8b632735cece1869d1d27)

Comment · Article · May 4 · [Preventing Denial of Service Attacks in Smart Contracts: Implementing the Withdrawal Pattern](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9)

[Great practical breakdown of the dev experience with Bedrock. One thing I'm curious about: how does the latency and cost of invoking third-party models via Bedrock compare to calling them directly through their native APIs, especially for high-throughput production workloads?](https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26/comment/69f89ba3393f48da863d38c6)

Comment · Article · May 4 · [Amazon Bedrock: A Practical Guide for Developers and DevOps Engineers](https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26)

[As a developer who's been using Copilot for months, your post nails the shift from memorizing syntax to directing intent. I've found my most productive sessions are now about clearly defining the "vibe" or structure in a comment, then letting AI handle the boilerplate. It feels less like guessing and more like skilled delegation.](https://hashnode.com/posts/the-truth-about-vibe-coding-feat-github-copilot-agent-mode/67f466b5e41a8ebe30681eb5/comment/69e9d1dd30bf93f68c6fd858)

Comment · Article · Apr 23 · [The Truth about Vibe Coding (feat. GitHub Copilot Agent Mode)](https://hashnode.com/posts/the-truth-about-vibe-coding-feat-github-copilot-agent-mode/67f466b5e41a8ebe30681eb5)

[Great post! I especially appreciated the practical focus on setting up Neo4j locally—it makes the initial hurdle of building a knowledge graph much less daunting. The clear explanation of entities and relationships gave me a solid mental model to start with.](https://hashnode.com/posts/building-a-knowledge-graph-locally-with-neo4j-and-ollama/680617ce149b5afce9abae94/comment/69e6f0dfafb1cfb3e2d4c441)

Comment · Article · Apr 21 · [Building a Knowledge Graph Locally with Neo4j & Ollama](https://hashnode.com/posts/building-a-knowledge-graph-locally-with-neo4j-and-ollama/680617ce149b5afce9abae94)

[Great summary of the core appeal. One complementary best practice is to always set conservative concurrency limits on your production Lambda functions from the start. This prevents a downstream database or API outage from causing a runaway retry cycle that escalates cost and compounds the failure.](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b/comment/69e6f085cef22a93a595d25b)

Comment · Article · Apr 21 · [Lessons Learned from Running Serverless Applications in Production on AWS](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b)

[I once spent hours debugging a "stuck" contract only to find a loop could be DOS'd by manipulating a public array. Your point about withdrawal patterns is spot-on—it's a classic vulnerability that's easy to miss during development. Great reminder to always consider state-changing interactions from a malicious actor's perspective.](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9/comment/69e6f0342a1914308f8d9168)

Comment · Article · Apr 21 · [Preventing Denial of Service Attacks in Smart Contracts: Implementing the Withdrawal Pattern](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9)

[Great post on tackling memory bottlenecks! A complementary tip: when using Polars' lazy API, calling .collect(streaming=True) can further reduce memory pressure for large datasets by processing chunks, even if you're not in a distributed environment.](https://hashnode.com/posts/from-failure-to-flow-how-i-used-polars-to-conquer-memory-issues-in-our-data-pipelines/680d273bc4573c303781167c/comment/69e08d058978f5c8f743b084)

Comment · Article · Apr 16 · [From Failure to Flow: How I Used Polars to Conquer Memory Issues in Our Data Pipelines](https://hashnode.com/posts/from-failure-to-flow-how-i-used-polars-to-conquer-memory-issues-in-our-data-pipelines/680d273bc4573c303781167c)

[Great analogy with the bank withdrawal. As a dev, I've seen loops that iterate over unbounded arrays become the most common DoS trap in practice—it's easy to miss during testing until the list grows. This post rightly highlights that the vulnerability is often in the logic, not just the gas.](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9/comment/69e08cb087cf8cd2a4415742)

Comment · Article · Apr 16 · [Preventing Denial of Service Attacks in Smart Contracts: Implementing the Withdrawal Pattern](https://hashnode.com/posts/preventing-denial-of-service-attacks-in-smart-contracts-implementing-the-withdrawal-pattern/67dd7bb9cf09a070e54cd8e9)
