1. 5

    I don’t think browser shortcuts are on topic for lobsters.

    1. 3

      What follows is basically a rant about everything that’s wrong with a bad manager from a worker-bee perspective, not everything will be applicable to you but just take whatever you find interesting from this. Thanks a lot!

      Read “The Mythical Man-Month”, some managers still don’t get that you can’t grow a baby in 1 month by impregnating 9 women.

      When you consult someone technical for advise on something not your area of expertise, don’t just blanket accept the advice but try giving someone equally or more knowledgeable the premise and conclusion to test if it’s sane. Make sure no one suspects any trust issues, it’s just to avoid the whole “gee, hadn’t thought of that” situation.

      Don’t lose your cool, ever.

      Sometimes the best way to do a task is to not do it at all, the onus should be on the manager to figure that out.

      If you disagree with someone, let them have their say before you judge. Don’t be too quick to dismiss someone.

      Make your time as worthwhile as possible, a good manager has this trait and can inspire his team to do the same. Don’t just assume others can automatically do this (or can be trained to do this in a day), but rather lead by example (and care to explain yourself).

      Stay top dog. You need your metaphorical weight to boss people around, and you don’t need to be a d*ck to do this either. But put people on a pedestal and suddenly everything is jeopardised. Compliment peoples output, not how they produced it (maybe if it’s extraordinary but don’t let their ego become any bigger than yours).

      Provide people with context, it’s good to see how things fit into the bigger picture and makes the work seem more worthwhile (and thus exciting).

      Recognise people who are often used for consult may require more time to complete any given task.

      Ask people what they’re good at, often they’ll tell you whether they like doing that as well. Ask or gauge what sort of task they’re not as proficient with compared to their co-workers and try to not make them do those things. Also don’t make it known what your findings are, because that messes up the team spirit.

      1. 1

        This is possible with a bit of XML + XSLT (and stackoverflow)

        1. 2

          The object literal pattern only supports switching on strings, because only strings can be object keys. By contrast, JavaScript’s built-in switch statement can switch on numbers too. Though with JavaScript’s type coercion, maybe you could use strings like '39' as object keys and access it with the index 39, but that feels unsafe to me.

          1. 2

            It might “feel” unsafe, but it’s perfectly fine. Here, try this:

            var x = {"39": 13.37}
            print(x[39])
            
            1. 3

              I think just further demonstrates why people don’t trust Javascript: to many reasonable, seasoned programmers that shouldn’t work, but it does.

              1. 3

                This works because JavaScript converts the hash keys to string before using it as key:

                > a = 'key';  // String
                > b = 4;  // Number
                > c = {};  // Object
                > d = {};
                > d[a] = 1;
                > d[b] = 2;
                > d[c] = 3;
                > d
                { '4': 2,
                  key: 1,
                  '[object Object]': 3 }
                

                This means that even though you can use objects as keys, they will all translate to '[object Object]'.