I would look into AWS Lambda. Lambda host backend functions written in javascript, python or java. You can then use the AWS javascript sdk in your frontend code to invoke these lambda functions. This will be very low cost and cuts out a lot of boilerplate work. You pay on a per request basis versus an hourly or monthly basis. So if no one is using your website, then you pay nothing.
We use Teletraan heavily. Currently we have about 500 deploys per day, including the auto deploys.
Slightly off topic, I'm a big fan of continuous deployments, but 500 deployments a day seems excessive. Assuming an 8 hour work day, thats more than 1 deploy every minute. Its great that this system works that seamlessly, but are there really benefits with deploying that frequently?
Im not positive, but it sounds like a fairly recent switch from a cloud provider to their own datacenter. If thats the case, Id expect a number of outages to come in the following months.
As we started transitioning hosts and services to our own data center, we quickly realized we'd also need an efficient process for installing and configuring operating systems on this new hardware.
You were probably already "gone" once HR contacted you in June. HR's job is to protect the company, at no point were they concerned with improving your work relationship with the other employee. However, they were concerned with making sure you couldn't sue Google for wrongful termination. They gave you 6 months notice, followed up with you a few times, tied up any lose ends and then let you go.
While I do think you were already gone, it sounds like you handled things horribly during this 6 month period. You should have cut off all contact with the other person and started job hunting.
I do a good bit of weight lifting, typically 4 or 5 times a week. I find it a great way to disconnect and focus on something very simple / straightforward for an hour. Its also a great way to relieve stress.
+1 for weight lifting/training. I'm more on the powerlifting style than Olympic Weightlifting.I go four times a weel and I've been following variations of 5/3/1 for about 5 years now. If anyone wants level up their strength and health I heartily recommend it.
I don't primarily train for my physique. When people lift weights, people can have different aims in mind. Olympic Weightlifters become more explosive and better at the Olympic lifts. Body builders train for muscle size and definition. My primary aim is to see the weights I lift get heavier and heavier from week to week and month to month. As a result of that, my physique is better than it was before, but I would never be mistaken for a mens fitness cover model.
I think you're over thinking things. Tech hiring is so random that you could have the most impressive list of projects on github, but if you get asked a single data structure question that you stumble on they might pass. Similarly, you could ace the white boarding questions, but if they check out a project of yours on github that they don't enjoy for some reason they might pass.
I would stick to doing whatever will give you the most confidence when talking to companies. If that is studying data structures/algorithms then keep doing that. If its launching a side project focus on that instead.
Thanks for the feedback-- that's what my hunch was. I agree completely. I think hiring _is_ quite random and that is partially what puts me on edge. I want to prepare and give myself the upper hand but it's so random it's hard to prepare for.
I do think data structures and algorithms are a must and if I had to guess, stumbling on the whiteboard is probably the most common reason for a rejection which is why I think that is something that needs to be practiced.
At one horrible startup I worked for I would do 3 hours of work and then wait out another 6 hours because of the 9 hour face time expectation. I had high output because I'm good at what I do but they couldn't wrap their heads around not having me there constantly.
I ended up quitting because I was tired of watching my boss browse Facebook and sports blogs all day.
Before I got there they rolled the dice and walked away from a $250MM acquisition offer and ousted their original CEO. They were somehow able to acquire additional funding before I left but, based on the numbers I saw, they were using questionable models to indicate that they were more profitable than they are.
They still exist and will probably take another 18 months to wither and die. The experience taught me to look hard for red flags and to hold my company as accountable as myself.
Hey I'm Ryan. Im a tech lead, full stack developer and Techstars graduate. I’ve built and launched multiple iOS apps which have been featured in the App Store. I have extensive experience building highly available, scalable and cost effective systems on AWS.
Software bug caused downtime vs infrastructure / hardware availability uptime to me are a different guarantee. I am pretty sure someone did something recently to DynamoDB.
Infrastructure guy here doing this for 14 years. Downtime is downtime. You get a pass if its "scheduled maintenance" you've notified your customers about to allow them to be prepared, but if you silently perform maintenance and it goes to shit, you've just counted against your metrics.
Nope. I still disagree. No service can guarantee 99.999999% unless you discount software upgrade. You just cannot. If you think those nines include software upgrades, you are probably over optimistic.
> If you think those nines include software upgrades, you are probably over optimistic.
If you advertise a product with a specific SLA, and you can't meet that SLA, you're a liar. Don't try to blame the victim because of inaccurate/untruthful marketing or engineering.
I used SLA to communicate an advertised/marketed level of service. In this case, I agree, that SLA is the wrong term as there is no contractual agreement.
