If you work in a product team that ships multiple times a day, there are great opportunities to empower designers to ship themselves. It lets engineers focus on high-impact, focused work, while empowering designers to sweat the finer details of the product. If you work in a busy product team, it’s worth asking yourself what could be unlocked if everyone was empowered to ship? Lorcan Coyle
Shell scripts have value. Everything you do for real code should be done for non trivial shell scripts, even for a one-time script. That includes versioning, code reviews, continuous integration, static code analysis, and testing. Thiht
This is a highlight from Michael Gorven's talk Continuous deployment to millions of users 40 times a day.
Software designers and developers are all about NEW. We like to experiment with far-out ideas and make shiny things. Our livelihood depends on it. We’re so addicted to NEW that sometimes it clouds our judgment. We love NEW and everyone else should too, so we force heavy-handed product changes onto our customers without much explanation. Jonas Downey
If you browse the log of any random Git repository, you will probably find its commit messages are more or less a mess. There is a vicious cycle here: because the commit history is unstructured and inconsistent, one doesn’t spend much time using or taking care of it. And because it doesn’t get used or taken care of, it remains unstructured and inconsistent. Chris Beams
It’s possible that you know C++ and Java but your work requires Python or you are well versed in Python and you need to code in Java at work. Or maybe you want to learn that cool language just to expand your expertise. So, how do you learn good practices of the new programming language that you are trying to learn? Sahil Dua
When deadlines slipped, there were no consequences — no consequences to my direct reports when they failed to deliver on time, no consequences to the people who reported to them — and no consequences to our vendors. Steve Blank