truetuna

Perhaps not as big as others, but Airbnb.

https://news.airbnb.com/airbnbs-design-to-live-and-work-anyw...

Indeed. If you don't like it, prepare to get into a lot of arguments. EKS/Helm providers in combination with controllers are wild. It forces you to understand every little facet your cluster if _anything_ goes wrong.

I had similar thoughts when I read their article. Their atomic deploy problem completely disappears had they gone with an immutable approach.

Even if you don't use Docker in production, I think it's still very useful tool for local development, combined with docker-compose.

When I'm working on one service, I often depend on a few other services too. I usually need a storage layer, perhaps API calls to related services, it may even to talk some Amazon services like S3 or SQS. Having a simple way to spin up every dependency locally, even AWS (lots of great AWS API compatible images out there) is really useful if only for local development.

Yeah, this and a couple other reasons have caused me to jump ship (slow boot times, weird config, glitchy UI, plenty of deploy integrations but individually limited, too much downtime e.g. today Travis had trouble talking to S3 for a while). They're constantly improving which is great but after using them for 2+ years, it was time to leave. Plenty of great alternatives out there. Circle CI, Buildkite, Jenkins, Bamboo.

Could you expand a bit on shorthand property syntax or provide a link to somewhere I could read more? I'm still doing a lot of .bind(this) in many places and I'm looking for an alternative.

I've used Shoutem's standalone UI library[1] for my last project but haven't used their platform as a whole. During that time, I found it painful to get it working.

Their documentation[2] wasn't great. It was out of date (missing component attributes, icons etc.) and lacked good examples. Often I would have to dig into the source to figure out obscure errors. When I first starting using @shoutem/ui, I couldn't use the latest version of React Native because they locked themselves into an experimental feature[3] which even until now, seems like it hasn't properly resolved.

Again. I can't comment on their platform but I didn't have a good time using their UI library. Had I known this, I would have just gone with NativeBase[4].

[1] - https://github.com/shoutem/ui

[2] - https://shoutem.github.io/docs/ui-toolkit/components/typogra...

[3] - https://github.com/shoutem/ui/issues/241

[4] - https://nativebase.io/

Based on my personal experience, sometimes even if the API is yours, making changes can be difficult. The example I first think of is my last company.

We had a backend and frontend team, both working on the same product but the two teams disagreed a lot and would take weeks to make a small change even if it wasn't a breaking change.

To add to it all, there wasn't a standard to deprecating APIs so even a simple key rename could cause everything to blow up. Things weren't fun so I can see the need for these kinds of tools.

Opening it up in incognito mode on the iPhone doesn't seem to work.

It's been a while since I've used Django but at the time (I think 1.6) I couldn't figure out a way to do a migration like adding a non null column to a decent sized relation 100M records without having the table lock up.

I use flyway now for db migrations and what's great is that I can perform migrations in multiple steps (because it's just SQL). So in this case, I can alter table and add a column with nullable, deploy my app to write to both, migrate data at a later time, deploy app again to stop writing to the old column, update column constraints and remove old column.

Does Django ORM have this kind of flexibility?

I've tried localstack once a few months ago to mock SQS and found it really slow to boot, had a pretty high memory footprint, crashed very often (was running inside their official docker container I recall), and lacked documentation.

If you just need to mock SQS, I recommend using elasticmq. I've used it for a few months now and haven't had any problems at all so far.

https://github.com/adamw/elasticmq/blob/master/README.md https://hub.docker.com/r/expert360/elasticmq/

I wouldn't recommend ECS. I've used it for a little over 6 months and even for trivial things, it lacks. A couple examples that come to mind include not being able to pass host environment variables into your container instances easily, and not being able to specify that a service must run on all hosts.

Theres an open issue (made ~2 years ago) on GH for the 1st example and it still hasn't been resolved.

Yeah, agreed.

Unfortunately when you inevitably make changes to your CF config, `terraform plan` doesn't help because it's likely you changed something inside the `template_body` and Terraform just knows the string has changed and doesn't tell you what part of the config changed. Parameterising as much as you can helps.

Terraform is great but there are certain things that I still use Cloudformation for (simply because you can't do it right now using Terraform). One example is rolling updates on your ASGs. Last time I checked you can't do it via the aws_autoscaling_group resource.

This!

I did exactly this before leaving my previous position. We had a friendly 45min call the next day, just talking about my current situation at the time and he was thrilled I reached out to him directly.

I've had my fair share of bad interviews too. Just recently I was interviewing for a full stack position with a company that tried to get me to recite "what happens when I type google.com into my browser". I asked them where they had gotten idea from and showed them this: https://github.com/alex/what-happens-when. They decided ask me another question soon after.

Sometimes the questions aren't even related to data structures or algorithms. I'm OK with those because at least you can somewhat prepare for them. I've once had an interviewer ask me obscure questions about Netscape 6 (this was 2016 btw).

> I much prefer “homework” projects, even if they involve me working “for free”, because I feel like they ask for actual programming skills rather than the “guess the algorithm” lottery of phone screens and whiteboard coding.

Me too but when you're interviewing with 3+ companies at the same time while working at your current job, it gets difficult. There was one time where I had spend my Saturday afternoon maybe 6-8 hours completing their "homework" project. I got a call back from them a few days later for a follow up interview and they flat out didn't even bother to ask about the project I had completed for them. What was the point?

Tech interviews suck.