Years and years of “mobile first” getting getting traction only to be forgotten in a heartbeat when it’s finally easy to do “real cool stuff” on desktop.
I actually have been in contact with Ashe just appreciating the idea of her work, and that was definitely a part of what inspired me, I just wanted to make extensive work that focused rather on a specific part of the body. Thank you for pointing it out.
Not at all, im an engineer, or I finish my final year of my masters in AI and Machine learning in like 8 months. This is actually abit out of my scope even when it comes to engineering, working with three.js haha.
I just wanted to make something new, I have a similar project on my github called pc anatomy that blew up, basically dissecting an entire computer to the smallest cuda core.
I got to many messages from teachers wanting to use it to teacher their students, and the thought of something like that actually being useful got me excited. So I decided to make another open source but this time for students in the medical field, I felt like doing the entire anatomy of the body is too ambitious to start so I decided to start with the oral field.
I hope that answers your question, it all just kinda boils down to me wanting to help people and make something free and open-source, sort of to start a community around it.
The implementation that is currently visible in the GitHub commit history was done over about 3 days, yes. But that does not include the research, planning and architecture work that happened before I started committing the implementation.
I spent roughly 2 weeks researching the domain, figuring out the structure of the tool, planning the architecture and deciding how the different anatomical layers and interactions should work before the repo history you are looking at began.
That's great. It reminds me of Elsevier's full-body anatomy tool which is very cool but requires a license of like $60 dollars per year (probably targeted at doctors and medical students). I hope someone can replicate the essence of it and make such a tool available for free.
Just a clarification for the people hating on clankers, I want to know what you expect from todays devs? do you genuinely think that people should manually handcode everything for it to hold any significant value?
I just don't understand the point of view where - "a clanker made it therefore it's trash", it's always the same people they lurk on reddit aswell.
Even in the case of putting something together manually, you are competing against people using AI and you will never match their production level or speed.
I mean the people who hold the highest priority say in this are the dentists/dental students, and so far all the feedback from those have been nothing but positive?
I wonder when Claude will stop doing "pale but not white background with a serif heading"
Also - not sure what happened, but clicking around, I got the entire model to disappear entirely and the reset button did not bring it back. A refresh did work.
One UX suggestion: The "Dissect Anatomy" area should instead have a toggle switch for the "laid out" option (And that could disable the assembled/in position ), as that seems to be a binary control, where the "assembled" and "in position" options are actually modified by the vertical slider.
Too bad the AI that this is built with isn't bright enough to know how many permanent teeth there are in a human's jaw. 38 seems high. Why should anyone trust it to know how all the other things are connected?
I hate to think that there are generations of engineers, programmers, etc who will not be qualified to determine whether the AI tools that they build and deploy can answer any of the questions that one would be inclined to ask or solve any of the problems that might need solutions.
Get an education. Learn to think for yourself so that you can recognize when some slop like this hits the screen.
Humans have 32 permanent teeth, and that is exactly what Dental Scope models. It is even pointed at the first screen.
If you found somewhere in the UI that says 38, point it out and I’ll fix it. That is useful feedback.
The rest is just a long rant based on the assumption that using AI means I neither understand nor review what I build. You know nothing about my education, my engineering background, or how this project was developed.
Sounds like an old grump that is falling behind to AI.
You pointed your clanker of choice to a dataset (or more realistically, asked it to find an appropriate dataset), and told it to build a interactive 3d model. You learned nothing from this project because no mental effort was spent beyond listing out features for your clanker, and some manual testing.
You continued an argument from somewhere else in a thread about a new way to use tech to visualize anatomy. You took English words you did not develop and typed them into an input device you use but did not invent.
I personally couldn’t be happier about it.
There was a live deploy, but it is currently unavailable: https://human-atlas-seven.vercel.app/
[1]: https://github.com/ashemag/human-atlas
[2]: https://x.com/ashebytes/status/2096221988763173186?lang=ar-x...
Live: https://dental-scope.com/
GitHub: https://github.com/Yoosseph/dental-scope
Feedback and contributions are welcome
I just wanted to make something new, I have a similar project on my github called pc anatomy that blew up, basically dissecting an entire computer to the smallest cuda core.
I got to many messages from teachers wanting to use it to teacher their students, and the thought of something like that actually being useful got me excited. So I decided to make another open source but this time for students in the medical field, I felt like doing the entire anatomy of the body is too ambitious to start so I decided to start with the oral field.
I hope that answers your question, it all just kinda boils down to me wanting to help people and make something free and open-source, sort of to start a community around it.
I spent roughly 2 weeks researching the domain, figuring out the structure of the tool, planning the architecture and deciding how the different anatomical layers and interactions should work before the repo history you are looking at began.
This could be a part of Wikipedia.
Zeruxe: in case you are unfamiliar, this means most people can’t see them, only those who are logged in and have showdead enabled.
https://imgur.com/a/ZmsyDWZ
note your comment at the bottom of that image
Not the engineering effort behind it.
It still looks great. And very good for understanding whatever it is my dentist is doing with my teeth.
I just don't understand the point of view where - "a clanker made it therefore it's trash", it's always the same people they lurk on reddit aswell.
Even in the case of putting something together manually, you are competing against people using AI and you will never match their production level or speed.
I mean the people who hold the highest priority say in this are the dentists/dental students, and so far all the feedback from those have been nothing but positive?
Also - not sure what happened, but clicking around, I got the entire model to disappear entirely and the reset button did not bring it back. A refresh did work.
One UX suggestion: The "Dissect Anatomy" area should instead have a toggle switch for the "laid out" option (And that could disable the assembled/in position ), as that seems to be a binary control, where the "assembled" and "in position" options are actually modified by the vertical slider.
Seems neat, for the most part.
Thanks for the feedback about the bug I will look into that.
Also thanks for the suggestion and the compliment :)
I hate to think that there are generations of engineers, programmers, etc who will not be qualified to determine whether the AI tools that they build and deploy can answer any of the questions that one would be inclined to ask or solve any of the problems that might need solutions.
Get an education. Learn to think for yourself so that you can recognize when some slop like this hits the screen.
If you found somewhere in the UI that says 38, point it out and I’ll fix it. That is useful feedback.
The rest is just a long rant based on the assumption that using AI means I neither understand nor review what I build. You know nothing about my education, my engineering background, or how this project was developed.
Sounds like an old grump that is falling behind to AI.
You pointed your clanker of choice to a dataset (or more realistically, asked it to find an appropriate dataset), and told it to build a interactive 3d model. You learned nothing from this project because no mental effort was spent beyond listing out features for your clanker, and some manual testing.
You continued an argument from somewhere else in a thread about a new way to use tech to visualize anatomy. You took English words you did not develop and typed them into an input device you use but did not invent.