# Going full cloud - seems like taking a step backwards

**URL:** <https://forum.serverless.com/t/going-full-cloud-seems-like-taking-a-step-backwards/16035>\
**Category:** Serverless Architectures\
**Created:** [October 7, 2021, 3:02am UTC](https://forum.serverless.com/t/going-full-cloud-seems-like-taking-a-step-backwards/16035 "2021-10-07T03:02:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChrisEdgington](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/chrisedgington/32/6251_2.png) [@ChrisEdgington](https://forum.serverless.com/u/ChrisEdgington)\
**Post date:** [October 7, 2021, 3:02am UTC](https://forum.serverless.com/t/going-full-cloud-seems-like-taking-a-step-backwards/16035/1 "2021-10-07T03:02:25Z")

</div>

I watched the “Enabling Serverless Teams” presentation today by the CEO of serverless. I was surprised by his suggestion to go “full cloud” when he was talking about development / debugging and whether or not to maintain local dev work environments. While I agree that they can get stale and require additional maintenance - what I’m finding is that using serverless / aws lambda in the cloud during dev is a huge pain. Serverless log tailing is super laggy. If I run code locally - I can see debug output immediately. Also deploys from github → serverless → aws take minutes, so every build-\>run cycle is painful with focus-stealing gaps. Is this really how folks do serverless work?

Thanks,  
-Chris