Get flash to fully experience Pearltrees
The prerequisites for being a great manager are: Sincerely and deeply caring about your team and company. Having empathy, self-awareness, organizational awareness, perspective, maturity, and security. If you possess those characteristics, you can become a great manager in practice by doing the following:
The weekly bi-Romanarian/Cohenarian
Teachers teach and do the world good kings just rule and most are never understood —KRS-One, My Philosophy Artist: KRS-One Track: My Philosophy Album: A Retrospective Released: 2000 Label: Jive Records Most managers seem to feel that training employees is a job that should be left to others. I, on the other hand, strongly believe that the manager should do it himself.
When you base your life on credit and your loving days are done checks you signed with love and kisses later come back signed insufficient funds —Funkadelic, Can You Get to That Artist: Funkadelic Track: Can You Get to That Album: Maggot Brain Released: 1971 Label: Westbound Thanks to Ward Cunningham, the metaphor technical debt is now a well-understood concept. While you may be able to borrow time by writing quick and dirty code, you will eventually have to pay it back—with interest.
It’s just another mutherf*ckin’ day for Dre, so I begin like this No medallions, dreadlocks, or black fists Just that gangsta glare with the gangsta raps —Dr. Dre, Let Me Ride Artist: Dr. Dre Track: Let Me Ride Album: The Chronic Released: 1993 Label: Death Row/Interscope Lyrics At Opsware I used to teach a management expectations course because I deeply believed in training . In it, I made it clear that I expected every manager to meet with her people on a regular basis. I even gave instructions on how to conduct a 1:1 meeting so there could be no excuses.
[Update: in response to some of the comments here and on HN, I thought it might be worth updating with a note on my personal experience with Agile, which appears at the bottom of the post.] Agile (with a big 'A') has become so mainstream now that it has started to become the problem. An alarming number of people who espouse the virtues of Agile, and who quote the Agile Manifesto believe that Agile is a project management methodology, and that Agile really means SCRUM, XP, Kanban, and that it is embodied in the daily stand-up, whiteboards or writing requirements on post-it notes.
by Joel Spolsky Tuesday, August 08, 2006 Frederick the Great [PDF] : “Soldiers should fear their officers more than all the dangers to which they are exposed.... Good will can never induce the common soldier to stand up to such dangers; he will only do so through fear.” The Command and Control form of management is based on military management.
In her previous post, the Cranky Product Manager unloaded on Code Boys & Grils who don’t fix their damn bugs . She dropped the eff bomb and everything. Indeed! This post is the flip side. The developer’s point of view when faced with a nasty bug. And it’s an extremely well-written piece by a Code Boy who is a reader of this humble and cantakerous blog.
Editor’s note :This guest post is part of an in-depth series looking at the daily deal industry written by Rocky Agrawal , an entrepreneur who has worked on local products since 1995. Read Part I, Part II , and Part III also. He blogs at reDesign and Tweets @rakeshlobster .
(Photo: Stuck in Customs ) For the last two years, one name has come up again and again when talking with A-class start-up investors: Pivotal Labs .
My experience as a programmer has taught me a few things about writing software. Here are some things that people might find surprising about writing code: Averaging over the lifetime of the project, a programmer spends about 10-20% of his time writing code, and most programmers write about 10-12 lines of code per day that goes into the final product, regardless of their skill level. Good programmers spend much of the other 90% thinking, researching, and experimenting to find the best design. Bad programmers spend much of that 90% debugging code by randomly making changes and seeing if they work. A good programmer is ten times more productive than an average programmer.
I love programming. I can truly say that of all the things I enjoy, I enjoy programming the most. There's nothing quite like the feeling you get when you create something. Writing code is a lot like building your own little universe. When you build stuff, you're in complete control, and, no matter how hard you fight it, your code directly reflects yourself. If you write sloppy code, I can almost guarantee you'll be a sloppy person.
Copyright © 2001 Eric S. Raymond
Last month, I took a little break from all the hustle and bustle of the Internets and decided to focus on trying to get a better handle on my daily life. It included eating right, working out and, in short, decompressing. I was trying to use a month-long break to change life-long behaviors such as staying up late, working long hours and more often than not, eating erratically.
User stories are the basic units of work for Agile methodologies.
I recently finished 97 Things every programmer should know . Well to be completely honest I did skim over a couple of the 97, but all and all this was a very nice compilation of thoughts and topics about software development from very experienced authors. Well worth a read.
Don't have the time to read this: i'm coding ! ;) by May 12