undefined | Better HN

0 pointstomatowurst4y ago0 comments

yeah that was my worry but seems like it is based on CDK so perhaps you would end up hacking that layer but then I don't know really know and I would be gambling and I really don't like it.

I'm just amazed by how small problems are blown out of proportion to sell you an elaborate contraception....like a Rube Goldberg machine which is what this feels like.

what is wrong with just using SAM or aws chalice like we've always done? even looking at Laravel vapor (problems with cloudwatch logs)....all of it seems like a rube goldberg machine of sorts and this is why aws chalice has been my go to tool simply because A) it is written by AWS team B) it just spits out cloudformation, SAM, cdk C) stages like you are used to

"magical" here means sacrificing simplicity and overloading the developer with MORE rube goldberg machine on TOP of the stress from having to do "program in AWS" imho.

0 comments

3np4y ago

If you don't see the purpose of something adding complexity or abstraction layers, you most likely don't need it and shouldn't adopt it (yet). With the hopefully obvious caveat of some things relating to security, like firewalls and scoping capabilities. Start simple and look for solutions only once certain things become painpoints.

zaphirplane4y ago

There was an post a few days ago about https://en.m.wikipedia.org/wiki/Wikipedia:Chesterton's_fence

Which boils down to if you don’t understand why then don’t replace it

tomatowurstOP4y ago

very very good principle. i have favorited. in case next time i feel like im drinking the koolaid.

also applies to the whole blockchain space.

3np4y ago

And as always - just because it is not the right choice for you right now does not mean it is "bad".

On the flip side, consider a small team spending hours every week doing fully manual deployments instead of automating at least parts of that.

Different people and orgs have different needs, and those can change over time. Learning to strike that balance and timing right is a hallmark of a great engineer IMO.

> also applies to the whole blockchain space.

It applies to everything. Blockchain can serve a purpose w.r.t. the security I alluded to above. Security in general is a tricky one as once you realize it's a problem, it may be too late to reconsider.

j / k navigate · click thread line to collapse

0 comments

3np4y ago

zaphirplane4y ago

There was an post a few days ago about https://en.m.wikipedia.org/wiki/Wikipedia:Chesterton's_fence

Which boils down to if you don’t understand why then don’t replace it

tomatowurstOP4y ago

very very good principle. i have favorited. in case next time i feel like im drinking the koolaid.

also applies to the whole blockchain space.

3np4y ago

And as always - just because it is not the right choice for you right now does not mean it is "bad".

On the flip side, consider a small team spending hours every week doing fully manual deployments instead of automating at least parts of that.

Different people and orgs have different needs, and those can change over time. Learning to strike that balance and timing right is a hallmark of a great engineer IMO.

> also applies to the whole blockchain space.

j / k navigate · click thread line to collapse