Freek.dev

On the Tighten blog Samatha Geitz sums up the benefits of giving developers one day of "free" time a week.

About a year ago, Tighten officially implemented a "20% time" policy for its developers. This means that, on any given week, we only bill our clients for 32 hours of developer work; for the other 8 hours, developers can work on whatever projects they’d like to (as long as they can readily come up with an explanation of how it benefits the company in some way.) ... Here are some reasons that you may want to consider experimenting with a policy like this

https://blog.tighten.co/give-your-developers-20-percent-time

Read more

Rob Allen, an active member of the Zend Framework community, makes the case for giving some love to API errors.

It's not hard to have great error responses; you just need to care. Poor error response cause developers to give up with an API and go elsewhere, so it's a competitive advantage to get this right.

Developers integrating with your API will thank you.

https://akrabat.com/api-errors-are-first-class-citizens

Read more

Often, when I’m able to slip into a state of flow while coding, I will produce more in a single afternoon than I could in several days of non-flow. Yet this is often an elusive state to obtain. Luckily, research dedicated to this topic in recent decades offers some help. Here we’ll look into both the stages of flow and how to obtain the prerequisites for flow, making it possible in the first place.

Read more