Posts Tagged: development

Git: the safety net for your projects

Very solid mini intro to Git by Tobias Gunther over at A List Apart. You can find this content virtually anywhere by running a simple Google search, but Tobias makes a stronger case. First he succinctly lays out the reasons why Git is such an improvement over older repository systems like Subversion. There’s also some great use of visuals here to lay out what happens during core commands like ‘git reset’ and ‘git revert’.

Can email be responsive?

Jason Rodriguez, writing for A List Apart:

Just like with responsive websites, there are three main components of a responsive email: flexible images, flexible layouts, and media queries.

The only difference between the web and email is in how these three techniques are implemented.

In email design, we have a limited subset of HTML and CSS at our disposal. We can’t rely on properties and values that designers use for responsive sites on the web; margins, floats, and ems don’t work in many email clients. So we have to think of workarounds.

Frankly before this post I considered “responsive” email as something of a lost cause. But there’s a lot of strategic, well explained code examples here that make me want to revisit the emails we regularly send out as part of our day job. At the very least check out Jason’s solution for flexibile images which has a very clean HTML and CSS-based solution.

Conquering the command line

I find a surprising number of otherwise skilled web developers that still have trepidation around the command line. I’m no expert myself, but a few of the basics, especially pertaining to grep, can really do wonders when you’re in a pinch in the middle of a development session.

Mark Bates has written a excellent book on the subject; I’ve already read the first two chapters and like what I’ve read. It’s easy to follow along and comprehensive. You can read the entire book contents online or purchase an ebook, screencasts, or a physical copy.

On power and responsibility

Other speakers from the Fronteers web conference were solid, but Robert Jan Verkade’s talk on work and the general future of the front end web industry was my favorite. Great work on some really unique slides as well.

From the start, signs of trouble at health portal

I enjoyed this New York Times A1 story on the health care exchange web portal launch; it highlighted a lot of problems that can plague any tech launch.

But Mr. Chao’s superiors at the Department of Health and Human Services told him, in effect, that failure was not an option, according to people who have spoken with him…Former government officials say the White House, which was calling the shots, feared that any backtracking would further embolden Republican critics who were trying to repeal the health care law.

Put politics aside. It’s a classic case of inflexible business requirements smashed up against mounting technical problems. Many of us have been there, and the results are rarely pretty.

Nor was rolling out the system in stages or on a smaller scale, as companies like Google typically do so that problems can more easily and quietly be fixed.

Massive release with little fallback or rollout strategy? Recipe for disaster.

Others warned that the fixes themselves were creating new problems, and said that the full extent of the problems might not be known because so many consumers had been stymied at the first step in the application process.

Sounds like there’s not enough load testing and QA isn’t thorough enough to catch regressions. Yikes.

Why talented creatives are leaving your shitty agency

Keeping the trend from yesterday on bad work practices, designer Murat Mutlu:

Ahhh working til 9pm several days a week, it’s just the agency way of life right? Wrong, it’s bad management.

Tell your account managers (or yourself) to stop selling things that can’t be completed unless we work ourselves to death. I’ve seen people strain their health, relationships and family lives for what? So a deodorant can get more brand awareness? So that we can meet the unrealistic deadline you promised whilst trying to win a pitch? Or so a client can get dozens of mockups before they go on holiday?

This is advertising we’re talking about, not some higher calling. Everything we make is forgotten about in 6 months. Who gives a shit?

This is a mantra that could be extended to a lot of other industries as well, especially web and tech agencies.

Five tools for analyzing dysfunction in engineering culture

Author “Shanley” on Medium:

What about when we reward acts of heroism — recovering from severe outages, working unreasonable hours, emerging triumphant from a death march? When such acts of heroism are very visible and rewarded, do we end up with a situation where people are incentivized to manifest the very conditions of catastrophe that allow them to be heroes? At what point are we actually incentivized to create unrealistic deadlines, work at an unsustainable cadence, even cause production issues?

How to work with engineers

Designer Julie Zhuo:

If you give an engineer a design to build but you’re not confident how well it’ll work out until you get to play with the implementation, make sure you let them know that there’s a good chance things will change. Nothing is more annoying to engineers than staying up all night to finish an implementation only to get a memo in the morning that Whoops! The whole design has been transformed! And now they’ll have to throw away all that production-quality code they put painstaking attention into.

A thousand times this. Having worked on projects on both design and development, this point has come back to bite me personally quite a few times. If you’re a developer, make sure you’re clear on what stage the design is at.

Dropbox is a Git remote

I’ve seen hints at this over at other posts, but developer Rob Stinogle gives the best explanation I’ve seen of how to use Dropbox as an effective Git remote repository. It’s no GitHub, but for a private project where you’re the sole contributor, it’s pretty slick, not to mention free (assuming you have the Dropbox space) and secure.

Coding horror: buying happiness

Web developer/designer Jonathan Christopher:

We can’t help but to be influenced by headlines like Instagram getting bought for $1B. As ridiculous as that is, as much of an outlying circumstance it is, we can’t help but to want something like that to happen to us. Seeing something that ridiculous happen almost makes it seem like “small” dreams of one day getting a $1M payout that much more realistic, almost deserved in some way.

Ultimately it seems to me that big payouts have become the definition of success in our industry, and to be blunt I think that sucks.