4 ms·

I’ve found that a lot of developers would rather not have to think about where their application is going to run. This is a real shame, especially when there ar

I’ve found that a lot of developers would rather not have to think about where their application is going to run. This is a real shame, especially when there are free tools like SST that bridge the DevOps gap, making things like AWS and IAM less of a pain. Even better, there are complete self-hostable platform solutions like Supabase or the classic Docker Compose. However, the shared downside with these solutions is that they require some setup when it comes to deploying, unlike the magic of Vercel. I do wonder when we started losing interest about where our code is actually being executed ?

lionkor 2y ago
> when we started losing interest about where our code is actually being executed I don't think we did - it's more that new programmers aren't forced to learn it, and a lot of them are lazy and only here for the money. The result is a lot of people who think all that matters is shipping quickly. To them, it doesn't matter that this will result in lots more work down the road once the product needs to scale up.
- deleted 2y ago
  [deleted]
- hennell 2y ago
  > To them, it doesn't matter that this will result in lots more work down the road once the product needs to scale up. *Might* result in lots more work, *if* the product needs to scale up. Program lazily and ship quickly enough and that isn't an issue.
- WJW 2y ago
  Not scaling up until needed is a fine strategy. Most products fail, so they don't ever need to scale up and spending the engineering hours to make it bulletproof is literally wasted effort. Wasting time and money at the start of a companies lifetime makes it more likely the business will go up in the first place. If you need to scale up, you will have lots more revenue to pay for that work than you do at the beginning.
m3h 2y ago
SST[1] looks pretty cool. Does it replicate the entire infrastructure Vercel attempts to provide you regarding hosting (such as CDN, caching, etc)? [1]. https://sst.dev/ https://sst.dev/
- selfsigned 2y ago
  It leverages AWS’ infrastructure, your app code runs on lambda and you get a cloudfront (AWS CDN) distribution link. You can add to the built-in constructs via CDK (urgh) or pulumi (with SST ion).

lionkor 2y ago

> when we started losing interest about where our code is actually being executed I don't think we did - it's more that new programmers aren't forced to learn it, and a lot of them are lazy and only here for the money. The result is a lot of people who think all that matters is shipping quickly. To them, it doesn't matter that this will result in lots more work down the road once the product needs to scale up.

deleted 2y ago
[deleted]
hennell 2y ago
> To them, it doesn't matter that this will result in lots more work down the road once the product needs to scale up. *Might* result in lots more work, *if* the product needs to scale up. Program lazily and ship quickly enough and that isn't an issue.
WJW 2y ago
Not scaling up until needed is a fine strategy. Most products fail, so they don't ever need to scale up and spending the engineering hours to make it bulletproof is literally wasted effort. Wasting time and money at the start of a companies lifetime makes it more likely the business will go up in the first place. If you need to scale up, you will have lots more revenue to pay for that work than you do at the beginning.

m3h 2y ago

SST[1] looks pretty cool. Does it replicate the entire infrastructure Vercel attempts to provide you regarding hosting (such as CDN, caching, etc)? [1]. https://sst.dev/ https://sst.dev/

selfsigned 2y ago
It leverages AWS’ infrastructure, your app code runs on lambda and you get a cloudfront (AWS CDN) distribution link. You can add to the built-in constructs via CDK (urgh) or pulumi (with SST ion).