Game journalist Maddy Myers:
I have no idea how anybody else survives in games journalism. Well, actually, I do know now. It’s that other people just get day jobs. They do what I’ve done. If they’re lucky enough to find one that they can do in addition to journalism without wanting to die all the time. Maybe they just give up and get a full-time job that has nothing to do with journalism at all.
Eventually, if enough people tell you that your work isn’t valuable, you start to believe them. No matter how many high-minded ideals you have about writing having intrinsic value or journalistic ethics or whatever … continuing to hustle while you’re also hungry and depressed is basically impossible. I tried to do it. I failed.
It’s very disheartening reading posts like this. It’s another reminder journalism in almost any entertainment media (film, gaming, tv) is a dying full time occupation, in the process leading to a serious drop in quality and enthusiasm. Just as importantly, it’s a reminder of the amount of harassment and discrimination women often endure in this field, be it as journalists, developers, or even enthusiasts.
CSS Tricks‘ Chris Coyier wrote a nice little post going over some of his favorite Sass mixins. Sass is wonderful and I’d recommend it to anyone, but even for vanilla CSS users, do read his ‘centerer’ code snippet as well. Fairly brilliant way to basically center anything regardless of the outer container size, all with a simple transform property.
Facebook engineer Carlos Bueno, writing a post already heavily passed around tech circles about the Valley/startup insular culture:
The problem is that Silicon Valley has gone completely to the other extreme. We’ve created a make-believe cult of objective meritocracy, a pseudo-scientific mythos to obscure and reinforce the belief that only people who look and talk like us are worth noticing. After making such a show of burning down the bad old rules of business, the new ones we’ve created seem pretty similar.
It’s been over a month since this was published, but Carlos’ post struck a cord with me and is worth revisiting. I suspect it’s going to be one of those posts that I revisit from time to time long from now, especially as I reach more positions to hire and shape the culture of a company.
I’ve documented best practices in the Git version control system for my coworkers often, from meetings to random Google Docs and emails. Yet reading over this post by developer Jean-Philippe Boily, I realize he’s eloquently and succinctly gone through the key principles that matter most. Worth a read for Git newbies.
I personally tend to favor commmand line runners and local apps for my sprite generation, but Spritebox looks like a slick web-based alternative.
I usually give my students and junior developers two pieces of advice: practice your skills and work on strong side projects. Practice is a given, but projects on your own time are a greatly underrated and often forgotten asset.
Strong projects challenge you in at least one way. If you’re focusing on development, maybe you’ll target a framework or an aspect of a programming language you haven’t used yet. If you’re a designer, it could be a new tool or workflow. Remember, the side project needs elements of the familiar to make regular progress so you do not get frustrated and give up, yet remain achievable over time.
Great side projects are a mix of what you can execute quickly but are also somewhat foreign and difficult. It’s a twist on your existing point of view, not one that’s completely coming from left field. One personal example: a refresh of this very site (familiar), but undertaken with a fresh set of responsive design tools and Sass underpinning the styling (foreign).
It’s not an accident I generated my latest project after work hours; the best side projects are almost always outside the day job. Because you’re free from work interference, it can and should move at your own pace. It’s ok to be disorganized too. You don’t even have to finish; the project can flounder and die days, weeks or months down line. As long as you grow from it, it’s still a success. And above all, side projects should be fun.
Shouldn’t a good job nullify the need for side projects? Not exactly. Even with the best jobs, your personal growth goals are never perfectly aligned with the company you work for. And some work, even with the best intentions, can get stuck in a boring, repetitive rut. A strong side project provides an opportunity to escape that.
At the very least, even a so-so side project teaches you something new on your own timetable. And at its best, side projects can establish your “niche” as a designer or developer, a critical way to stand out from your tech peers. They did for me; three years at Gucci, my first formalized web job, pushed me most of the way. However, it’s my Hacker News and Rdio browser extensions on my own time, along with some minimal Tumblr themes, that confirmed my interests as a web developer on the very front of front-end development that often drifts into UX and aesthetic design.
Good jobs push your career far. Good side projects push it further. Make time and a commitment to both.
Developer Mark Llobrera over at A List Apart gives advice for successfully integrating new web design and development techniques on new projects:
Look at the projects you have on the horizon. Think about the portions of your workflow that you want to improve, and pick just one of those things to introduce into your project. Why just one? It allows you enough space to experiment without endangering your project.
A mentor of mine once told me that programming (and especially programming for the web) boils down to reducing the number of “unknowns” on a project to a manageable number. One is fine, two is a stretch, and three is asking for trouble. If you think exploring HTML/CSS wireframes could have a positive impact on your work, introduce just that one thing. Most projects have enough built-in friction without adding or changing multiple processes at the same time.
I share code snippets all the time with both coworkers and students in my classes. The main Gist page on Github makes it easy, but there’s no substitute for the raw speed of this Alfred extension. I just copy the code block in question, type my Alfred shortcut, and a moment later a link to the Gist is copied to my clipboard. Very useful.
We’re technically two months past the exact anniversary, but it’s worth a look back at a few images from what remains a groundbreaking, highly influential film.
Craig Mod:
When we explore new ground (or re-explore old ground, forgotten ground) in new mediums, we often find it necessary to swing the design and interaction pendulum to the baroque side of the scale. We do this to see what “too much” feels like in order to understand the edges of “enough.” We saw this happen with iPad “magazines.” We saw this happen with “Snow Fall.” “Snow Fall” was less about what felt natural in a web browser or what was best for the story, and more about what was maximally possible in a web browser. The experiment just happened to be attached to an article.
Great storytelling is not about maximizing technical possibility.
Spot on.