webpack 4: released

Webpack now has zero-configuration modes and is significantly faster.

 

Webpack 4: released today!!✨ Codename: Legato Today we’re happy to announce that webpack 4 is available today! You can get it via yarn or npm using: $> yarn add webpack webpack-cli -dev or $> npm i webpack webpack-cli -save-dev Why Legato? We wanted to start a new tradition by giving each of our major releases a codename! Therefore, we decided to give this privilege to our largest OpenCollective sponsor: trivago! So we reached out and here was their response: [At trivago] we usually give our projects a name with a musical theme.

Legato means to play each note in sequence without gaps.

Webpack bundles our entire frontend app together, without gaps (JS, CSS.

Read more from the source: Medium

How to Run a Remote Team

From Zapier: a great list of tools and approaches that make remote work environments successful

 

A lot of energy has been expended over the last few years debating the merits of remote work. Unfortunately, not much information is shared about how to setup remote work so that you and your team can be successful.

For over three years, Zapier has ran as a remote team. We’ve grown from three founders to over twenty people. We’ve gotten a lot of questions about how we make it work. This chapter will explain how we make it work.

Read more from the source: zapier.com

The Difference Between “Remote” and “Remote-First” – ThinkGrowth.org

From Litmus: the 10 things remote teams need to succeed

 

One misconception about remote work is that it hinders collaboration. In my experience, the inverse is more likely: offices hinder independent work. Collaboration tends to happen in short bursts, followed by longer periods of writing, designing, coding and thinking. It’s more important to give employees quiet time than it is to cram them into an open office.

Read more from the source: ThinkGrowth.org

Remote-First vs. Remote-Friendly

Remote-first work environments take some work but can be very appealing

 

I think there’s a split between being remote-friendly — hiring some workers in a different city — and remote-first, meaning you build your development team around a workflow that embraces the concepts of remote work, whether or not your employees are remote.

By forcing yourself to use chat instead of meetings, by forcing yourself to use chatops to mercilessly automate every single manual action, you end up creating things faster, with more built-in context, and greater ability to share your knowledge across the organization.

If you’re not working in a remote-first environment today, not only are you not going to have a remote-friendly environment tomorrow, but you’re going to eventually have a hard time retaining talent and keeping competitive pace in the future.

The world of work is changing. That’s just the way it is.

Read more from the source: zachholman.com