Just because you are perfectly right... doesn't mean you aren't a complete and total asshole.
As a reformed asshole myself I can tell you that condescendingly pointing out the failures of your colleagues will not get you what you want. Specifically (and I'm assuming here that your goal is the same as mine) getting your colleagues to stop acting like self-righteous fucktards. Most programmers are convinced they are geniuses. This is crucial to understand if you wish to work with them and wish to get them to do anything at all.
I am ostensibly in a senior role in my day job and I do find many things these other programmers do... well... fucktarded. That is they are beyond retarded since a retard would know they are a retard or at least not entertain the delusion of superiority that a fucktard does. No my friends we need to call them fucktards because they are fucking arrogant in their belief of superiority. So I can't tell these geniuses to do anything. Nope. Not at all.
You need to use psychology on these fucktards. What you need to do is something Socrates used to do with his little fucktards that he taught. Ask questions. Since the genius/fucktard seems to know so much start by asking leading questions that will do one of two things... it will lead the fucktard down a road that will show you both how stupid he is (and you can pretend they figured it out themselves they love to take credit). Or it will show you where you were wrong... and that you were the fucktard.
Remember we are after end results. So we put aside lesser things (like pride) in the search for a greater goal which should be better software and the ability to make more of it. If you can psychologically manipulate an army of fucktards you will become fucking powerful. Much more fucking powerful than you fucking are on your fucking own. I wish you good fucking luck as I can tell by the response to your post that you are a fucking powerful personality and will definitely lead your own army of fucktards one day.
Hopefully when we meet on the field we can be allies and not enemies.
Well, the Hang-Glider guy was working in a romanticized way too if he wasn't slacking off completely.
I've done a little professional writing... not a lot... but the general ideas seem to be the same. You have to know what you are talking about... then you talk about it... then you proof it... and you repeat until you either get perfection or run out of time.
I've said the same thing... but not as an opener. I usually say something like "I invent new computer programs"... this usually communicates the right information and also keeps me from getting asked to fix the printer.
"I knew someone who was working for a big company doing some coding."
"Management at the company was so out of touch (had no clue what folks did in IT at all) that this was possible and this person was NEVER missed while not at work."
If the person was a software engineer, or even a coder, he isn't in "IT". There is a reason why companies have an IT department, and then a completely seperate department called software engineeing. An IT guy needs to be in the building to help employees, repair and replace bad hardware, and do general system maintanence, etc. A software engineer , on the other hand, may well be working on the drive, and while actually hang gliding. This used to piss me off when I worked at a company where the management didn't get this: Just because I'm outside drinking a coffe and smoking a cigarette doesn't mean I'm not working! In fact, just because I'm sleeping, that doesn't mean I'm not working. I have woken many times with the solution to a problem I had been trying to solve for days clear in my mind, that bubbled up from my subconscious while in delta (dream state.)
If you think a true software developer should spend most of his time in front of a computer writing code, then it is you who has no idea what is involved in developing great software.
This is honestly why I think being a Software Engineer is more like being a writer than it is anything else. No, being a Software Engineer is NOT being a writer... just they are the most similar in working styles. The writer (as a reporter, researcher, journalist, or just fiction writer) runs off to research things and does stuff that looks a lot like goofing off for weeks at a time to sit down one day an in a flurry produce something the company then takes and sells for millions. Truly new and innovative software requires lots and lots of field work. If that SE was writing software about flying then hang-gliding might be very important research.
Oh good, I thought the sun was burning out. If the days get longer I'm going to have a big party. I may have to set up some stones in the field out back to keep track of this...
We could probably get these items built much more inexpensively in China. In fact we should probably just outsource our science, engineering, and manufacturing of space exploration to China. We might use our own people for Astronauts though. It's all about making sure we're focused on the "true value add" that we have for Space Exploration as a marketplace. We can leverage the synergies of other nations to help us keep our energies focused on our "Core Business Objectives." Our core business in exploring space should be the exploring part. The whole "science" and "engineering" and all that useless "knowledge" stuff is best done by the people who are deeply specialized in those things... and they ain't us./suit-speak
“The decision is not going to make anyone gasp,” said one source in the White House, which hopes to ease congressional concerns about the impact of the new plan on existing aerospace jobs.
This is about jobs; not science. Which means, science will take a back seat - shit will be built for the sake of creating the most jobs regardless of the scientific merits and it means that if a scientifically justified project creates less jobs or no jobs, it will be placed behind a project that creates more jobs.
As long as this involves building a moonbase and getting some sharks with friggin' lasers on their friggin' heads... you won't hear me complain.
We are unable to transmit through conscious neural interference. You are receiving this broadcast as a dream. We are transmitting from the year two zero one seven.
Hey! You've had that dream too? I thought I was the only one.
Just because you are perfectly right ... doesn't mean you aren't a complete and total asshole.
As a reformed asshole myself I can tell you that condescendingly pointing out the failures of your colleagues will not get you what you want. Specifically (and I'm assuming here that your goal is the same as mine) getting your colleagues to stop acting like self-righteous fucktards. Most programmers are convinced they are geniuses. This is crucial to understand if you wish to work with them and wish to get them to do anything at all.
I am ostensibly in a senior role in my day job and I do find many things these other programmers do ... well ... fucktarded. That is they are beyond retarded since a retard would know they are a retard or at least not entertain the delusion of superiority that a fucktard does. No my friends we need to call them fucktards because they are fucking arrogant in their belief of superiority. So I can't tell these geniuses to do anything. Nope. Not at all.
You need to use psychology on these fucktards. What you need to do is something Socrates used to do with his little fucktards that he taught. Ask questions. Since the genius/fucktard seems to know so much start by asking leading questions that will do one of two things... it will lead the fucktard down a road that will show you both how stupid he is (and you can pretend they figured it out themselves they love to take credit). Or it will show you where you were wrong... and that you were the fucktard.
Remember we are after end results. So we put aside lesser things (like pride) in the search for a greater goal which should be better software and the ability to make more of it. If you can psychologically manipulate an army of fucktards you will become fucking powerful. Much more fucking powerful than you fucking are on your fucking own. I wish you good fucking luck as I can tell by the response to your post that you are a fucking powerful personality and will definitely lead your own army of fucktards one day.
Hopefully when we meet on the field we can be allies and not enemies.
Well, the Hang-Glider guy was working in a romanticized way too if he wasn't slacking off completely.
I've done a little professional writing ... not a lot ... but the general ideas seem to be the same. You have to know what you are talking about ... then you talk about it ... then you proof it ... and you repeat until you either get perfection or run out of time.
I've said the same thing... but not as an opener. I usually say something like "I invent new computer programs" ... this usually communicates the right information and also keeps me from getting asked to fix the printer.
*lol*
There are *bad* writers and there are *bad* coders dude. There are crappy chefs and there are good chefs.
And there are good Trolls and bad Trolls.
If the person was a software engineer, or even a coder, he isn't in "IT". There is a reason why companies have an IT department, and then a completely seperate department called software engineeing. An IT guy needs to be in the building to help employees, repair and replace bad hardware, and do general system maintanence, etc. A software engineer , on the other hand, may well be working on the drive, and while actually hang gliding. This used to piss me off when I worked at a company where the management didn't get this: Just because I'm outside drinking a coffe and smoking a cigarette doesn't mean I'm not working! In fact, just because I'm sleeping, that doesn't mean I'm not working. I have woken many times with the solution to a problem I had been trying to solve for days clear in my mind, that bubbled up from my subconscious while in delta (dream state.)
If you think a true software developer should spend most of his time in front of a computer writing code, then it is you who has no idea what is involved in developing great software.
This is honestly why I think being a Software Engineer is more like being a writer than it is anything else. No, being a Software Engineer is NOT being a writer... just they are the most similar in working styles. The writer (as a reporter, researcher, journalist, or just fiction writer) runs off to research things and does stuff that looks a lot like goofing off for weeks at a time to sit down one day an in a flurry produce something the company then takes and sells for millions. Truly new and innovative software requires lots and lots of field work. If that SE was writing software about flying then hang-gliding might be very important research.
Desktop and mobile devices with larger screens, 17" on up for mobile,
and 20 on up for desktops.
TVs
Some people collapse the 2nd and 3d categories into one and talk about
"Three screens"
I collapse Desktop and TV into the same thing... at least that's how things work at my house.
No, XML stands for "Brainnnnssss. Must eat brainnnnns...."
You sound like our lead "Architect" ... except he says: "SOA! SOA! Brrawk! SOA!" then starts asking for crackers.
XML stands for Xtremely Massively L-awesome!
I think they're Hungry for freedom.
I can see it now:
"Oh, no officer I wasn't talking on my cell phone while driving. This? Oh. This is a Ham radio."
Your Avatar's hobbies include playing this game... as you.
Sorry to rain on your parade, but 1 billion isn't going to give you sharks. It's not going to give you mutant sea bass.
I'd be pleasantly surprised if you get a goldfish with a laser pointer duct taped to it's head.
You have no idea how low my expectations are right now... I'm totally on board with the gold-fish laser pointer. This will rock so hard!
Oh good, I thought the sun was burning out. If the days get longer I'm going to have a big party. I may have to set up some stones in the field out back to keep track of this...
We could probably get these items built much more inexpensively in China. In fact we should probably just outsource our science, engineering, and manufacturing of space exploration to China. We might use our own people for Astronauts though. It's all about making sure we're focused on the "true value add" that we have for Space Exploration as a marketplace. We can leverage the synergies of other nations to help us keep our energies focused on our "Core Business Objectives." Our core business in exploring space should be the exploring part. The whole "science" and "engineering" and all that useless "knowledge" stuff is best done by the people who are deeply specialized in those things... and they ain't us. /suit-speak
“The decision is not going to make anyone gasp,” said one source in the White House, which hopes to ease congressional concerns about the impact of the new plan on existing aerospace jobs.
This is about jobs; not science. Which means, science will take a back seat - shit will be built for the sake of creating the most jobs regardless of the scientific merits and it means that if a scientifically justified project creates less jobs or no jobs, it will be placed behind a project that creates more jobs.
As long as this involves building a moonbase and getting some sharks with friggin' lasers on their friggin' heads... you won't hear me complain.
... by all the wanna be SciFi film makers uploading their budget clips to YouTube trying to get a movie deal now. Thanks a lot buddy.
This seemed utterly rubbish to me until I put on my Google Goggles. Now everything looks awesome.
No, really guys... mod me down... I'm totally karma-whoring. (and I don't need more karma)
... I mean, just look at these comments! Genius! Many of them (like this one) are far too brilliant to be sullied with naughty karma points!
Too right. How could you possibly answer that the documentation was good enough for *anything* all products are perpetually poorly documented.
You and me both. I have an idea for a book called: "Buzzword Buzzword Buzzword for more Buzzword" want to collaborate?
No, that one's just you.
Oh, everyone has those dreams.
We are unable to transmit through conscious neural interference. You are receiving this broadcast as a dream. We are transmitting from the year two zero one seven.
Hey! You've had that dream too? I thought I was the only one.
Darn time-travelers always screwing up my plans for world domination!