
Backend Tech Lead at @Founder_L Developer. Reader. Speaker. Weird. Coding in Laravel. Clouds : Heroku + GCP
Mohali, India
Joined January 2010
- Tweets1.4K
- Following763
- Followers227
- Likes5.5K
Jagdeep Singh / JD retweeted
Only if education could be this interactive ❤️🔥
I've had a looong wish to build something genuinely useful through vibe coding, and I finally did it.
A 3D human anatomy application built with @threejs using GPT 5.6 Sol.
It all started with a single design image that I created using GPT Image 2.0. I then used it to generate every 3D organ image, one by one.
Next, I converted each of those images into 3D models using @tripoai (and no, they didn't sponsor this 😄).
After that, I opened Codex, wrote a master prompt based on the design, and gave it the prompt, the design image, and all the 3D models.
Codex built the first version beautifully, but there was one big problem.
Every single 3D model was nearly 120-150 MB. That obviously wasn't practical for the web and was giving a performance of 16fps.
After a few iterations, Codex optimized each model down to roughly 2–5.5 MB while preserving the visual quality, reducing the total asset size from ~900 MB to just 28.6 MB. And each model loads on demand.
Along the way, Codex also generated those anatomical illustrations showing where each organ sits in the human body, and even created the interactive hotspot markers that explain different parts of every organ. It handled all of that.
The process wasn't exactly one shot, but it also wasn't difficult. You just have to do it step by step.
It genuinely felt like building something that could make learning anatomy much more engaging.
The inspiration came from @DilumSanjaya's 3D animal plant cell project. I remember seeing it and thinking, "I want to build something like this one day."
And I did it :D
Live: anatomy-livid.vercel.app/
Code: github.com/thebuggeddev/anat…
Jagdeep Singh / JD retweeted
🎉 We've been cooking up some pretty exciting things recently for Inertia.js v2.0 — @joetannenbaum has literally rewritten a decent chunk of the core router to accommodate some new features we're adding.
One big goal for v2.0 is to improve the background data reloading and polling story, and I'm so pumped to share what we've come up with 🙌
Jagdeep Singh / JD retweeted
Digging in to inertia a bit
Laravel + inertia is probably the best "single developer" stack on the market right now for general cases
Jagdeep Singh / JD retweeted
📢 Announcing Speaker for #LaravelChd April Chapter.
@jdecode will be talking about Docker
Join this fantastic session at @founderandlightning
Book your tickets: sutli.li/srzcf
@LaraconIN @laravelphp
Jagdeep Singh / JD retweeted
The developer condition:
Waking up with big ambitions, then burning half the day on some random edge-case/tail-chase bug in CI or something incredibly hard to debug 🙈
Jagdeep Singh / JD retweeted
Thank you, Narayan Sharma, for an excellent session.
@laravel @laravelChd
Jagdeep Singh / JD retweeted
🎁 Day 3...
Catalyst v0.1.0 is here! 🥳
Our first fully-componentized, batteries-included application UI kit for React 🤝🏻
tailwindcss.com/blog/introdu…
Jagdeep Singh / JD retweeted
The Laravel team continues to push the scope of what a "framework" can be. They just dropped another first-party, free offering that could be a million-dollar SaaS.
Pulse is basically a full-on, self-hosted APM tool.
pulse.laravel.com/
Jagdeep Singh / JD retweeted
Mobile web dev is usually a pain
UNTILL NOWW
dun dun dun
Check this out. Super easy to wire up your physical iphone with desktop devtools 🍰
Jagdeep Singh / JD retweeted
The @pestphp plugin for PhpStorm is now maintained by JetBrains 💫
We’d like to give a big shout out to its author, @OliverNybroe!
Read the whole story and find out what's coming next in this blog post 👇
blog.jetbrains.com/phpstorm/…
Jagdeep Singh / JD retweeted
Replying to @ThePrimeagen @aarondfrancis
This is now the official "PHP is not dead" face
Jagdeep Singh / JD retweeted
Every week, we ask these three questions to keep us focused, make sure we're working on the right things, and make sure we actually ship.
What are you aiming to get done this week?
Specific, measurable things we want to be able to call done by the end of the week. The wording here matters — "get done" is very different from "work on". It forces you to break things down into smaller problems, and get better at sequencing work in large projects.
Sometimes it's hard to answer this question, and that's when it's most important. Weeks without a plan are the ones where you're most likely to find yourself at the end of the week telling yourself "I felt like I was busy all week but I don't have anything to show for it".
How are your projects going so far this week?
A chance to share your work in progress, talk about interesting problems you've run into so far, and step back to assess whether you're on track to meet your goals. This one really helps us all on the team feel connected to what everyone is working on, and is an awesome way to get exposed to new things and keep learning.
It's also really helpful for leadership just to know how things are going and to be able to provide any helpful direction or suggest ways to cut scope to avoid spinning our wheels.
What did you accomplish this week?
Not what did you work on, what did you get done. A chance to celebrate what we each shipped, compare our progress to what we planned at the beginning of the week, and fine-tune our own expectations of ourselves for next week.
Getting stuff done feels awesome and gives you energy, and this little piece of accountability helps us stay focused on shipping, instead of letting long, murky projects drag out forever without locking in progress at thoughtful milestones.
—
Getting serious about answering these questions every week has made my life 100x better as a leader, and as an individual contributor. Everyone on the team answers these questions (including leadership), and it gives us all so much more confidence in what we're doing.
No more feeling of "lost weeks", and so much clarity about how to get started when cracking open the computer in the morning.
Jagdeep Singh / JD retweeted
Announcing Pest 2:
✓ New powerful architecture plugin
✓ Up to 60% faster on parallel testing
✓ Stay organized with to-dos in your tests
✓ New options like --profile, --retry, --dirty
Plus, we've completely revamped our documentation and website! pestphp.com/docs/announcing-…
Jagdeep Singh / JD retweeted
Wrote docs for the new "Pipeline" facade. We've used the Pipeline internally in Laravel for years, but more end users have recently discovered its usefulness. So, had to document it. 📚
laravel.com/docs/10.x/helper…
Jagdeep Singh / JD retweeted
My family after seeing my swag t-shirts 🤣:-
Mother: "inke paas black ke alwa koi color nahi hota?"
Father: "tumhe kaam karne par bas t-shirt hi milti Hain aisi?"
Grandfather: "Yeh t-shirt ke saath lower nahi dete kya?"
Jagdeep Singh / JD retweeted
Laravel Secrets are shared here #LaraconIN 😳👀
Jagdeep Singh / JD retweeted
So cool for @Caneco to call out these awesome packages at @LaraconIN.


























