Slashdot Mirror


How To Behave At a Software Company?

dawilcox writes "I'm a recent grad and am going to begin work at a software company. I want to make a good impression on my boss and coworkers. I know that performance is usually tracked, but there are also innate personality traits of good software developers that bosses just want to have around. What are those personality traits? What should I be trying to do in order to make a good impression on the people at my work?" (Appropriate side question: What behavior traits would you like your co-workers to exhibit?)

53 of 842 comments (clear)

  1. Good hygiene, don't be a know it all. by Anonymous Coward · · Score: 5, Insightful

    Good hygiene and refraining from acting like a know-it-all are my two best pieces of advice. Nerd types are often (myself included) poor at those two things.

    1. Re:Good hygiene, don't be a know it all. by russotto · · Score: 5, Funny

      It's an absolute travesty that you need to point out things like "have good hygiene". Everyone should have good hygiene. If you don't, you should probably kill yourself.

      That's going a bit overboard, and won't work anyway; dead bodies are quite unhygienic. WASHING yourself (i.e. showering -- use soap and shampoo) and brushing your teeth (toothpaste: tastes bad, works good) are the two most important things you can do. Put on clean clothes after showering; this generally means doing laundry now and again, but it's worth it.

    2. Re:Good hygiene, don't be a know it all. by Anonymous Coward · · Score: 5, Funny

      Good hygiene and refraining from acting like a know-it-all are my two best pieces of advice. Nerd types are often (myself included) poor at those two things.

      It's good to follow the dress code as well. I try to stick to an unbuttoned Hawaiian shirt, Bermuda shorts, sun glasses and a beer hat. On days when there are no meetings scheduled I dress more casually.

    3. Re:Good hygiene, don't be a know it all. by jetole · · Score: 5, Insightful

      Buy a book on corporate ethics. Read it twice and abide. Also buy a few Dilbert books and read them twice as many times as the corporate ethics books. If your not sure what decision to make in a situation, side with what the Dilbert books suggest over the corporate ethics books.

    4. Re:Good hygiene, don't be a know it all. by StrategicIrony · · Score: 5, Informative

      Bullshit.

      I have a co-worker who constantly pulls the "dude, RTFM" on everyone like he knows the answer. But when you pin him to the wall, frankly, he constantly doesn't.

      He frequently chortles when someone asks a question "dude, didn't you learn this in 4th grade?" but he then gets the same thing wrong the next time he has to do it because he can't ask the same question (having teased someone for asking it before).

      Knowing a lot is very different from being a jackass, which is what is implied in the GP's answer.

      Asking credible questions incorporating the previous steps you attempted to answer your own question gains you a lot of support and will make you a wiser person in the long run.

      Simply being a turd and thinking you already "know it all" just impresses people who don't know any better. Those who do know just roll their eyes and quietly check you off in their head as a know it all turd.

    5. Re:Good hygiene, don't be a know it all. by Eric52902 · · Score: 5, Interesting

      Won't this just leave me with a broken spirit gaming the system while working for a know-nothing boss who makes ridiculous requests and sets impossible deadlines in a dead-end job?

    6. Re:Good hygiene, don't be a know it all. by jetole · · Score: 5, Insightful

      See? You're already half way there.

    7. Re:Good hygiene, don't be a know it all. by Yvanhoe · · Score: 4, Insightful

      Knowing a lot is very different from being a jackass, which is what is implied in the GP's answer.

      That's actually a very good way to spot knowledgeable people. When you discuss something they don't know very well, they will ask you a lot of questions and not fear looking ignorant. You can bet that these types of profile know a lot more than others.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    8. Re:Good hygiene, don't be a know it all. by shiftless · · Score: 4, Insightful

      The end result of this is that I give him very quick, superficial advice, so that he, and the pen, will go away.

      A better idea would be to tell him to quit clicking the goddamn pen.

    9. Re:Good hygiene, don't be a know it all. by Hal_Porter · · Score: 5, Funny

      Naah, *never* stand up for what you believe in. Software is about passive aggression. Rather than telling someone to stop clicking, spend the afternoon arguing about why you won't tell him on Slashdot.

      People that stand up for what they believe in a trouble makers. We need people people in this team. Oh, and I'm going to need you to come in on Saturday. Remember what I just said. Slashdot isn't blocked by the corporate firewall BTW.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    10. Re:Good hygiene, don't be a know it all. by omglolbah · · Score: 4, Informative

      You might be surprised how hard it is to break such a habit.... Speaking from personal experience it is a lot harder than one may think.
      Reminding the guy that he is doing it would be the considerate thing to do. If he doesnt realize he is doing it then he cant at the same time be inconsiderate ;)

    11. Re:Good hygiene, don't be a know it all. by Tack · · Score: 4, Insightful

      +1. I've noticed that the people I respect the most are those who will honestly say "I don't know" when they actually don't. Generally the more intelligent and rational people will start dropping qualifiers left and right when talking about something they're not deeply familiar with.

  2. Lunch by Anonymous Coward · · Score: 4, Funny

    Do not bring any food containers that smell like something died inside to work and eat it at your desk.

    1. Re:Lunch by __aasqbs9791 · · Score: 5, Funny

      Also, though this may be a catch-22, don't bring live things into work to eat either.

    2. Re:Lunch by jc42 · · Score: 5, Funny

      Do not bring any food containers that smell like something died inside ...

      But, but ... Almost all my food consists of something that died.

      Yeah, there are exception, like the lettuce, tomato, etc., that are technically still alive. But, for example, the bread was made from a pile of baby wheat plants that were ground up (while still alive), then mixed with live yeast and a few other ingredients, then baked at a temperature guaranteed to kill everything in the loaf. Then we slice that up, fill it with slices of dead animals and other things. Only the lettuce leaves and the seeds inside the tomato slices are still alive; the rest is quite dead.

      I've found that people tend to think that such food is very "fresh", whatever that might mean, but they're clearly wrong. It's mostly made up of things that have died in the recent past. Some of them, like the baby wheat plants, died a rather awful death by being tossed live into a grinder. Others, like the yeast in the bread, died a horrible death in a bath of steam slowly getting hotter.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    3. Re:Lunch by Kjella · · Score: 4, Informative

      And going back on topic, talking about your food like that over lunch is a big NO.

      --
      Live today, because you never know what tomorrow brings
    4. Re:Lunch by Peach+Rings · · Score: 5, Funny

      My advice: Do not drop references to literature you've never read.

    5. Re:Lunch by __aasqbs9791 · · Score: 5, Funny

      That certainly would be a white whale, to be sure!

  3. Attitude by ShakaUVM · · Score: 5, Informative

    Be confident without being overconfident.
    Know how to communicate and also when to leave other people alone.
    Don't be too pessimistic or too optimistic when setting goals.
    Don't be a pushover, but don't be a dick, either.
    Be productive, positive, and competent.
    Always work to improve yourself.

    1. Re:Attitude by nmb3000 · · Score: 5, Funny

      Now we see why they say, "Go not to Slashdot for counsel, for they will say both yes and no."

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
  4. throw fits over minor things by convolvatron · · Score: 5, Funny

    stop bathing
    be awkward around the opposite gender
    come in at noon and leave after midnight
    be extremely condescending towards anyone at the company who is not an engineer
    never admit that anything is your fault
    drink 20 cans of free soda a day
    claim to be a libertarian if you dont already

  5. Re:notepad.exe by yup2000 · · Score: 5, Informative

    Also, read this: http://samizdat.mines.edu/howto/HowToBeAProgrammer.html

  6. Re:Advice, Dawg by Culture20 · · Score: 5, Insightful

    Eat lunch by yourself so that you won't be obligated to reveal personal information.

    Quickest way to alienate yourself and become first on the chopping block. If everyone eats lunch in, bring your lunch too. If everyone eats lunch out, go with them. If you can't afford to eat out, make an effort; suggest Taco Bell, letting the gang know you're strapped for cash but trying to be part of the group. You're not obligated to reveal personal information at lunch, but in my experience, people who ignore any and all lunches with coworkers are viewed as snobbish loners, and their work ethic seems to be the same (they are the people that ignore meetings, ignore policies, etc).

  7. Woah by Puff_Of_Hot_Air · · Score: 4, Insightful

    Am I glad that I don't work with you! "I'm here to work, not talk". Ever hear of the concept of colaboration? You know, working together as a team to achieve a common goal? Normally involves this thing I like to call "communication", you do it with your mouth. The advise on avoiding gossip is good, but the rest of your post smacks of some severe personality problems. Many of my co-workers are now friends, and this is a good thing! Lifes too short to be the "lone wolf". As another counter-point, you will never get anywhere if you don't socialize. It's half gaining peoples respect for your technical ability, and half gaining their trust because they know you. Get your head out of your arse, and join in!

    1. Re:Woah by Anonymous Coward · · Score: 5, Insightful

      If the "talk" is about work the "talk" is work. If the "talk" is about bullshit the "talk" is talk.

      "Lifes too short to be the "lone wolf"."

      Lifes too short to listen to bullshit.

    2. Re:Woah by amRadioHed · · Score: 5, Insightful

      Completely right. You can socialize with your coworkers without engaging in gossip and other destructive stuff.

      The concept of keeping your work separate from your life is BS. Your work is a big part of your life. You spend more time with your coworkers than with your family and significant others so you're just setting yourself up to hate your job if you avoid building relationships. I've had some annoying coworkers and I've had some great coworkers that have become good friends both inside and outside of the office. If you're office discourages you from having some fun during the day with your coworkers then I'd look for another place to work before you burn out.

      The important thing is that while you can control who you hang out with after work, you don't get to control who you work with. Show the annoying guys in the office the same respect you give the coworkers who you are good friends with.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    3. Re:Woah by kklein · · Score: 5, Interesting

      The concept of keeping your work separate from your life is BS.

      Hear hear! Your coworkers are a part of your life. They are your family at work. Just like your family at home, you weren't allowed to pick them, but you're stuck with them, so you need to learn how to like them.

      I've lived and worked in Japan for most of my working life, and I just have to say that most places here get that right. Westerners wonder why Japanese workers are so loyal to the company, and there are a lot of reasons, but one of the strongest emotional/psychological ones is that many places really try to foster a real kinship. You very well might think that Kinoshita-san from 2 desks over is a jackass, but when push comes to shove, he's your jackass. Also, thanks to the boozy parties the company throws (that everyone pays for equally), you've chatted with him over beers and know that he is a super-involved dad who takes his kids out on the skiff to go fishing every weekend. You can't see him as just a jackass anymore; now he's a neat dad who happens to be a jackass at work.

      At first, I resisted this culture with all my BS American individualist might, but before long I came to get it. They aren't forcing you to go to the party because they want to see what kind of stupid thing you'll say when you're drunk; they want to hang out together, and if you don't go it'll be a bummer for everyone. It's not a trick. People actually want to get to know each other. They probably won't be BFFs or anything; and the relationship will probably disappear if you transfer to another department or office, but for the time that you work together, you're doing it with people you know, and that makes all the difference in the world. When Sayama-san is going through a tough time with her husband, you cover for her--not because she's having a hard time with her husband, but because she's Sayama-san. And Sayama-san is having a hard time with her husband.

      Finally, though, so much of this is predicated on the assumption that you're not going to be fired at the drop of a hat with a simple "oops, we can't afford so many people; bye." But that's another post entirely (and again, not really a socialistic post--one about not handing so much goddamned money to the people at the top so you don't have to panic every time the market changes, because you have money in the bank and tons of wiggle room in the budget).

  8. Re:Advice, Dawg by EEPROMS · · Score: 4, Interesting

    Eat lunch by yourself so that you won't be obligated to reveal personal information.

    As a branch manager in an IT company this is bad news to me, it tells me employee in question is not a team player shown by their inability to communicate well with others. IT is about the flow of information and team work not about building walls. The best advice I can give anyone just starting a job is to not to form opinions and listen.. Also do not try and show off as this may mark you as being insecure. So on your first day take a note book and use it as this will tell your employer that you are serious about your job. Last but not least "be yourself"

  9. Re:Advice, Dawg by MoeDrippins · · Score: 5, Funny

    Suggesting Taco Bell is ok... it's the aftermath that can be alienating.

    --
    Before you design for reuse, make sure to design it for use.
  10. Re:Advice, Dawg by g33korama · · Score: 5, Interesting

    Uh, last software company I worked for and ate by myself... they thought I was anti-social and booted me. I'm like you though, I hate office drama so I avoid it like the plague, unfortunately... in an ironic turn, by not socializing to stay away from drama, you unfortunately can create it and draw attention to yourself.

  11. Even balanced by HTMLSpinnr · · Score: 5, Insightful

    Some random thoughts - I'm a Systems Admin/Engineer by trade, but have spent some time in the Manager's chair as well. Here's some thoughts that would have helped me for my first real job (i.e. why didn't someone tell me):

    Don't act like a know-it-all, but don't be afraid to offer a concise answer if solicited. Us nerds tend to LOVE to elaborate to "make an impression". The only impression is "Thanks, now how do I shut this guy up?".

    Don't be afraid to challenge your peers when your approach may be better, but know when to back down when you're out-numbered.

    In a cubical farm, your voice or other odd noises carry much further than you think. Same applies for the office restroom.

    Speakerphone is a privilege reserved those with an office and a closed door. (Ab)using speakerphone (esp. loudly) in a cubicle will earn many more enemies than friends. Consider a headset if you're going to be on the phone a lot and need to type or do other things with your hands.

    Learn and understand your company's core values. Chances are, you hold some of these yourself or you wouldn't have been hired (at least by any competent manager). These values will help guide your management team's decisions, just in case you question their motives.

    If you lied on your interview, you'll be quickly found out the moment you submit your first program. If it's a serious lie that you can't lie your way out of again, don't even bother showing up for your first day.

    Learn how to comment your code, but don't do it so much that stripping them out strips 75% of the file.

    Use sane variables that someone else can maintain. "a, b, foo and bar" are not sane.

    Be willing to learn - always. This may involve learning OUTSIDE of your job as well.

    You will be required to understand the business to a degree that helps you develop useful code. Don't be surprised if your first few weeks on the job involve training that seems initially pointless (stocking shelves, packing boxes, etc.). It will all make sense in the end, and may even help start the creative flow of "I could do that better".

    Innovate or get out of the way. Complacency often gets you fired.

    For some companies, continuous improvement is expected. For others, they prefer the tried and true. Don't be afraid to ride the middle if you aren't sure which one you're dealing with at first. Someone will set you straight.

    Make sure your line of communication with your manager is wide open. Understand his/her expectations and deliver on what's asked. However, if the expectations are completely unreasonable, have a backbone and ensure they know why you can't rewrite Linux in a day.

    This is hard at first, but employees who perform well need little management. Those who don't can expect constant management. Then again, some managers like to micro-manage anyway, especially their under-performers.

    --
    $ man woman *
    -bash: /usr/bin/man: Argument list too long
  12. A lot of common sense by Anrego · · Score: 5, Insightful

    There is such a wide variety of office "culture" that general advice is hard. I think a lot of it is trial an error.. you're going to at some point piss someone off or at least do something/say something and hate yourself for it. When you do, just try and learn from it and minimize the damage as best you can.

    I guess one thing I'd recommend though is that while you (being fresh out of school) probably have all kinds of great ideas on how you're going to revolutionize everything, you have to accept that companies can't just change their process with ever new graduating class. Not saying you shouldn't try to bring in new ideas.. but don't be "that guy" who spends every meeting talking about how the way things are being done is totally wrong and how pair programming and executable UML would be perfect. The guys with 20+ years of experience may be set in their ways.. but they also (probably) have a lot of experience seeing projects succeed and fail.. having some new kid throwing ideas from a textbook at them can ruffle some feathers.

    1. Re:A lot of common sense by coryking · · Score: 4, Insightful

      It isn't they are set in their ways. It is that they've seen shit fail and know the warning signs. Your totally awesome idea about pair programming (hey, it says right in the XP book, they can't lie) might not be appropriate because XYZ. Your rad idea of cloud computing might be friggen awesome (everybody is doing it, you stone age losers) because I don't know, gee, you might have these pesky HIPAA regulations, whatever those are. Your idea of rewriting the codebase because the code is U.G.L.Y. might be totally awesome because you can totally do it in a week, but gee, the shit we have now works and it would take way longer than you estimate because, gee, that code has been around for *years*. Lord knows what kind of shit when into it to make it work--that code has history man.

      Bottom line is, the most important thing is to admit you do not know jack shit. Better to admit you don't know anything because, brother, we all don't know shit--even people who have been there, done that. The people that truly do not know anything tend to be the ones that always brag about knowing everything. I have yet to meet a person who brags about knowing stuff that actually knows stuff.

  13. Re:Advice, Dawg by CyberSnyder · · Score: 4, Insightful

    Good way to network. Learn to network, it's as important of a skill as your technical expertise.

  14. Re:Advice, Dawg by Skreems · · Score: 4, Insightful

    As far as I've seen that kind of behavior will only get you so far. At some point you have to be able to voice an opinion, publicly, and then follow through on it. Otherwise you're going to top out at some point. Even if you limit that advice to just the social stuff, workers who act as a social nexus for a team are valuable in a completely different sense than skilled engineers. I don't know why you'd intentionally go out of your way to avoid all aspects of that role.

    The best advice I can give is, ask questions. Ask everything you can think of. It doesn't matter if it's something you need to understand to do your work for the next two weeks, if somebody who's been around longer than you is willing to explain something to you, take as much of their time as they're willing to give. Some people avoid asking questions because they think it makes them look weak. It doesn't. It just makes you look stubborn, and you're going to get passed right and left by people who aren't afraid to admit they don't know things.

    Once you understand enough start proposing fixes, and follow through on them. Don't be an ass about it, but make sure you keep the work you're doing as an active part of the conversation from day to day. It helps you because people will notice the things you fix, and it's a good way to get other people to chip in on parts of the fixes as well. If you can demonstrate that you're able to help steer the group in a positive direction, even in just one aspect of many, it'll go a long way. Remember you're here to build stuff, and that includes the team and the process, not just sitting in a corner turning out your coding assignments on time.

    --
    Slashdot needs a "-1, Wrong" moderation option.
    The Urban Hippie
  15. easy. by Anonymous Coward · · Score: 5, Funny

    innate personality traits of good software developers that bosses just want to have around.

    Have a positive can-do attitude, especially whenever the boss asks you to work evenings and weekends. What bosses love to have around are smart people who get things done and don't mind working 60 hour weeks standard (up from there whenever anything surprising happens or is badly panned) for a 40-hour salary.

    Appropriate side question: What behavior traits would you like your co-workers to exhibit?

    A little self-respect, and enough spine to refuse to be exploited into giving up your personal life to further your bosses ends. Every time you work long hours, you create expectations that your co-workers should work long hours too, and they will despise you for it.

    1. Re:easy. by sonamchauhan · · Score: 4, Insightful

      Someone mark this funny please, not interesting

      To answer: if expected to work weekends or evenings also expect time in lieu when things are slow. If this is not a given, raise it with the boss, but privately. Also, convey the impression you are happy to work overtime, but for important stuff - not a presentation the boss must make to his boss the next morning, but didn't plan for. Play this by ear, but convey the general idea so they are respectful in their demands on your time.

      Plan on starting your own little business on the side (that does not impinge on your company's turf or time). Contribute to open source projects, keep your resume updated. Spend money on upgrading your own skills - buy books, sit for certifications, and if possible get your company to front up money. SAVE MONEY!! Once you can afford to, buy a house. Marry someone sensible and like yourself.

    2. Re:easy. by ultrabot · · Score: 5, Funny

      SAVE MONEY!! Once you can afford to, buy a house. Marry someone sensible and like yourself.

      And don't forget the sunscreen.

      --
      Save your wrists today - switch to Dvorak
    3. Re:easy. by Skal+Tura · · Score: 4, Insightful

      Working 60hour weeks for 40hour salary? You got to be insane.
      That only helps create environment for abuse of the greatest asset a software company has. In my experience how much you work means shit, infact if you work longer hours you will have LESS respect from management, even if you are not a push over and get paid +50% extra hourly salary for those hours.

      IT employees are probably the most abused, neglected bunch of employees in the world just because of that kind of an attitude. Good coders are actually highly creative, yet engineer like while sometimes code is just as much art as engineering, if not even more about art than engineering to create that very simplified, easy to maintain system. Simple code pretty much is an art, to see the connections and make it so simple. To be creative you need good environment, but promoting abusive behavior like working 50% more for the same salary is going to just make things worse, it's like saying "It's ok to whip my back bloody to get more productivity out of me, and ruin my personal life".

    4. Re:easy. by shiftless · · Score: 5, Interesting

      A little self-respect, and enough spine to refuse to be exploited into giving up your personal life to further your bosses ends. Every time you work long hours, you create expectations that your co-workers should work long hours too, and they will despise you for it.

      My first (and last) experience in a cubicle farm was a pretty shocking one. We had three guys doing the work of 10. It was extremely stressful. My co-workers would routinely work 60-70+ hours a week, if not in the office then at home with the laptop dialed in. I mean this job was practically their entire lives, and for what? $35k/year? Fuck that. When 5 o'clock rolled around I rolled out. The boss called me up one Friday evening wanting me to come back in and restart a data conversion process that had failed (due to programmers not having the file structure figured out completely) and I said no. I'd rather stand in the sun and dig ditches all day, regardless of pay, cause at least ditch diggers know when they get to go home and forget about work. They called some other unlucky fool in to do the job and nobody ever said a word to me about it, but I could feel some people didnt like it at all. Fuck them. My life is too valuable to be spent slaving away for someone else's benefit.

    5. Re:easy. by cas2000 · · Score: 4, Insightful

      IT employees are probably the most abused, neglected bunch of employees in the world just because of that kind of an attitude.

      yep, they certainly are... ...right after factory workers, checkout chicks, shop assistants, office clerks, [...], third world sweat shop laborers, and pretty much everyone else in the world below middle and senior management in large corporations.

      sure, IT workers get shafted by their employers making unreasonable demands. but there's a huge difference between someone making 60-90K per year for physically undemanding work who has the skills to get a similar or better job pretty nearly whenever they want, and someone working a physically demanding minimum-wage (or lower if they're in a seriously exploitable category like "immigrant" or "stupid") shit job that barely pays enough to live on, let alone save anything to improve their situation. or worse, someone working for a $1 a day to make t-shirts and other stuff that rich western programmers pay $40 or more for.

      so, while i know from personal experience just how much IT workers get taken for granted and ripped off, we're still MUCH better off than most.

      BTW, this is absolutely *NOT* saying "just put up with it and stop whinging" (i'm way too much of a socialist to ever think that exploitation of any worker is acceptable). it's saying "being outraged by it is sensible, but get a sense of proportion and lose the ridiculous exaggeration".

  16. wtf by LBt1st · · Score: 4, Insightful

    Be yourself, otherwise you'll come off as fake and no one will like you.

  17. First Day by BlueBoxSW.com · · Score: 5, Funny

    The first day, what you need to do, is find the biggest, smartest, most awesome software developer they have... and kick his ass.

    No one will screw with you after that.

  18. Re:Advice, Dawg by edivad · · Score: 5, Insightful

    If you are a software engineer, and you can't afford going out for lunch, you might consider the chance of having been screwed during the salary negotiation.

  19. Re:Advice, Dawg by mmmmbeer · · Score: 5, Insightful

    I agree. At one company that I worked for, there was one programmer who just never joined the group. He was a good programmer, and a decent enough guy, but he just didn't socialize. When the company started going under, and layoffs started, he was the first to go. I'm certain it was because the Powers That Were felt (correctly) that would have the least impact on morale, compared to firing any of the rest of us.

  20. Re:Advice, Dawg by __aasqbs9791 · · Score: 4, Interesting

    Here here, I agree whole heartedly with your modification (and everything else about the OP comment). I worked at a place a few years ago and since most of us didn't make all that much, we usually went out to fairly cheap places for lunch. One day several of us went out to a Mongolian grill over the river from work and on a spur of the moment I decided I could afford to pay for lunch for all of nine (I think) of us (it was about $55 IIRC). I didn't start out the lunch by saying I'd do it, and I insisted that no one pay me back. I was hoping it would help morale (it was generally okay, but not great sometimes as our bosses were slashing jobs left and right, while insisting each one was the last). It worked very well, and people started offering to pay for each other's lunch from time to time. Sometimes small gestures, especially when unexpected, can help relationships, if handled properly. I suppose YMMV of course, especially if you have a bunch of self-entitled people at your work.

  21. +1 what the others said, and my two cents worth by TheGrumpster · · Score: 5, Insightful

    Lots of great stuff here already, but as a corporate executive in charge of R&D, I'll put in my additional two cents worth... The first rule of business: don't take it personally. It isn't all fun and games. You're not there to make friends or have fun - you're there to do a job. Yes, ideally, on the whole, you should enjoy it - if not, you're in the wrong line of work; but there will be times that the job sucks ass no matter where you work. There will be assholes that rip on you, rightly or wrongly. Don't take it personally. Keep your spirits up and focus on the work at hand. This will get you way ahead of the rest of the crowd. Act as though time is of the essence - it is. You'll be amazed at how quickly you go from being a green kid out of college to being an old geezer like me. Don't waste your time on piddly bullshit. Work your ass off at all times - not for the company's sake, but for yours. Your life is ticking away by the minute - the only reason it doesn't seem that way is because you are young. Youth is wasted on the young - the sooner you understand why, the better off you'll be. Don't be afraid to make mistakes. Take on the hardest work you can handle, then ask for something even harder. You don't grow by taking it easy; strength comes from adversity, not comfort. If you're comfortable, you're dead. Ask for help when you need it - there is no shame in admitting that one is in way over one's head; real achievers always are. Good luck!

  22. Re:Advice, Dawg by scotch · · Score: 5, Insightful

    Ironically, since he was the first to go, he probably got the best severance deal and a chance to look for a job before the rest of you guys flooded the market with your down-with-a-sinking-ship stench.

    --
    XML causes global warming.
  23. A few thoughts by MichaelSmith · · Score: 5, Insightful

    I have been a team leader at different times so maybe I can give the bosses perspective:

    • Show up. If you get in late, then leave late. I never expected people to work extra hours but it is good to know when to expect a person in the office.
    • Be a "can do" guy. Don't say "no, I can't do that" when asked to do a task. If you have to research something then say so. If the place is well organised there might be resources you can use anyway.
    • Develop your skills. Its good to see people improve. Nobody has all the knowledge. If you are working on stuff outside work like OSS software then talk about it with your co-workers.
    • Display an interest in technology. If you are in a technical field you should have an interest in technology, as opposed to jumping up in to management at the first opportunity.

    There is a lot of overlap in the above. It comes down to "don't be a dope". Posting here suggests to me that your biggest problem is a lack of self confidence. Work on that by being open with people. Maybe by telling them you were the guy who posted "How to behave in a software company" on slashdot. That'l get some laughs.

    The only other thing is to look out for sociopaths. Don't assume everybody you work with has a perfect personality. In practice a great many do not. I can't help you deal with these people. Sometimes they are hard to spot. A good skill it to learn not to reply to trolls. Don't let people wind you up. Getting somebody angry is a great way to beat them at something. If you are good at something you will likely get picked out for treatment early on if this kind of person is around.

  24. Re:Advice, Dawg by kjart · · Score: 4, Insightful

    So, your advice is to be a quiet, passive-aggressive loner that keeps themselves apart from the group? Please do your coworkers a favor and quit now.

    Seriously, though, the cynical answer is always that you aren't at work to make friends, but in my experience work is so much better when your coworkers are indeed friends. I worked several years in tech support while in university and the only thing that made it bearable was the people I worked with. Obviously, you can go too far - you don't want to spend all day talking to people and not get your job done - but the idea that you shouldn't be friendly since you're at work is absurd.

  25. Dental hygiene by Anonymous Coward · · Score: 4, Informative

    I know this was mostly a joke, but here is a serious bit of advice on tooth care.

    0) Floss at least once per day. If you need an incentive, here is one: your breath will smell much less bad if you do this. I don't really like to floss, but I absolutely hate my breath after even one day of skipping the flossing. It makes a difference.

    1) I highly recommend a good electric toothbrush. I use a Sonicare, but presumably there are other good brands too. I just happened to start using a Sonicare one month before a cleaning/checkup at the dentist's office; the dental hygienist took one look at my teeth and said "I can already tell you are doing something different, and whatever it is, I like it." I have noticed that tooth cleaning takes less time and is less unpleasant now that I have started using the electric toothbrush. There is just less tartar attached to my teeth. Also, my gums are improved; I'm not sure what the "pocket depth" means with gums or why deeper is worse, but mine improved after I started using the electric toothbrush.

    2) You might even want to use a flouride mouthwash. I use Act Restoring (stupid name, but the one I use is the one that is alcohol-based; the other Act has no alcohol). I figure killing germs in my mouth is always good, and the flouride can't hurt.

  26. Re:Advice, Dawg by im_thatoneguy · · Score: 4, Insightful

    Lesson 1 in networking: make everyone look good. You don't have to do it at your own expense but when people are thinking about who they want to work with who are they going to pick the guy who always takes all the credit or the guy who makes them look great in front of their bosses?

    We're all geeks here: look at it like statistics. Advancement is as much luck as it is talent. If you are in 8 people's favor the chances of one of them getting into a position to return the favor is far greater than you yourself getting noticed.

    As to the original question it's pretty simple for me:
    1) Be competent. Nothing annoys me more than someone who doesn't know how to do their job and is a waste of space.
    2) Do your fair share.
    3) Be appreciative. If someone does something for you and you take it for granted, you probably won't see a lot of effort in the future on anyone's part.
    4) Be helpful. If someone is struggling due to no fault of their own, stop and offer assistance. If someone feels like they're drowning and nobody helps they will get resentful.
    5) Be pro-active. If there is something to be done. Do it. Keeping someone busy can easily become a full time job for a manager. If they're spending all day finding things for you to do then you're a burden. Don't be a burden.
    6) Be friendly. If you're a loner and don't participate then people will be far less likely to overlook #1-5. People always give their friends the benefit of the doubt.

    And of course Always Try To Make Everyone Look Good. Nothing will make you look better.

  27. Professionals have *standards* by thygrrr · · Score: 4, Funny

    Be polite.
    Be efficient.
    Have a plan to kill everyone you meet!