In my experience, “full-stack developers” always translates to “programmers who can do frontend code because they have to and it’s ‘easy’.” It’s never the other way around. The term “full-stack developer” implies that a developer is equally adept at both frontend code and backend code, but I’ve never in my personal experience witnessed anyone who truly fits that description.
When every new website on the internet has perfect, semantic, accessible HTML and exceptionally executed, accessible CSS that works on every device and browser, then you can tell me that these languages are not valuable on their own. Until then we need to stop devaluing CSS and HTML.
I like Chris’s list of criteria for the nebulous role of senior developer:
- A senior front end developer has experience.
- A senior front-end developer has a track record of good judgment.
- A senior developer has positive impact beyond the code.
- A senior developer is helpful, not all-knowing.
- A senior front-end developer is a force multiplier.
Sometimes our job titles and distinctions feel like the plastic grass in a sushi bento; flimsy and only there for decoration.
This is relevant to my interests because I think I’m supposed to be a senior developer. Or maybe a technical director. I’m really not sure (job titles suck).
Anyway, I very much appreciate the idea that a technical leadership position isn’t just about technical skills, but also communication and connectedness.
When we boiled down what we’re looking for, we came away with 12 traits that divide pretty cleanly along those three areas of responsibility: technical capability, leadership, and community.
For someone like me with fairly mediocre technical capability, this is reassuring.
Now if I only I weren’t also mediocre in those other areas too…
Story of my life:
I have to confess I had no idea what a technical leader really does. I figured it out, eventually.
Seriously, this resonates a lot with what I find myself doing at Clearleft these days.
Hmmm …I think Jeffrey might have just given me my new job title.
This could come in useful for updating the Clearleft website.
This is absolutely delightful, nicely weird, and thoroughly entertaining.
Get out my head, Emil! This is pretty much exactly how I feel about my work, especially this bit:
In trying to be the best web developer I can, I feel a need to understand the web. That involves a lot of what some of my friends who are not in the web business think my job is about, i.e. “clicking on funny links all day”. I read copiously about new and old technologies. I bookmark them, I try to classify them, see them in the light of history as well as projected future. Follow up on them. Try them out. Even if they’re not specifically about what I do for a living, the nature of them might have a bearing on my understanding of how other people use the web.
Job postings that only use male pronouns.
See, this is why using “they”, while technically incorrect, can often be the least worst option.
The truth …it burns!
A hackweek project from Twitter employees to create the best/worst recruitment video of all time.
While others recall Steve Jobs’s legacy with Apple, Tim Berners-Lee recounts the importance of NeXT.
I like this way of whittling down potential candidates for the job: “To apply, check the HTTP headers.”
Cindy is now working for nclud. That's good for Cindy and good for nclud.
Early adopters of the iPhone now get a $100 of Apple Store credit. Nice bit of customer management.
Last.fm are hiring. If you're London-based and in the job market, I can think of a lot worse places to work.
Last.fm are looking for a designer. Want to be part of an exciting Web 2.0 startup without moving to the valley? Now's your chance.