← HomeThe person with the questions

Sreekar

I like electronics, small experiments, and finding out how the pieces fit. I write about electronics, code and what I learn while building things.

NOTE
Kindred Hands

What these three months have changed

The Kindred Hands software phase took about three months and was completed by February 2026. I had looked at WordPress and Dokan, continuing costs changed the direction, and I brought open-source alternatives together with guidance. Reaching a working setup gave that phase an ending, but it als

·3 min read
NOTE
Kindred Hands

The website is only part of the work

A daily earning of about Rs350, roughly three days to produce a saree and a selling price of Rs15,000–20,000 are different kinds of numbers. They were part of the concern I was trying to understand through Kindred Hands. Subtracting one from another would not explain the whole route: materials,

·3 min read
NOTE
Kindred Hands

Can someone use these instructions without me beside them?

Part of my Kindred Hands work involved recording defects and feeding checked results back into development. I also use Research support with documentation, while remaining responsible for the decisions and claims I make. Writing something down therefore has a practical purpose: the explanation

·4 min read
NOTE
Kindred Hands

Comparing the same job on both sides

The cost decision in Kindred Hands had a purpose behind it. I wanted to help weavers reach customers more directly without our taking commission, and the initiative was intended as not-for-profit. Continuing costs around the initial WordPress and Dokan route led me to alternatives, which I link

·4 min read
NOTE
Kindred Hands

Putting the project down without losing the question

Kindred Hands sat alongside my studies and sport. Football and volleyball have been important parts of my life, and sport is one way I find balance with academic work. Technical projects also ask for a different kind of attention: a small-looking question can open into several things I need to

·3 min read
NOTE
Kindred Hands

What would convince me that the whole task works?

Bringing the components together gave Kindred Hands a working software setup. Testing also belonged with the work: smoke and regression checks, recording defects and feeding results back into development. Those responsibilities made it important to understand the question behind a result. A pag

·5 min read
NOTE
Kindred Hands

When the cost question changed the route

The continuing costs changed the direction of my Kindred Hands setup. I had looked at WordPress and Dokan, and then began exploring open-source alternatives. The question was no longer only whether a tool could help me get started. It was what choosing that arrangement would mean for the initia

·3 min read
NOTE
Kindred Hands

The work in between the tools

I was responsible for bringing the Kindred Hands software service together, with mentor support. After looking at WordPress and Dokan, the continuing costs led me towards a couple of open-source alternatives. I linked the components with guidance. I was building on existing software, rather tha

·4 min read
NOTE
Kindred Hands

What I bring to a mentor discussion

I was responsible for the Kindred Hands software setup, and I had help from my mentor. I brought the alternative components together with guidance after the continuing costs changed the route. Taking responsibility did not mean doing every part without guidance. It meant keeping track of what I

·3 min read
NOTE
Kindred Hands

The first attempt did not disappear when I changed direction

Changing the route was part of my work on Kindred Hands. I looked at WordPress and Dokan, continuing costs led me towards alternatives, and I brought open-source components together with guidance. The earlier investigation still mattered because the purpose of the initiative had not changed whe

·3 min read
NOTE
Kindred Hands

One change, one question

Testing and defect reporting were part of my Kindred Hands work. That connects this method to something practical: a result needs to help the next development decision, rather than simply make the screen look more encouraging. My engineering approach includes checking ordinary operation, edge c

·3 min read
NOTE
Kindred Hands

What one sample product can tell me

My work on Kindred Hands included smoke and regression checks, recording defects and feeding checked results back into development. Checking belonged with the e-commerce and multi-vendor work, rather than beginning only when the home page looked finished. It asked a different question from whet

·4 min read
NOTE
Kindred Hands

Agreement was not yet participation

I had written a pitch and made a website. When I first explained the Kindred Hands idea to people in the weaving community, the conversations sounded encouraging. They agreed readily, and I expected the next part to follow smoothly. I gave them my contact details and went home. Agreement in the

·3 min read
NOTE
Kindred Hands

The boxes are easy. The arrows are the problem.

The connections were part of my work in Kindred Hands. I was responsible for bringing a couple of open-source tools together with guidance after the first route raised continuing-cost concerns. The e-commerce and multi-vendor responsibilities gave those connections a purpose. Separate useful pi

·4 min read
NOTE
Kindred Hands

The smaller question is usually the better one

Research support was part of bringing the alternative setup together for Kindred Hands. I used that assistance alongside my mentor's support after the continuing costs changed the route. It gave me another way to approach unfamiliar software, but the explanations still had to connect to the ser

·3 min read