---
title: "Esanju Babatunde (@Teesofttech) | Hashnode"
description: "Esanju Babatunde (@Teesofttech) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@Teesofttech"
---

@Teesofttech

# Esanju Babatunde

@Teesofttech · Joined July 2025

### [A Fraud Score Is Not Permission to Move Money](https://tundehub.dev/a-fraud-score-is-not-permission-to-move-money?utm_source=hashnode&utm_medium=feed)

Fraud detection is an important part of financial engineering. But it becomes dangerous when we ask it to answer questions that belong elsewhere. A transaction receiving a low risk score does not esta

5 min read · [tundehub.dev](https://tundehub.dev/a-fraud-score-is-not-permission-to-move-money?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/a-fraud-score-is-not-permission-to-move-money/6afcdf8aa4913dab084a7af5)

### [A Status Column Is Not an Audit Trail: Designing for Accountability Across Regulated Products](https://tundehub.dev/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products?utm_source=hashnode&utm_medium=feed)

Working across financial, insurance, and legal products makes one architectural question difficult to ignore: Can the system explain how it reached its current state? A feature can work perfectly from

4 min read · [tundehub.dev](https://tundehub.dev/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products?utm_source=hashnode&utm_medium=feed)

[6](https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4) [3d ago](https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4)

### [Before You Cache That .NET Endpoint, Inspect the Query](https://tundehub.dev/before-you-cache-that-net-endpoint-inspect-the-query?utm_source=hashnode&utm_medium=feed)

A slow endpoint can make Redis look like the obvious next step. Put the result in a cache. Avoid another database call. Return the response faster. That can be a sensible approach. But before introduc

5 min read · [tundehub.dev](https://tundehub.dev/before-you-cache-that-net-endpoint-inspect-the-query?utm_source=hashnode&utm_medium=feed)

[3](https://hashnode.com/posts/before-you-cache-that-net-endpoint-inspect-the-query/6af3a9bf06e0902fc89b060d) [Nov 10](https://hashnode.com/posts/before-you-cache-that-net-endpoint-inspect-the-query/6af3a9bf06e0902fc89b060d)

### [Your C# Nullable Warning Might Be a Design Question](https://tundehub.dev/your-c-nullable-warning-might-be-a-design-question?utm_source=hashnode&utm_medium=feed)

A green build can hide an unanswered question. Consider this code: var customer = await repository.FindByIdAsync(customerId); await emailService.SendAsync( customer!.Email, "Your application

7 min read · [tundehub.dev](https://tundehub.dev/your-c-nullable-warning-might-be-a-design-question?utm_source=hashnode&utm_medium=feed)

[Nov 8](https://hashnode.com/posts/your-c-nullable-warning-might-be-a-design-question/6af0b10bb6461ed6de6bf2be)

### [Before You Split Your .NET Application Into Microservices, Define the Problem](https://tundehub.dev/before-you-split-your-net-application-into-microservices-define-the-problem?utm_source=hashnode&utm_medium=feed)

Microservices are attractive for good reasons. They can let teams deploy business capabilities independently and scale individual services according to demand. But those benefits come with responsibil

4 min read · [tundehub.dev](https://tundehub.dev/before-you-split-your-net-application-into-microservices-define-the-problem?utm_source=hashnode&utm_medium=feed)

[Nov 5](https://hashnode.com/posts/before-you-split-your-net-application-into-microservices-define-the-problem/6aecbb3ff87f882466f2997a)
