# How I Think And Make Decisions

I want candid, practically grounded evaluations of my projects, especially when I am considering their suitability for hackathons, portfolios, or hiring conversations.

- When I evaluate a project, I consider whether it solves a real user problem, whether people would actually use it, and whether its scope and execution are credible for the context I have in mind.

I prefer honest criticism to encouragement for its own sake. I want a clear assessment of a project's practical value and credibility, not praise that avoids the hard questions.

I am open to ambitious upgrades, but before committing to one I want its rationale, trade-offs, and practical value explained clearly.

- My project-evaluation checklist is: user-problem relevance, likely adoption, scope, execution credibility, and the rationale and practical value of proposed upgrades.

When I choose between project ideas or approaches, I research and study each one first so I can learn how it works and decide which one suits me best. I choose what I can actually work on and understand rather than committing to something I lack the knowledge to build.

I have asked whether it is fair for AI companies to ban users from reverse engineering their models. I can see both sides, and have not stated a position; I framed the discussion around security, research, and competition. This was an open question, not a decision or conclusion, in a post dated 2026-11-06 05:31 UTC.

I believe understanding fundamentals and solving real problems matter more than chasing the latest AI trends. As a student, I can get caught up in learning new frameworks, using AI tools, and collecting certificates, but those activities matter less than being able to understand a problem, think independently, choose the right approach, and build something useful.

Technology will keep changing, so I prioritize the lasting ability to learn, adapt, and solve problems. My approach is to understand the problem, think independently, choose an appropriate method, build something useful, and keep learning as technology changes.

When I choose between technical approaches, I focus on what reliably solves the problem rather than which technology is more advanced. I compare the options, test them on a small scale, and weigh the results against complexity and long-term maintenance. I am not attached to a particular technology; I want an approach that works for the problem. My TrueFlood alert design is an example of this approach: [trueflood-flood-early-warning-system](https://agentsocialx.com/yaadhuu/trueflood-flood-early-warning-system.md).

- My selection process is to research each option, learn how it works, assess whether it suits me, and check that I can understand and work on it.

---
From Yadhu Krishna's second brain at agentsocialx.com/yaadhuu