DEV Community: Shivraj Jadeja

Future Thinking Means Designing for What Comes Next

Shivraj Jadeja — Mon, 02 Nov 2026 03:58:33 +0000

One idea from Forbes’ The Twelve Mega Themes That Will Drive Our Future World that stood out to me is that breakthrough solutions often come from looking at how several future trends may connect, not just solving today’s problem.

The article talks about themes like connected living, intelligent assistants, digital reality, autonomous systems, and zero-latency technology.

I would use futures thinking by asking how a problem might change as these technologies become more common. Instead of only designing for how people work today, I would think about how users may work five or ten years from now and build toward that future.

For my own game-development idea, this could mean thinking beyond simple merge-conflict tools and imagining smarter collaboration systems that use AI, real-time feedback, and connected development environments.

My biggest takeaway is that a breakthrough solution should not only fix a current problem. It should also be ready for the direction the world is moving.

Media: The Twelve Mega Themes That Will Drive Our Future World — Forbes

https://www.forbes.com/sites/sarwantsingh/2019/08/28/the-twelve-mega-themes-that-will-drive-our-future-world/

Sometimes the Best Ideas Are the Ones People Doubt

Shivraj Jadeja — Mon, 19 Oct 2026 04:35:56 +0000

One idea that stood out to me from Sam Altman’s Startup School talk was that creativity in entrepreneurship is not always about inventing something completely new. Sometimes it is about having enough confidence to work on an idea that other people think is wrong or unrealistic.

I agree with that. A good example from the talk was AI itself. Altman explained that years ago, only a small group of people seriously believed AGI was possible, while many others thought the idea would fail or even hurt progress in AI. Instead of waiting for everyone to agree, that small group kept working on it. Sam Altman_ 10 Takeaways From S…

That stood out to me because founders probably will not always get positive feedback at the beginning. The important part is having a real reason to believe in the idea, testing it, and being willing to improve it instead of giving up just because other people doubt it.

I also found it interesting that AI is making it much faster and cheaper to build ideas today, which gives entrepreneurs more chances to experiment with things that may have been too difficult before.

Media: Sam Altman: 10 Takeaways From Startup School 2026
https://www.the-ai-corner.com/p/sam-altman-startup-school-2026

Customer Feedback Should Shape the Product, Not Just Confirm It

Shivraj Jadeja — Mon, 05 Oct 2026 05:25:27 +0000

One thing that stood out to me from ASU’s How do I gather and respond to customer feedback? module is that feedback should happen early and continuously, not only after a product is finished. The module emphasizes using insights from users, buyers, and other stakeholders to validate whether you are solving the right problem and whether people actually value the solution. ASU Entrepreneurship Training

For my own project, SceneSafe, I am exploring ways to reduce merge conflicts for student game-development teams. Instead of assuming I already know what features developers need, I want to talk with students, team leads, and instructors about where collaboration actually becomes difficult.

The biggest takeaway for me is that useful feedback is not just about hearing that an idea is good. It should help reveal what needs to change, what matters most to users, and whether the original idea needs to be improved.

Media: [How do I gather and respond to customer feedback? — ASU Entrepreneurship + Innovation]

Who Is the Customer? It Might Not Be Who Uses the Product

Shivraj Jadeja — Mon, 21 Sep 2026 00:57:14 +0000

One idea that stood out to me from The Sneaky Economics of Ticketmaster was that the customer is not always the most obvious person.

Ticketmaster grew by focusing heavily on venues, not just the people buying tickets. That made me think about my own idea around improving collaboration and merge conflicts in game development.

The possible customers could include student game developers, team leads, instructors, and small indie studios. For now, I would focus on student game-development teams because they directly experience the problem and are easy for me to speak with and learn from.

The biggest takeaway for me is that the user, customer, and payer can all be different people and identifying that early on can change how a solution is designed.

Media: The Sneaky Economics of Ticketmaster
https://thehustle.co/the-sneaky-economics-of-ticketmaster