About buildlumy

Last updated

On this page

buildlumy makes complicated things simple: tested guides, free tools and step-by-step lessons.

The technology changes. The underlying idea doesn't:

Take something complicated and make it more useful.

I try to test what I write and to say clearly when something is an experiment or an opinion.

What you'll find here

AI

How I use AI tools to learn, build, automate and experiment, and where the technology is genuinely useful versus where the hype gets ahead of reality. It also has guides to finding a job while AI changes how hiring works.

Tech

Fixes for everyday tech problems, worked out from real reports, and a look at tech careers: which roles hire freshers, what they pay and how people got in.

Systems

Lessons you run, not read: SQL from the first SELECT, with every query running live in your browser, one step at a time.

Finance

How everyday money choices really work out, like credit cards, savings and a first salary, with real numbers and the fine print.

Stories & Books

Free tracing worksheets, pages to color and activity guides for children 3 to 8 and the grown-ups who read with them, and the Willowpaw Tales books.

Games

Not only playing them, but understanding the systems, mechanics and design decisions behind them.

Ideas

Anything else that I find genuinely interesting enough to investigate, understand and explain.

Who builds it

I'm Manish Singh, a computer science graduate from Madhya Pradesh, currently building my career around data, AI, automation and software. My journey hasn't been a straight line, and that's probably one of the most important things to know about me.

I grew up in Umaria, Madhya Pradesh, a relatively small town, and later moved to Hyderabad for work. I studied Computer Science and gradually found myself drawn less toward simply writing code and more toward understanding how technology can solve real problems for people and businesses. That curiosity has taken me through data analytics, Python, SQL, Power BI, automation, web development, AI, data engineering and, increasingly, the process of turning ideas into actual products.

I'm someone who tends to think in terms of systems. When I encounter a repetitive process, a messy spreadsheet, information scattered across emails, or a problem that requires people to keep doing the same thing manually, my first instinct is usually:

"Can this be turned into a system?"

That way of thinking led to one of the biggest projects I've worked on: Trinetra. It started from a very practical problem inside a manufacturing environment, where important operational information was spread across large Excel workbooks, trackers, emails and departmental processes. I built a web-based system to bring workflows, reporting, procurement, production, warehouse, quality, maintenance and related activities into a more centralized digital process. Working on it taught me something that tutorials and courses never could: building software is only one part of solving a problem. Understanding the people, processes, constraints and business context is just as important.

I want to build things that remove friction: turning a complicated spreadsheet process into a web application, transforming messy data into something understandable, automating repetitive reporting, or taking an idea that exists only in someone's head and turning it into something people can actually use.

The process before the result

I don't have everything figured out. A lot of technology content is written from the perspective of someone who has already succeeded. What interests me more is the process before the result: the ugly prototype, the feature that nobody uses, the experiment that fails, the business idea that seemed brilliant until real users tried it.

Those are the things I learn the most from, and this website is where I document them.

One principle I'm trying to follow

I don't want to pretend I know the answer before I test the idea. So my approach is becoming:

Learn → Build → Launch → Measure → Understand → Improve → Repeat.

Not every experiment will become a business. Not every project will succeed. Not every technology will live up to the hype. That's okay. The goal is to keep learning fast enough, building enough, and paying enough attention to reality that eventually something compounds.

— Manish Singh