I've seemed to found myself in a limbo between passing a screen and waiting for an onsite to be scheduled without much in the way of feedback from the recruiters on when to expect next steps. I've been working with them for about 2 months now and I'm not seeing an end in site; any suggestions? This is for a Staff SWE role fwiw.
Sorry to hear that. If it's for the role in my link or another product eng role let me know and I can have someone look in to it for you. If not the recruiter you're talking to is likely your best bet.
I believe it was, actually. I know the original rec I was looking at was filled at some point and that threw some things off so the recruiter was looking at this one instead but haven't heard anything since, unfortunately. Is there a good way to send you info on myself for you to pass along?
We have been having that discussion internally at the company I work for. After the initial shock wore off and we started deciding what we would do with the projects currently on Parse, we realized that this could very well be a good thing. Before this, we were not able to use Parse for larger clients or clients with specific database hosting needs, but that may no longer be an issue. I'm excited to see what the future holds for Open Source Parse.
We spent a few days investigating alternatives and then decided to just wait and see what happens over the next few months. We want to switch to DynamoDB instead of MongoDB due to cheaper hosting costs through AWS for the amount of data we use. There's already someone working on cleaning up the DB code to allow for switching DB providers.
In my study of Dynamo DB I found that it might actually be more expensive than managed Mongo DB. But I didn't get a chance to test this out because of lack of budget as we decided to build against Mongo DB rather than build for both and check which one is more expensive.
The problem with Dynamo DB is that one needs to provision the read and write capacity in advance, which means that one needs to over provision in order to be sure. Also even for things like exporting database which requires lots of reads in short time, one needs to provision the read capacity. This can make the back ups very expensive. However I am basing this from my study of their docs as we were building our application. (A chat server).
It will be good if somebody can share their actual experience about Dynamo DB especially from the perspective of cost. Yes, almost unlimited scalability is very attractive, but I found that I had to think about data access patterns a lot to ensure that we will stay in acceptable read write quota for Dynamo DB. This was causing a lot of delay in our MVP. So we decided to go with Mongo DB which we knew we could scale fairly beyond our MVP and may be rewrite the data access layer later on if we achieve a mass that requires a switch to something like Dynamo Db or manual sharding.
This looks great. I have a few friends involved in teaching K-12 education who have been exploring ways to introduce some of the younger ones to programming so I will be sure to pass this along.
I bet it would be fairly similar to the level of integration offered by Pebble which would mean at least notifications could be received by it. Not 100% sure what Pebble is capable of doing nowadays as I'm stilling waiting for Pebble Time Steel.
As of this last year's WWDC I think Apple is finally backing down on that. None of the presentations carried the usual alert to not share what you have seen in there and they have started (slowly) opening new OS X and iOS betas to the public.
I think it has potential but it needs to be quite a bit more subtle. It seems too distracting the way it is right now. I find myself trying to just keep track of the animations and not really appreciating the attention to detail.
I love UIAppearance. I am not too well versed in CSS but UIAppearance adds a lot of what I have seen done with CSS. You can change the default appearance of most default elements really easily, and declare containers inside of that with a whole different set of defaults. It makes styling your app a really painless process. All you have to do to make all the UIToolbars in your app red, for example, is use this one line at the start of your program.
