Evernote Food was already shut down (https://blog.evernote.com/blog/2015/09/16/better-brainstorms...) a couple weeks ago.
400 karma · joined June 18, 2011
Evernote Food was already shut down (https://blog.evernote.com/blog/2015/09/16/better-brainstorms...) a couple weeks ago.
- especially: owning the encryption keys [1].
- agnostic of the storage (S3, Glacier, Dropbox etc. can be used)
- documented backup format
[1] https://www.haystacksoftware.com/blog/2014/10/its-not-about-...
- Go to developer conferences. You will make connections with other people who might have leads or other people doing the same thing who don't have time to do everything and might forward projects to you.
- Build a software library in your field of interest (or even a successful product). From experience this will generate inbound interest for customizations. You will be very well positioned to do the work (Sidekiq, Ensembles come to mind).
You would think you can still develop an iOS app when GitHub is down, but a simple `pod install` requires access to repos hosted on GitHub.
http://www.theguardian.com/technology/2015/apr/29/apple-ipad... http://qz.com/393909/american-airlines-planes-are-grounded-b... http://money.cnn.com/2015/04/29/technology/american-airlines...
These frameworks actually don't require you to rewrite your whole app in a different way: you can easily migrate a few classes or just rewrite a few new classes. I would recommend this as a way to get familiar with functional reactive programming in an applied way.
This reminds me Steven Colbert interviewing Thomas Piketty. Colbert jokes about the short work weeks and two-months vacations in France. Piketty's reply: "in Europe, many people believe the purpose of civilization is to work less, have more vacation, take care of your friends and family. But you can make a different choice and that's fine". France is still the 6th economic power.
In theory it's nice to work with, as it forces you to think everything more carefully and consider all error/nullable cases. In practice, integration with XCode is still full of bugs, code completion is crashing all the time, Swift classes show up as missing symbols in Objective-C (but the project compiles fine)... So, it's a bit painful and it slows down the development process.
We will keep it to very small and well-defined pieces of code for now. It's good to learn about it, but it's not productive.
The OP didn't claim it was better than anything, it's just a nice exercise in style!
We are currently two but we will be three starting next year. That will definitely help!
We want the backend to be very transparent for the user. This means that if there is any downtime on the server, you will still be able to use the app, scan documents, create PDFs, export them etc.
However, it has always been our philosophy to take our time to reduce the operational load as much as possible since our time is so precious. We have quite some experience with that having run the business as a side-project for a while before going full time on it. Running a boostrapped, profitable company also helps in that you don't have any external pressure.
What you are after is the publishers and the labels, not the copyright monopoly.
Base salary for fresh out of school engineer is about 40 kEUR. You need to add 75% of social contributions, so that totals around 70 kEUR.
If you are a "young innovative company" though, you can have exoneration of these social contributions and only pay ~40 kEUR for the first few years.
To address the "one way" API limitation, I would expect Microsoft to add more endpoints over time and I think it's not a bad strategy to start with that one. Adding a way to post notes to OneNote already enabled a lot of cool integrations...