I was listening to a podcast called Voice of Design, and in the first episode the hosts ask themselves: "What is the job of a designer?" Now that got me thinking about the job of a programmer and what we're actually being paid to do. I think a
Katherine and I had Vaidehi Joshi on our podcast Friends Talk Frontend yesterday, and we asked her about her learning habits while she was working on basecs. Basecs—for people who are unfamiliar with it—is a blog (now a podcast and a video series) where she set out to
I find myself working with a lot of people on a project: other developers, other designers, content strategists, project managers, and stakeholders. I can keep people in the loop through meetings and through status updates on the work that I'm doing, but what I've found useful—especially when working with
I think one of the hardest things to do—and it doesn't matter if you're just starting out or if you've been in the industry for years—is finding the time to learn. And it's especially bad if you're a web developer because things really are moving quickly, and it's
I've been programming for a while, but I've never really made any games myself. I've played around with Codea back in 2015, but I stopped and didn't get to learn how to make an actual playable game. But a few days ago I ran into the PICO-8 (thanks to @BrianHall!