Practices Icon


Development and business practices, methodologies, workflows, etc.
15 Stories
All Topics

Practices Icon

What does a developer advocate do?

Lorna Jane Mitchell, on the role of a developer advocate: The less-visible part of the role is probably the most technical part. People rarely think of the gregarious advocates they see on stage or tweeting as being technical but we are, probably more than you expected. I write sample code and internal tools, but better than that: it's my business to wade in and improve anything that would make life easier for developers. An advocate is just that, someone who acts on another's behalf — a role that requires a variety of skills: The job requires a really weird mix of skills, and like most advocates I'm endlessly delighted to find that there's a job that combines such a great combination of stuff I like to do! The role varies a lot between jobs, and also between weeks — it's a little bit of everything.

logged by @adamstac 2018-02-15T15:15:38.117178Z permalink #practices

Medium Icon Medium

What I wish I knew when I became CTO

From David Mack, CTO and co-founder of SketchDeck: You can accumulate responsibility faster than you can learn how to harness it. I now appreciate that the infrastructure, frameworks, and languages you choose will stick with you for a really long time. Only hire when you feel you’re completely desperate for the role. Hire to keep up with growth, not to generate it. I really appreciated David's thoughts on hiring.

logged by @adamstac 2018-02-15T02:25:52.857259Z permalink #practices

Matt Steele

The neverending side project

Matt Steele, ruminating on the side project that he's been hacking on since 2011: A long-lived side project gives you the chance to confront your old habits and see how far you've progressed. Over the years, he's rewritten the Super Bowl Squares app 5 different times. One of his findings: A long-lived side project also gives you breathing room to ask how much stock to put into trends. My original jQuery app still loads faster, has 60% less code, and (to my mind) is more understandable than my latest version built atop Angular 5. Have I actually made things better? Have we as an industry? Good question!

logged by @jerodsanto 2018-02-13T17:01:00.009558Z permalink #practices

CSS Icon

Everything easy is hard again

This is a long, nuanced piece about progress in web-building technologies and practices. It's written from a designer's perspective, but many of the themes ring true to my developer's brain. I wonder if I have twenty years of experience making websites, or if it is really five years of experience, repeated four times. If you’ve been working in the technology industry a while, please tell me this sounds familiar to you. The primary example cited is how we answer the simple question, "How do I put two things next to each other?" The status quo has changed (tables -> floats -> Flexbox -> CSS grids), but to what advantage? A few of his points feel a bit like looking back at the "good 'ole days" through rose colored glasses, but his case is mostly well-reasoned and powerful. the foundations are now sufficiently complicated enough on their own that it seems foolish to go add more optional complexity on top of it. I’ve kept my examples to the most basic of web implementations, and I haven’t touched on Javascript, animation, libraries, frameworks, pre-processors, package managers, automation, testing, or deployment. Whew. Whew, indeed! The breadth and depth of knowledge required to feel competent in today's web ecosystem is probably why we spend so much time dealing with imposter syndrome in this industry.

logged by @jerodsanto 2018-02-12T14:19:00.08510Z permalink #design #css #practices

Rico Sta. Cruz Avatar The Changelog #283

Devhints - TL;DR for Developer Documentation

Rico Sta. Cruz joined us to talk about his project Devhints — cheatsheets for developers! There are more than 365 cheatsheets you can contribute to and it's open source. We talked about the design, technical implementation, community, and alternate interfaces (CLI). We also covered RSJS, RSCSS, and Docpress. You have to sell what it is you're building in your documentation. It's not just describing what it is and how to use it. It's about telling interesting stories. — Rico Sta. Cruz

logged by @adamstac 2018-02-09T23:18:08.927265Z permalink #practices #javascript #css

Kelsey Hightower

No Code

Reminds me of madrobby/vapor.js. No code is the best way to write secure and reliable applications. Write nothing; deploy nowhere. Go back in time and listen to The Changelog #39 to hear about Vapor.js.

logged by @adamstac 2018-02-07T16:30:51.346911Z permalink #practices

Practices Icon

Why write postmortems?

Postmortems are a healthy exercise to do after an incident to learn the specifics of why it happened and what needs to be done to prevent it from happening again. A good report captures the risks of current services, and helps Product and Engineering to more proactively prioritize work on services. Someone from outside your team should be able to read your postmortem report and answer these five questions...

logged by @adamstac 2018-02-01T04:16:00.009523Z permalink #practices #ops

TODO Group Icon TODO Group

A guide to shutting down an open source project

The TODO Group published a set of guides last year focused on open source program management. This year, they kicked things off with an initial guide about how your org and team can plan for the day when you're ready to end or move away from an open source project. This guide covers the gamut of concerns around shutting things down: Why life cycle planning is important What does a dead open source project look like? Trouble signs to watch for Why plan for the end of a project before you even launch it? Protecting your company’s reputation Of course, all of the TODO Group guides are open source on GitHub. We talked about the TODO Group with Will Norris from Google on The Changelog #245.

logged by @adamstac 2018-01-30T05:51:44.969834Z permalink #practices

Practices Icon


This is an incredibly insightful piece the difference between popularity and quality in software development. In software development, a lot of people pick the most popular tool that can solve a given problem. Popularity is measurable: you can check the number of downloads, the number of stars, the questions and answers all over the web. Quality, on the other hand, is hard to measure... An anecdote of a CTO trying to navigate tool selection with his development team is provided, and while his choice is out of the ordinary, the response from the peanut gallery is not. Read the whole thing (it's short), but here's a snippet of the author's takeaway: we should be extremely cautious about taking what is popular for what is good, and conversely we should not disregard something just because it didn't gather enough stars. This reminds me of the excellent conversation we had with Ozan Onay on episode #260 of The Changelog, where he encouraged developers everywhere to DYOR.

logged by @jerodsanto 2018-01-29T15:52:00.010578Z permalink #practices
0:00 / 0:00