So far I have extracted and loaded the xml data from the Health.app into MySQL tables. Next to recreate the rings in React.
Also need to be able to load a 'delta' of xml data, as the loading can take a loooong time.
571–580 of 1001 posts
So far I have extracted and loaded the xml data from the Health.app into MySQL tables. Next to recreate the rings in React.
Also need to be able to load a 'delta' of xml data, as the loading can take a loooong time.
I've been focusing more on implementation rather than an actual language design and have been blatantly replicating what commonly works on other languages (i.e. from the C family).
My goal is to eventually have a bag of tricks that is big enough to be reused if I ever decide to make a proper new language. At that point, it would "just" be changing the front-end.
There are a lot of good books, but eventually you're on your own if you want to reach the functionality of languages in daily use. It's fun programming challenges and a lot of rabbit holes.
Not making any assumptions that the code will be lean and clean. But at least it is code that I understand better than any ready-made publicly available code.
https://www.incrediblechinese.com
Right now I'm working on more content, sprucing up the interface and making the conversations more "live" (changing conversation pathways depending on the user's response, giving the bot a memory for the user's answers, and so on).
Eventually I really want to get to open-ended conversation (as in, not multiple choice unless the user specifically requests a prompt).
The problem is that language learners usually can't form a grammatically correct sentence longer than a few words, so the app will need to be able parse poorly constructed sentences (and ideally, correct them). This isn't an impossible task, but it will take a few months.
Not applying to YC though may be looking for private investment in the coming months.
Any and all feedback is welcome!
I also built and maintain JQBX (https://www.jqbx.fm) which is a turntable.fm-like website except it hooks into Spotify.
https://fsnot.es - open source, swift, secure :)
I call it a participatory sound art project. Many others have called it a scream hotline. It's been getting a lot of press!
The main use case is for multiple people. Think of it like Pocket / Instapaper but with the ability to share your collection of bookmarks with password protection for individual collections. One of the reasons for this website is to replace GitHub's "awesome-something" repos. Instead of having a GitHub repo which requires Git abilities (it is trivial to tech workers to use command line but not to others), I provide a simple interface for them to share bookmarks.
One of the use cases is for course resources - the professor can simple provide a link to a collection and update course readings / other resources there, and students will be able to access the most updated information. (The anonymous part is actually inspired by sharing of protest resources)
Smart Bookmarks, With Notes, Highlights, History, and Sharing
Histre helps you efforlessly create a personal knowledge base. The core idea is that the signals that users generate as they go about their day on the we can be put to good use for them. Right now it visualizes their research path, save notes and highlights, collaborate with teams, and such things related to creating and maintaining a knowledge base semi-automatically. have ambitious plans for where we want to take the product.
There are a number of integrations including with Hacker News, Pocket, and Pinboard. I'd love to hear your feedback.