4 ms·
I've interviewed at a few Saas startups recently: - React / Redux / <and everything under the sun> - NodeJS + Typescript everything or die - GraphQL but we d
by keyle 6y ago
I've interviewed at a few Saas startups recently:
- React / Redux / <and everything under the sun>
- NodeJS + Typescript everything or die
- GraphQL but we don't know why
- React native because we wouldn't know what native is
- Postgres with replication and fail over for 10 concurrent
users
- Docker everything on AWS <every possible keywords>
- Don't forget lambdas, but batch with Kafka first
- Route 53 just cause the name is too cool not to have it
Joking about their Angular rewrite into React is a fireable offence.
See you in 2 years. /s
- iFreilicht 6y agoI mean I really get why people like using npm and Typescript is great, but the whole “web-tech got adapted for backend then adapted back to web” just makes everything so unnecessarily complicated. I think a lot of this “using frameworks without knowing why” is just because people read articles about them and how-tos and get excited too quickly, and Google just shows way more tutorials about how to do something in React than in plain JS. What are lambdas in this context? I thought those were just another name for closures?
- keyle 6y agoAWS lambda. Functions as a service!