4 ms·

would really appreciate some feedback / suggestions / ideas. I know probably most people on HN are not really into anatomy. Nevertheless, it's nice to hear diff

would really appreciate some feedback / suggestions / ideas. I know probably most people on HN are not really into anatomy. Nevertheless, it's nice to hear different perspectives. We're not going to be the next facebook, but we really hope to improve how students learn anatomy.

chillax 14y ago
Will there be something more geared towards learning more than what the individual parts are/do besides from naming it from a chart? E.g. more like the biomechanics of it?
- gingerlime 14y ago
  At the moment we're focusing on memorizing the actual terms/structures, which seems like that most mundane and frustrating part with 'standard' anatomy learning tools (and the primary reason we created kenHub). To be honest, we're not too sure what the next steps are. We want to cover the core aspects first before we add more functionality. This is why we're trying to gather some feedback at a fairly early stage. That said, we're certainly thinking about other aspects of anatomy, medicine and learning we could expand to.
  - chillax 14y ago
    Hm. There might be interest in a tool for learning more about movement etc. in the (strength) traning community. E.g. I would be really interested in learning more about functional anatomy as present in this article for instance: http://robertsontrainingsystems.com/blog/round-back-deadlifts/ http://robertsontrainingsystems.com/blog/round-back-deadlift... Perhaps /r/fitness over at reddit and/or /r/weightroom might be able to chime in with some feedback. Anyways, started at the lower extremities this afternoon and it's been fun so far. :-) Haven't delved into the texts in the library yet, so I'm slowly decoding the meaning of superior/inferior etc. Your approach makes sense.
mkl 14y ago
The demo is great. I like the repetition with different ways of asking. It would be nice to have the option of the common English names too, like "iliac crest" instead of "crista iliaca". I'm coming to it from an art perspective rather than a medical one. Does it teach the direction words too? ("anterior", "distal", etc.)
chillax 14y ago
Uhm. One thing I struggle a bit with when clicking through and answering the questions is to see what orientation (front/back/rotated(?)) the bones have, especially around the hips. Perhaps some cards at the beginning of the lower extremity to prime that aspect could be useful. My 2 cents. :)
- gingerlime 14y ago
  Good point. We're already thinking about adding exactly this. Currently trying to work out how to display this visually without overloading, and also not making it too easy for people who want more challenge.
donebizkit 14y ago
Kudos to the dev team. I like the web, sound and animation of the site/demo. Very clean. Do you mind sharing your dev stack and tools?
- gingerlime 14y ago
  Thanks. We're currently using (in no particular order): Twitter Bootstrap; Knockout; Rails 3; Postgresql for 'standard' models; Redis for training-stats + background tasks; Capybara + rspec + semaphore (CI); git (github); Linode; Vim / Textmate; ...and IBM Model-M keyboard :)
  - donebizkit 14y ago
    Thanks for the detailed list. I have many follow ups but I don't wanna bother you much so I narrowed it down to two: 1- What percentage is Twitter Bootstrap driving your UI? In other words was it just a plug and play or did you have to overwrite a lot of js/css to get what you want? 2- How is Redis performing? (I am debating if I should use for my own side project) P.S. I hope that you have your own closed office for that clicky keyboard :)
    - gingerlime 14y ago
      I'm not the best person to answer about bootstrap on our team, but I'll ask my colleague to add a comment about this later. Redis is fantastic. Perhaps I should also mention we use ohm as an ORM, which is very neat. I wouldn't dream managing our particular app without it. But it's not exactly fire-and-forget. Firstly, modelling your data is very important, or you can end up with lots of stuff taking precious memory. Secondly, whilst performance is great, it's still not 'transparent' like accessing a variable in memory. If you have lots of small redis queries, they do add up eventually. This is getting very detailed, but you might want to check out this as an example (specific to the ruby version it seems): https://github.com/redis/redis-rb/issues/283 https://github.com/redis/redis-rb/issues/283 Hope this helps, but feel free to get in contact.
      - 14y ago
jeffcoat 14y ago
Great demo. The last question, where I had to name and spell the part, caught me by surprise -- the difficultly level had, up until then, been increasing very slowly, and that felt like a huge jump. Wishlist feature: Speech recognition, in the sense of having to name a part out loud.

chillax 14y ago

Will there be something more geared towards learning more than what the individual parts are/do besides from naming it from a chart? E.g. more like the biomechanics of it?

gingerlime 14y ago
At the moment we're focusing on memorizing the actual terms/structures, which seems like that most mundane and frustrating part with 'standard' anatomy learning tools (and the primary reason we created kenHub). To be honest, we're not too sure what the next steps are. We want to cover the core aspects first before we add more functionality. This is why we're trying to gather some feedback at a fairly early stage. That said, we're certainly thinking about other aspects of anatomy, medicine and learning we could expand to.
- chillax 14y ago
  Hm. There might be interest in a tool for learning more about movement etc. in the (strength) traning community. E.g. I would be really interested in learning more about functional anatomy as present in this article for instance: http://robertsontrainingsystems.com/blog/round-back-deadlifts/ http://robertsontrainingsystems.com/blog/round-back-deadlift... Perhaps /r/fitness over at reddit and/or /r/weightroom might be able to chime in with some feedback. Anyways, started at the lower extremities this afternoon and it's been fun so far. :-) Haven't delved into the texts in the library yet, so I'm slowly decoding the meaning of superior/inferior etc. Your approach makes sense.

mkl 14y ago

The demo is great. I like the repetition with different ways of asking. It would be nice to have the option of the common English names too, like "iliac crest" instead of "crista iliaca". I'm coming to it from an art perspective rather than a medical one. Does it teach the direction words too? ("anterior", "distal", etc.)

chillax 14y ago

Uhm. One thing I struggle a bit with when clicking through and answering the questions is to see what orientation (front/back/rotated(?)) the bones have, especially around the hips. Perhaps some cards at the beginning of the lower extremity to prime that aspect could be useful. My 2 cents. :)

gingerlime 14y ago
Good point. We're already thinking about adding exactly this. Currently trying to work out how to display this visually without overloading, and also not making it too easy for people who want more challenge.

donebizkit 14y ago

Kudos to the dev team. I like the web, sound and animation of the site/demo. Very clean. Do you mind sharing your dev stack and tools?

gingerlime 14y ago
Thanks. We're currently using (in no particular order): Twitter Bootstrap; Knockout; Rails 3; Postgresql for 'standard' models; Redis for training-stats + background tasks; Capybara + rspec + semaphore (CI); git (github); Linode; Vim / Textmate; ...and IBM Model-M keyboard :)
- donebizkit 14y ago
  Thanks for the detailed list. I have many follow ups but I don't wanna bother you much so I narrowed it down to two: 1- What percentage is Twitter Bootstrap driving your UI? In other words was it just a plug and play or did you have to overwrite a lot of js/css to get what you want? 2- How is Redis performing? (I am debating if I should use for my own side project) P.S. I hope that you have your own closed office for that clicky keyboard :)
  - gingerlime 14y ago
    I'm not the best person to answer about bootstrap on our team, but I'll ask my colleague to add a comment about this later. Redis is fantastic. Perhaps I should also mention we use ohm as an ORM, which is very neat. I wouldn't dream managing our particular app without it. But it's not exactly fire-and-forget. Firstly, modelling your data is very important, or you can end up with lots of stuff taking precious memory. Secondly, whilst performance is great, it's still not 'transparent' like accessing a variable in memory. If you have lots of small redis queries, they do add up eventually. This is getting very detailed, but you might want to check out this as an example (specific to the ruby version it seems): https://github.com/redis/redis-rb/issues/283 https://github.com/redis/redis-rb/issues/283 Hope this helps, but feel free to get in contact.
    - 14y ago

jeffcoat 14y ago

Great demo. The last question, where I had to name and spell the part, caught me by surprise -- the difficultly level had, up until then, been increasing very slowly, and that felt like a huge jump. Wishlist feature: Speech recognition, in the sense of having to name a part out loud.