You don’t need to be “enterprise-ready” or “scalable”

Re:You don’t need to be “enterprise-ready” or “scalable” by roflyear on Tuesday May 31, 2022 @07:01PM (#31575941)

Local dev isn't the end, it is the beginning. With it it allows you to get further than you would otherwise - and most importantly, when (not if) you do discover a problem on a lower environment (or prod) it gives you a place to try and replicate it. You run everything locally so hopefully you can make a change to mirror the problem... Not a guarantee but at least you have a good starting point.

Also your local dev should try and mirror prod as much as possible.

[ Parent | on HN ]

Re:You don’t need to be “enterprise-ready” or “scalable” by lmm on Tuesday May 31, 2022 @09:18PM (#31576938)

Yep. This is one reason I've always ran linux on my dev machine anywhere that would let me - sure, there shouldn't be any difference between OSes, but otherwise it's one more place for differences between dev and prod to creep in.

[ Parent | on HN ]

Re:You don’t need to be “enterprise-ready” or “scalable” by ek750 on Tuesday May 31, 2022 @09:25PM (#31576994)

Heck, in my previous $WORK, I saw differences from local (running Debian) to production running CentOS. Luckily one cluster of Jenkins build nodes were also running CentOS and those caught a subtle incompatibility between system libraries that would have blown up if we had merged and deployed to production. My local Debian testing env did not catch it.

[ Parent | on HN ]

Re:You don’t need to be “enterprise-ready” or “scalable” by roflyear on Wednesday June 01, 2022 @09:25AM (#31581482)

As a Python developer, yes, there are differences - and those differences are sometimes a huge PITA.

The only reason I don't run Linux is due to other MS tech - Teams, Outlook, and primarily office products.

[ Parent | on HN ]