The iOS-Frontend is UIKit and RxSwift. The backend is pretty lean — TypeScript, Firestore with the beginnings of PostgreSQL (with Prisma!). The recommender piece for the daily tips is Python. We also use cloud functions to run async updates (e.g. for daily updates and migrations).
Otherwise — lots of hosted services in the mix (Brave, Circle/Github, HoneyComb to name a few).
As for the future, we're exploring Flutter and a few other options to provide different experiences.
A new account doesn't have all AWS services enabled by default, so the impact seems minimal to start with. Not sure if you can lock this down further as I haven't looked into it.
In general, and especially for people freelancing in Germany, I'd add: Not getting a tax consultant.
I'm pretty sure this is the same everywhere, but regardless, it's the first thing I tell people which they have to get in order so they don't get screwed later on. ;)
> Data are encrypted directly by the provider, which means customers need no specific technical know-how and incur no extra costs. All data are stored in secure data centers located in Germany.
Not sure how this is the solution. People need to learn how to do encryption themselves. For the average John Doe (or Hans Wurst :-)) there need to be tools to accomplish that without a degree in Math or CS.
I don't think provider-side encryption is a solution at all. Collecting vast amounts of meta data would still be possible.
In addition, I'm not a huge fan of linkedin either. There are no guarantees to it. One is that most of what's on there is hard to check and linkedin endorsements are just unreal to start with.
I know people who just endorse each other for random things. I have endorsements from people who I have never worked with for technologies I have never worked with.
So in the end — Github or similar wins. Allows me to see their code (and contributions), and that's what matters. For the rest (compatibility on a social level), there are interviews and probation.
Can anyone explain/summarize what this is? I gather it was/is feed reader, but I can't find much more and she (?) is very vague. Or I don't know how to navigate her blog.
A rescue dog — unless maybe really, really old — needs to be challenged constantly. And by challenged, I mean — these dogs are/were rescue dogs for a reason. :)
Challenges include games and tasks, and all that. These dogs need "work" to feel alive.
We're using emberjs right now as well. But the lack of test integration is a huge problem for us. We right some tests with busterjs currently, but none of these tests are unit tests and tell us what exactly went wrong — somewhere.
So not to mis-read my comment: our application works and we deployed to production, and it's being used by customers, etc.. But whenver we need to dive into an emberjs-specific issue (e.g. we had a few regressions to fix which were introduced with the RCs) it gets messy.
If anything, the lack of testing (and currently lack of ideas how to integrate any) is the number one reason why I don't want to use emberjs again any time soon.
ember-data seems fine for us. Lots of conventions to adhere to (otherwise it's no fun at all). Once you figure out the side-loading, you're fine. We had to write a custom adapter so we don't have to repeat the things they call REST on the server.
It would be pretty nice (if I may suggest that ;)), if you added add branch support so the patches are saved into a refactoring branch or maybe individual branches?
I am less interested in running k8s itself in Firecracker (or kata, or similar), but the pods started by it. I think there are advantages to that.