3 ms·
#1 - You’re not smarter than anyone Stupidity is in no short supply ... I have faith in the people I work with, I always question my own assumptions, I always
by bad_user 15y ago
#1 - You’re not smarter than anyone
Stupidity is in no short supply ... I have faith in the people I work with, I always question my own assumptions, I always blame me first ... but beware of dumb people with strong opinions, as they will suck your soul out.
#2 - There is such a thing as a stupid question
The thing that pisses me the most is when newbies DO NOT ask questions, as if I would think less of them.
I'm always telling newbies -- "don't worry, I know you suck, everybody sucked at some point and I'm more interested in how fast you can learn".
You can also drive the learning process -- instead of giving your coworker/employee a concrete list of steps he needs to follow, give him links to documentation instead. That's far more productive and he'll be less likely to ask the same question twice.
#3 - Looks matter
Yes, if you're referring to the work you do. I like beautiful code.
This really depends on the work environment. In big corporations people get impressed by suits more than in smaller companies where everyday is casual Friday.
#4 - Know what you know and what you don't know
The more I learn, the more I realize I don't know shit.
Also, could this advice be any more useless?
#6 - Software’s primary function is to earn profits
NO, that's the company's primary function, and it's a freaking big difference, especially when you think about the laws of microeconomics.
#7 - Listen to people
In other words, behave like a human.
#8 - Have a presence
When I worked for the bigco, I preferred to get stuff done instead of going to pointless meetings. It worked great, and I got promoted in front of people that kissed ass.
32. Never Get Drunk At Work Parties
Lame. There's nothing like getting drunk shoulder to shoulder with the CEO.
33. Don't do things because they are cutting edge
Why? What's wrong with making a bad decision?
Before switching techniques, languages,
or anything else, carefully decide if it
provides a large enough benefit
And yet there are so many choices out there that many times it's best to just follow your instinct. Playing it safe is stupid and also irresponsible -- that's how companies still choose Java EE, that's how you end up with a mountain of crap (that nobody in particular can be blamed for).
...
Some pieces of the article are perfectly valid, but I can't help but wonder if those shouldn't be common sense for a properly raised 7-year old.
My number #1 advice I would give to newbies:
Stop giving advices
- 5hoom 15y agoMaybe I've spent too much time being brainwashed by FOSS advocates, but #6 (Software’s primary function is to earn profit) made my stomach lurch. I agree, profit is the _company's_ primary function. There are profitable companies out there who publish free software. Lets not go advising the younglings that the entire software world must be locked-up & proprietary.
- tenpoundhammer 15y agoIf a company is a software company isn't the goal of the software to create profits for the company? Even a company that provides free software needs to make money... One way or another. I'm confused on how this couldn't be the case? Also I don't think I mentioned locked-up or proprietary. I was hinting more that software decisions often had to fall in line with business decisions.
- azulum 15y agoi read #2, you know Only when you have exhausted all possibilities should you ask for help. and stopped reading. this is hands down one of the most asinine things i have ever read—though i don't doubt many feel this way. one of the purposes of being human is sharing ideas. in fact, it's the sharing of ideas that allow any of us to code. here's a ted talk http://www.ted.com/talks/matt_ridley_when_ideas_have_sex.htmlon http://www.ted.com/talks/matt_ridley_when_ideas_have_sex.htm... this very idea. on top of that, there are some that learn best in collaboration with others. if you ask me, not asking for help is one of the dumbest things you can do. maybe being self-taught has lead me to be naïve. if that's the case, i'm better off. edit: for some reason the link was bad, here's the youtube: http://www.youtube.com/watch?v=OLHh9E5ilZ4 http://www.youtube.com/watch?v=OLHh9E5ilZ4
- j_baker 15y agoI agree with literally everything you say except one thing (and boy is it a biggie). This really depends on the work environment. In big corporations people get impressed by suits more than in smaller companies where everyday is casual Friday. Just because you dress casually doesn't mean people aren't judging you based on looks. If anything, they're judging you more because they're seeing the real you. This is one point the OP is probably right on. People, regardless of the size of their employer, judge you from the standpoint of looks. It's just in our nature. To say that one can overcome this with simple coding prowess is incredibly naive.