Items tagged work

It's becoming a cliche these days to talk about the overwhelming pace of life, the combination of stress, overwork and information overload that assaults us every day, but sometimes we all need to slow down.
It’s good to take the opportunity to clean up your code as you go along, especially on big projects that will be maintained for a while. After all, the chances that you'll go back and fix those little things later is pretty slim.
Clients aren't stupid. OK, well some of them are. But, much as designers and developers love to think they are cleverer than everyone else, the people who hire them are not a bunch of useless morons. Your clients aren't stupid. They just have a different skillset to you.
Imagine you're going away on holiday. You decide where to go. You book a hotel. You book flights. You decide what you're going to take. So you make a list. Then you take the things on the list, and you put them in the suitcase.
Very often, junior colleagues ask me what they should do in a particular situation. Very often, to the point where I feel like a broken record, my answer is "Use your judgement”. This is partly because I don’t have as much time as I’d like to guide them through how I would approach the situation, but mostly it’s because I want them to be able to figure it out for themselves.
We need new mental models for modern communication methods. Think of instant messages like post-it notes.
Some lessons learned from cycling that can be applied to project management.
I spend a lot of time working. Too much time. I go home and I'm exhausted, and still I'm thinking about work. I don't get round to making plans to have a social life, because I work so much. And I'm not the only one. As Jeremy Girard and Yiannis Knostantakopoulos have both written recently, too many people in the web industry push themselves too hard at work.
Sometimes I think there's too much democracy in the workplace, and that what we need is benevolent dictatorship. There's too much taking account of how everyone feels about an issue, too much talking around the issues, too little action. In short, too many meetings.
My employer recently rationalised job titles, so I went from being a Project Leader to a Software Engineer Lead. I wouldn't mind, but I'd only just got round to changing my email signature. Previously I'd been a Developer. The new title sounds very grand, although in our company it is more junior than senior software engineer. Another colleague who does more or less the same thing, and is at the same grade, is a Front End Consultant.

Pages