---
title: "Merlin Wellington (@wizardcraftcode) | Hashnode"
description: "A software engineer for too long to admit and a Professor"
url: "https://hashnode.com/@wizardcraftcode"
---

@wizardcraftcode

# Merlin Wellington

@wizardcraftcode · Joined June 2026

### [What a Proliferation of Clones is Trying to Tell You About Your Rust API](https://wizardcraftcode.hashnode.dev/what-a-proliferation-of-clones-is-trying-to-tell-you-about-your-rust-api?utm_source=hashnode&utm_medium=feed)

When you are fighting the Rust borrow checker, it can easily feel like the compiler is actively getting in your way. You hit a brick wall with error\[E0382\]: use of moved value, and then you remember t

7 min read · [wizardcraftcode.hashnode.dev](https://wizardcraftcode.hashnode.dev/what-a-proliferation-of-clones-is-trying-to-tell-you-about-your-rust-api?utm_source=hashnode&utm_medium=feed)

[Jul 1](https://hashnode.com/posts/what-a-proliferation-of-clones-is-trying-to-tell-you-about-your-rust-api/6a459397f6222102bad22623)

### [Stop Forcing Classes Into Rust: Methods vs. Free Functions](https://wizardcraftcode.hashnode.dev/stop-forcing-classes-into-rust-methods-vs-free-functions?utm_source=hashnode&utm_medium=feed)

If you learned to program in an object-oriented language, you were taught that data and the functions that operate on that data belong together—bound forever inside a class framework. When you come to

5 min read · [wizardcraftcode.hashnode.dev](https://wizardcraftcode.hashnode.dev/stop-forcing-classes-into-rust-methods-vs-free-functions?utm_source=hashnode&utm_medium=feed)

[Jun 26](https://hashnode.com/posts/stop-forcing-classes-into-rust-methods-vs-free-functions/6a3ebcc050c24f43357e8327)

### [Your Getters are Ruining Your Rust Code](https://wizardcraftcode.hashnode.dev/your-getters-are-ruining-your-rust-code?utm_source=hashnode&utm_medium=feed)

Coming to Rust from object-oriented languages like Java, C++, or C# creates a dangerous form of muscle memory. In the object-oriented paradigm, encapsulation dictates a simple rule: hide your struct f

3 min read · [wizardcraftcode.hashnode.dev](https://wizardcraftcode.hashnode.dev/your-getters-are-ruining-your-rust-code?utm_source=hashnode&utm_medium=feed)

[Jun 17](https://hashnode.com/posts/your-getters-are-ruining-your-rust-code/6a321618c46666fa0d1de70f)

### [How to Design Rust Ownership (Without the Guesswork)](https://wizardcraftcode.hashnode.dev/how-to-design-rust-ownership-without-the-guesswork?utm_source=hashnode&utm_medium=feed)

We have all been there. You are writing a fresh Rust feature, you get a flash of inspiration, and you type out fifty lines of complex logic. You hit save, run the compiler, and get hit with a wall of

6 min read · [wizardcraftcode.hashnode.dev](https://wizardcraftcode.hashnode.dev/how-to-design-rust-ownership-without-the-guesswork?utm_source=hashnode&utm_medium=feed)

[Jun 10](https://hashnode.com/posts/how-to-design-rust-ownership-without-the-guesswork/6a28b97cd4fb00bd32056c74)

### [The Sigil Framework: A Visual Reference for Rust Ownership & Borrowing](https://wizardcraftcode.hashnode.dev/the-sigil-framework-a-visual-reference-for-rust-ownership-borrowing?utm_source=hashnode&utm_medium=feed)

If you are coming to Rust from languages with a garbage collector (like Go, Java, or JavaScript) or manual memory management (like C++), Rust's ownership model can feel like an arbitrary set of syntax

4 min read · [wizardcraftcode.hashnode.dev](https://wizardcraftcode.hashnode.dev/the-sigil-framework-a-visual-reference-for-rust-ownership-borrowing?utm_source=hashnode&utm_medium=feed)

[Jun 8](https://hashnode.com/posts/the-sigil-framework-a-visual-reference-for-rust-ownership-borrowing/6a271f051d6a3fb3fee40d5d)
