mmcgrana
Joined 19 years ago
Joined 19 years ago
The foundation of our approach is to have a versioned, documented schema shared among clients. Every write down to the individual attribute level is persisted with a schema version. We're already several versions in, and indeed think it's healthy to get experience with version updates frequently so that it's not an unusual occurrence.
Currently we use this schema to interpret / coerce values as needed at read-time. For example we see an attribute has schema version 1, and know that it should be interpreted in the sense that we meant as of version 1. In the future, we may also choose to write out updates for "migrations" where that'd be helpful. So that e.g. instead of having to re-interpret values for older version 1, we'd right out an update to he attribute that overwrites the old value and updates the version tag to e.g. 3.
We do think lenses are interesting and the lab from which we spun out has done some good work with them: https://www.inkandswitch.com/cambria/. They're just a bit complex for our modest needs re: schema versioning at this time.
Looks like the site has a few other scraped posts as well.
FWIW I no longer use this exact noprocrast(1) approach to avoiding procrastination, but do apply the same basic idea.
Muse is an iPad app to empower freeform, creative thinking. The company spun off from our industrial research lab (https://www.inkandswitch.com); we’re taking the novel interface approaches and technical ideas developed in that setting and turning them into a real-world product.
Learn more about Muse:
- Conference talk by a founder: https://www.youtube.com/watch?v=A_fe2c6IUUo
- Article by the team: https://www.inkandswitch.com/muse-studio-for-ideas.html
We’re hiring one engineer to join our all-remote team of four, with either of these two profiles:
- iOS Engineer: https://getmuse.app/ios-engineer
- Systems Engineer: https://getmuse.app/systems-engineer
We aim to be a small, independent business that optimizes for building an uncompromising product and that’s a rewarding place to work.
If you're interested please email us at [email protected]. We look forward to hearing from you!
Muse is an independent software company that makes an iPad app for thoughtful work. The app brings together your research, photos, and notes in a single fluid workspace: https://museapp.com
We're hiring one engineer to join our all-remote team of four. One profile that's a good fit is an experienced iOS engineer:
https://museapp.com/ios-engineer
If you're excited about Muse but haven't developed for iOS, we can teach you iOS. In particular we'd love to hear from systems engineers with experience in e.g. game engines and graphics pipelines who'd like to apply their skill set to a product like Muse:
Also agree that a learn more section could be good - I'll noodle on it.
Heroku is hiring infrastructure engineers across all of our platform teams.
We develop a large distributed system that runs and manages thousands of applications in the cloud. We're looking for engineers who are exited about working on challenging systems at scale.
Some specific things we work on:
- Dynamic HTTP and Syslog routing: Erlang, Redis
- Cloud-wide distributed process management: Ruby, PostgreSQL, AMQP
- Containerized process execution: Linux, LXC
- Platform substrate management: Ruby, EC2/ELB/S3
- Real-time event processing: Clojure
If you're interested in learning more, email me directly: [email protected].