Remove hiring status

Author: soareschen

content/blog/2025-07-07-extensible-datatypes-part-1.md

@@ -1063,7 +1063,3 @@ In this first installment, we explored how CGP v0.4.2 empowers Rust developers t
 This approach dramatically simplifies configuration management, promotes code reuse, and opens the door to highly flexible, plugin-style architectures in Rust. Whether you're building minimal test contexts or full-featured production systems, CGP gives you the tools to scale your logic modularly and safely.
 
 In [Part 2 of this series, **Modular Interpreters and Extensible Visitors**](/blog/extensible-datatypes-part-2/), we’ll shift gears to look at **extensible variants**, where CGP tackles the expression problem with a modular visitor pattern. If you've ever wanted to define interpreters, pattern match over generic enums, or evolve your data types without breaking existing logic — you won’t want to miss what’s coming next.
-
-## Hire Me
-
-P.S. Btw, [I am available for hire](/hire)!

content/blog/2025-07-09-extensible-datatypes-part-2.md

@@ -904,8 +904,3 @@ Rather than tying our logic to rigid enums or bloated visitor traits, we’ve be
 This is more than a workaround for the expression problem — it’s a foundational shift in how we think about data structures and operations in Rust. With CGP, you no longer need to trade off between extensibility and type safety. You can add new variants without touching existing code, and build interpreters or transformers that evolve organically with your domain.
 
 In [Part 3 of this series, **Implementing Extensible Records**](/blog/extensible-datatypes-part-3), we will dive into the *underlying* implementation details of **extensible records**, and how the extensible builder pattern is built on top of it. We will cover the concepts of **partial records**, and the use of traits such as `BuildField` and `FinalizeField` to represent *row constraints*.
-
-
-## Hire Me
-
-P.S. Btw, [I am available for hire](/hire)!

content/blog/2025-07-12-extensible-datatypes-part-3.md

@@ -1004,7 +1004,3 @@ If you're still unsure how all of this comes together, a future blog post will w
 ## Next Part
 
 In the final [Part 4 of this series, **Implementing Extensible Variants**](/blog/extensible-datatypes-part-4), we will follow a similar path to explore how CGP implements extensible variants. Keep in mind the concepts we covered for extensible records — you may be surprised to discover just how much of the same logic carries over, despite the differences between records and variants.
-
-## Hire Me
-
-P.S. Btw, [I am available for hire](/hire)!

content/blog/2025-07-30-extensible-datatypes-part-4.md

@@ -1535,7 +1535,3 @@ The design and implementation of extensible data types push the boundaries of wh
 Even if you have not fully absorbed every concept presented, I hope this series has inspired you to begin learning CGP from the fundamentals. It is important to realize that many of the basic CGP patterns may initially seem unnecessary or overengineered, yet they are the foundation that makes advanced patterns like extensible data types and [Hypershell](/blog/hypershell-release/) achievable.
 
 Finally, you do not need to create entirely new language features or DSLs for CGP to prove valuable. In upcoming posts, we will explore more foundational and intermediate CGP patterns that can help you build practical and maintainable Rust applications. Thank you for following this series and for your support of the CGP project. Exciting developments are on the horizon, and I look forward to sharing them with you.
-
-## Hire Me
-
-P.S. Btw, [I am available for hire](/hire)!