11–20 of 23 posts
Just this morning I was griping to a friend about my frustration at the lack of modern / affordable / convenient / dynamic tools for learning Anatomy & Physiology as it's a course my SO is currently taking.
This looks really, really good. A potential godsend.
Earlier quoted context omitted.
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?
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. Tha…
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.
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.
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.
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.
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?
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 :)
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.
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. :)
Earlier quoted context omitted.
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?
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 :)
P.S. I hope that you have your own closed office for that clicky keyboard :)
Earlier quoted context omitted.
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 :)
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…
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
Hope this helps, but feel free to get in contact.
Earlier quoted context omitted.
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 :)
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…
We used bootstrap as a starting point and - to be honest - at that point it looked like this. But over time we changed and added more and more of our own code. But I would say it is quite marginal still if you look at what bootstrap provides.
I like and we still use twitter bootstrap for the grid, the readability of the text and the basic layout elements. But it is very important to give it your own style and diverge from it over time.
Of course the anatomy trainer itself is mainly built without bootstrap. But even here we use elements of it.