Ask Slashdot: What Defines Good Developer Culture?
An anonymous reader writes "I'm part of a team of six people developing applications for mobile devices (Android & iOS). In our company, which consists of many teams responsible for 'classic' software development, business intelligence, virtualization, hardware, etc., we are kind of a small startup because we were the first to use agile methods like Scrum and we are open to new technologies and methods. Also, our team is pretty young — I'm the oldest at 30 years of age. We would like to further raise productivity and motivation, so we're currently collecting ideas about what makes a good developer/hacker culture, and how it can be improved in our team/company. These can be things we do ourselves, or suggestions we pass on to management. I would like to know: what, in your opinion, defines good, modern developer culture? What does developer culture consists of? For example, is it: clearly defined career opportunities? A geeky office? Benefits like trips to extraordinary conferences? Please let me know what you think."
Soon we'll be using rasberry pis bought with bitcoins in the year of the linux desktop.
To offset political mods, replace Flamebait with Insightful.
make sure bug reports have a "who's fault is this" section so you know who to blame. make sure everyone has to fill out a time sheet with their daily activities down to a 15 minute intervals. start every day with a meeting that's a half hour to an hour long so that everyone start work with maximum productivity in mind. make sure everyones personal phone is in a public list so you can call them up at any time and ask questions. oh yeah and a mandatory softball game every other friday after work, people love that, builds unity.
The solution is obvious: have a meeting to discuss the usefulness of meetings.
readily available supply of Nerf weapons
I've nothing to say here...
Agree with most of this - but I would also add variable width fonts to the list.
An emphasis on keeping high-quality & intelligent developers. Don't ever let intellectually lazy developers onto your team.
We have a solution for lazy developers. Well, a solution for the whole team. Keeps things simple:
We're adding a little something to this month's developer salaries. First prize is a Cadillac Eldorado. Anybody want to see second prize?
Second prize is a set of steak knives.
Third prize is you're fired.
When the foot seeks the place of the head, the line is crossed. Know your place. Keep your place. Be a shoe.
The solution is obvious: have a meeting to discuss the usefulness of meetings.
Yes but you can't rush right into a meeting like that. Often it takes four or five pre-meeting meetings before going into a meeting like that.
That describes pretty much every scrum retrospective I've been a part of.
Oh man! Hahaha! Whoosh on me! I laughed pretty hard when I finally realized that everyone was actually talking about sex.