News for hackers. Stuff that matters.
Re:Cloud Functions: Go 1.11 is now a supported language by omeid2 on Wednesday January 16, 2019 @08:25PM (#18927490)
Your code review and deployment pipeline should be all automated from day zero. Setting up a CI pays off in the first couple of days in terms of time investment and massive returns on longer term mostly for avoiding human error and confusions that ensues.
Re:Cloud Functions: Go 1.11 is now a supported language by solatic on Thursday January 17, 2019 @10:27AM (#18931435)
CI is a continuous integration tool. There are inherent latencies to committing, pushing, deploying to AWS, running tests. Mature development tooling, if it's not REPL-based, will at least allow a local debugger to step through the code compiled/run locally, without these remote latencies.

Both tools are necessary for fast engineering, but in different contexts.

Re:Cloud Functions: Go 1.11 is now a supported language by benatkin on Wednesday January 16, 2019 @08:52PM (#18927629)
I didn't say that you don't need CI. I use CI regularly, and I think it's best for CI to be for testing, and to minimize the build artifacts except those used for test results.

A lot of developers have this preference for client side code. Since the early days heroku has been building the client side bundles for rails.

Re:Cloud Functions: Go 1.11 is now a supported language by weberc2 on Wednesday January 16, 2019 @09:07PM (#18927677)
The parent’s point was that contributors shouldn’t have permissions to upload binaries; they only commit source code and your CI infrastructure compiles, releases, and deploys it.