About

I'm Unwana-Emmanuel Obot, and I look after AmelaStock.

I started Platform Notes mostly because I wanted somewhere to write about the things I'm actually building and the problems I run into while building them.

A lot of that work sits somewhere between software engineering, ERPNext, AI, automation and keeping a real platform running. Sometimes I start with what looks like a fairly simple problem and end up somewhere completely different. The Product Intake workflow is a good example of that.

That's mostly what I want to write about here.

I'll talk about what I was trying to do, the first approach I took, what worked, what didn't, and how the system changed as I understood the problem better. Where it makes sense I'll include screenshots, code, architecture and the technical decisions behind it, but I don't want this to turn into documentation for documentation's sake.

What you'll find here

  • Things I've built or am currently building.
  • ERPNext and AmelaStock workflows.
  • AI-assisted development and experiments with agents.
  • Automation and platform work.
  • Technical decisions, including the ones that didn't work particularly well the first time.
  • The operational side of getting something from “this seems like a good idea” to something people can actually use.

Some articles will be fairly technical. Others will probably be more about the strange sequence of decisions that led to the technical solution in the first place.

A note about AI

I use AI quite a lot in my engineering work. I use it for research, exploring ideas, writing and reviewing code, creating images and, increasingly, for parts of the systems I'm building.

I may also use AI while working on an article, particularly for research, organising material or helping me work through a draft.

The experiences, decisions and opinions in the articles are mine, and I review everything before I publish it.

These posts are personal professional reflections. They aren't official AmelaStock or ERPNext documentation, and they shouldn't be treated as professional advice.

You can also find me on LinkedIn.

Comments

Post a Comment

Popular posts from this blog

I Had 11,000 Messy Legacy Inventory Rows. Making Sense of Them Became an ERPNext Workflow

Image
I Had 11,000 Messy Legacy Inventory Rows. Making Sense of Them Became an ERPNext Workflow A few months ago, I started trying to make sense of years of messy inventory data so we could recreate the useful parts of it properly in ERPNext. I was new to ERPNext, so I spent a lot of time in the documentation first. I started with the Item master , because for a medium-sized business such as ours that is really the backbone of the inventory side of the system. I needed to understand item codes, item names, descriptions, barcodes, buying and selling prices, and how those records fed into the rest of ERPNext. Because I also decided to add the Webshop app, I had the Website Item fields to think about too: website names, short descriptions, images and the other catalogue information. Not all of that went in first time round, but I understood enough to get started. Our business had used other inventory and POS systems before ERPNext. We had moved between a couple of providers over the yea...
Read more