Ad Exec: Learn To Code Or You're Dead To Me
theodp writes "In a widely-read WSJ Op-Ed, English major Kirk McDonald, president of online ad optimization service PubMatic, informed college grads that he considers them unemployable unless they can claim familiarity with at least two programming languages. 'Teach yourself just enough of the grammar and the logic of computer languages to be able to see the big picture,' McDonald advises. 'Get acquainted with APIs. Dabble in a bit of Python. For most employers, that would be more than enough.' Over at Typical Programmer, Greg Jorgensen is not impressed. 'I have some complaints about this "everyone must code" movement,' Jorgensen writes, 'and Mr. McDonald's article gives me a starting point because he touched on so many of them.'"
Consider yourself obsolete, Kirk McDonald.
Guy who owns a technical company tells people they're no good to him if they can't be technical.
News at 11.
Get free satoshi (Bitcoin) and Dogecoins
These are more fundamental
Didn't this PR stunt get posted a couple of months ago?
There are thousands of occupations with no need for programming skills. Ah, how about nursing, for instance. This is just an ad salesman trying to give off the impression of being relevant in this day and age. He's an ad salesman. An idiot.
I've been a programmer for 15 years now, and the absolute worst people to work with are the ones who know just enough about programming that they vastly overestimate their knowledge. I don't want to work with a bunch of people who are on top of Mt. Stupid, least of all some exec who thinks a tiny bit of coding knowledge will help you make estimates about how long a bit project will take.
Let programmers program. Be serious about it, or don't do it.
That is all, and I say that as someone who knows more than one programming language.
And THE MAN, wearing boots, is always looking to step on your neck. These new ubermensch rule the roost from shiny new San Francisco offices with their free lunches, aeron chairs and mandatory copies of Atlas Shrugged standing proudly on their otherwise empty bookshelves.
You, not working for Apple or Google, simply don't matter. Get used to it.
And that's all there is to say about that.
Well, duh. Which of us can't think of an English major we'd like to fuck? But that's not what we're discussing...
The idea that programming is something anyone can learn if they just sit down with a book and type examples is not just offensive to programmers—it’s a dangerously misleading idea
That's funny. Most of the best programmers I know learned (at first) exactly that way.
My first experience with programming was reading a book on BASIC. This was before the widespread availability of personal computers like the Apple II or TRS-80, so I had to work out all the exercises with pencil and paper. This led to a successful career as a programmer, despite the fact that I think I only took one programming course ever (Fortran in college).
I have a friend (still working as a professional software engineer) who first learned by reading a used book on PDP-11 assembly language.
Maybe everybody doesn't need to know how to program. But even if that is true, Jorgenson is still an asshole.
The feeling is mutual (whether he's able to code or not)...
Everyone should know at least the basics of what is part of our daily lives.
Everyone should know how to read and write, even if they're not professional authors (and, like me, are pretty bad at it in general)
Everyone should know basic math, even if they never use it, at least to be able to calculate tip at the restaurant and be able to read their tax report.
Everyone should know enough biology to be able to make a basic informed decision when discussing a problem with their doctor or dentist.
Everyone should know at least basic economics and finance, so that they can at least understand the graphs on their 401k.
And.....everyone should know at least the very very very elementary basics of programming, as it is now part of our everyday lives. No need to know python and APIs or how to compile a linux kernel. Know just enough to understand what a conditional and a loop statement is, why software can crash, and why a single programmer cannot write an entire ERP suite in 2 weeks by themselves.
What an arrogant ass. "I run a cool company...", yeah, I have heard that before, from a ball-busting micro-manager who worked people into the ground, and could never bring himself to use the phrase, "good job". He had taken a couple of classes at a community college on programming, and thought he was an expert. Disaster. No time allotted to plan projects, no time allotted to test, but we were a cool company. Incompetent, but cool. I bet he still wonders why the turnover rate is so high.
This guy is head of PubMatic, which is one of those companies on the fringes of on-line advertising. Here are their job listings. The programming jobs are in Puma, India. The US jobs are for things like "Mobile Account Executive" (i.e. ad sales rep.) Requires "proven track record of meeting or exceeding sales targets." No mention of any tech skills.
The PubMatic site is so full of business buzzwords that it's difficult to tell what they actually do. "From brand awareness initiatives looking to reach broad demographic segments through to lower funnel campaigns focused on reaching those expressing purchase intent, PubMatic has a targeting solution to fit advertisers' needs." What they seem to do is match up low-end advertisers with unsold ad space on web sites.
If this company dropped off the face of the earth (or AdBlock became popular enough to delete all their ads) nothing of value would be lost.
I'd consider myself an experienced web developer (PHP, CSS, HTML. JS, DOM API). I wanted to learn more languages, but I found it very inaccessible to learn different "languages" since it seems these are merged nowadays in frameworks with deep learning curves. It tried Visual studio 2010, Titanium frameworks and some others. Either giving me dependencies-error during installation or a complexity level that feels disastrous to cope with as a newbie.
I just feel that it seems most programmers/developers and their tools want to protect their creed of "language" with a steep learning curve to protect their profession & expertise, and make it as inaccessible for newbies as possible. VB6 compared to the latter Visual VB is an example of simplicity morphed into "enterprise level" development.
Why don't people start to differentiate in the actual "language" and the bloated "framework".
the absolute worst people to work with are the ones who know just enough about programming that they vastly overestimate their knowledge.
That's very true, but the BEST non-coding co-workers are those with similar levels of knowledge who then have a better understanding of what is possible, why some things may be hard and a tolerance for mysterious delay.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Yeah, it's almost as though they make up for unemployability with sheer hotness. First girlfriend in college. English major. Hot. Liked to bang like no one's business. No idea what she planned to do with English. Unlikely to matter given that she could just pick some man take care of her.
Probably a rich housewife/socialite now.
THIS is the reason to block all ads from the internet.
The worst programmers in the world work for ad networks writing crap javascript code to run inside every computer browser in the world. Nothing could go wrong with that, right?
He's probably the type that thinks for example that for example C# is totally different than any other object oriented language. Most likely he would be honestly surprised to find out somebody that understood general OO concepts and was in an expert in another one like C++ could pick up a second OO in a matter of days or less. (Sorry, I get that a lot. I think it took me 1-2 days to get up to speed from C# from C++. Not sure how long it'd take me to pick up java but I'd expect a week at most.)
Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
so why would I need to know how to drive?j
The guy's examples don't make sense, but his premise is sound.
It's a big world, and he doesn't define success OR
failure.
Each garbage collector need not write a separate program. An employee of the company employing dozens of garbage collectors can write the program, and the team for each truck can load a map into that program.
The situation: You've got a thousand applicants. You've got one or two job openings.
If you don't have the slightest idea what makes the internet and the information age run, you probably don't deserve the job. But the converse is also true: programmers should learn something of art, literature, and history. Too many software people don't even know anything about science. A person that can't think broadly in a well-rounded way is useless.
I think that everyone should learn to code. Not because it will make them a programmer. Not because it will enable them to estimate how long something will take, not least because experienced programmers are legendarily bad at doing that anyway. Everyone should learn to program because programming makes the modern world go round, and it's good for everyone to have at least an inkling of what that involves.
We teach a lot of kids chemistry, without any expectation that they will invent a new compound that will change the world. We teach a lot of kids physics, without any expectation that they'll make a significant contribution to subatomic particle research. We teach most kids to do creative writing and poetry, without expecting the vast majority of them to produce fiction or poetry of publishable quality. I don't see why we wouldn't teach programming alongside all those other topics that most students never master and never "need".
One argument for teaching a lot of academic subjects widely is that the skills you learn along the way have wider application than the topic itself. And it seems to me that this argument holds at least as well for programming as for, say, pure math. As programmers keep saying, programming is about analysis, structure, models... is there really no application whatsoever for those skills outside of hardcore programming? Does no-one ever wish that their managers had a better grasp of "system"? Yes, of course, you can acquire these skills in other places. But the thing about programming, pretty much from the outset, is that your pious beliefs about system will stop your code from performing correctly unless those beliefs are reasonably accurate. I sometimes tell people that I do executable philisophy - it's all about logic, but, unlike the philosopher, my logic has to work.
No, a bit of Python won't enable people to produce estimates for projects. But it may enable managers to understand why writing code once to do something that needs doing often is often a good plan (and, also, why it sometimes isn't). It may enable managers to understand why "Can we just change this one assumption" at the end of a project may involve restarting the entire project.
Yes, a little knowledge is a dangerous thing. But the little knowledge is out there already on the TV station of your choice. I don't even like Python that much, but I'd still much rather deal with erroneous assumptions based on a bit of Python experience than deal with erroneous assumptions based on watching Mission Impossible and NCIS.
Virtually serving coffee
With everything ever written both protected by copyright and patents, what is this guy proposing? I think it's clear that only companies with big legal budgets can be allowed to have coders on staff. Everyone else is a risk.
Ad Exec: Learn to code or you're dead to me
It might be worth it to forget what languages I know, if it meant the online ad companies would start considering me to be dead.
#DeleteChrome
If you've ever worked in IT, you know that the clueless secretary isn't your worst enemy. At least she knows the knows nothing.
Your worst enemy is the "power-user". The guy who knows just enough to fuck everything up. This is the same thing. Breeding people who know a little bit about 2 programming languages is breeding a catastrophic collection of idiots who don't know that they know nothing.
Teaching someone the basic principles of programming, that's cool. Let them know a little about how algorithms work and stuff, a little bit of basic understanding of what, exactly, programming is. But please don't teach someone a little bit about a programming language or two.
Assorted stuff I do sometimes: Lemuria.org
Indeed. One does not simply walk into a field of mones. Be careful!
Tic-Tac-Toe, Global Thermonuclear War, and relationships all have the same winning move.
Remember COBOL? Remember what it was intended for?
Those who forget history are doomed to... um... something, right?
There's no -1 for "I don't get it."
What's this guys smokin'? Crack?
Sorry charlie, if you want to work at any companies *I* ever worked for (current included), you had to have a proper technical degree. Period.
'nuff said.
Bite me.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
Non-programmers are losers. Actually non-GNU/Linux C/C++ programmers are losers.
an ill wind that blows no good
He's president of an ad optimization company. They deal in programming. Of course he thinks he needs people who understand programming. If he were selling cars he would think differently.
FTA: "This isn't because I don't have positions that need filling. On the contrary, I'm constantly searching for talented new employees, and if someone with the right skills walked into my office, he or she would likely leave it with a very compelling offer. The problem is that the right skills are very hard to find. And I'm sorry to say it, dear graduates, but you probably don't have them."
-----
The downside of having said programming skills if you could be conned into working for a total douche-nozzle like this.
Also, this dude is very high on himself and what he's doing. "Next potential dream boss"? "Cool and interesting" company with "interesting and rewarding" work? Bro, you sell internet ads. Your "interesting and rewarding" work is trying to find new and innovative ways to piss me off while I'm looking at Ebay and surifing for porn. Let's not get carried away here.
So does it count if you know brainfuck and whitespace?
The Tao of math: The numbers you can count are not the real numbers.
and java is the COBOL of the 90s that still lingers like a really rancid fart in a church long after the congregation left.
Interesting. If you want to work for the successful companies I've worked for, you need to be intelligent.
People with non-technical degrees still qualify. I can teach someone intelligent to program a hell of a lot more easily than I can teach some muppet with a technical degree.
A well educated person should know a little about a lot of things (economics, business, writing, math, science, physics, etc...) but this moron say that the reason his employees should know a little programming is so that they can give estimates to clients. Moronic idiot! ^ 2
A grammar lesson for you:
https://www.youtube.com/watch?v=bzhEt1-qGhk
...I couldn't care less about anything a fucking ad exec says.
There is a war going on for your mind.
C'mon, that's unfair. COBOL was in all seriousness meant to let "Managers do Programming", and so it had syntax like "ADD 1 TO X".
Java really was like an easy C/C++. The the object system wasn't bolted on like with C++ and memory management was GC done for free. I program in C for a living but I don't see the hate for Java. It seems like some trendy bullshit to me.
j2ee on the other hand, holy crap what a stinking turd..
Exactly. It even has the same wordiness, the laborious attention to meticulous mind-numbing detail.Substitute jar files for copy libs and you even have the same nightmare descent into spaghetti which masquerades as coding structure. Java has replaced COBOL as the language du jour of the current generation of software engineers. What is wrong with this picture? Why are we still doing this and when are we going to stop? Computer coding is a mindless task which should be relegated to the machines which consume it.
This is pretty funny. An advertising executive telling college students what they have to know to not be "dead to him".
A guy who makes his living by getting people to buy stuff.
He doesn't realize how little it takes to make his entire existence meaningless. Plus, don't you hate guys who go speak to college students and tries to do this kind of tough talk? Too many people got boners when they saw Gordon Gecko give his speech in Wall Street. They thought, "I wanna be that guy who makes young people quake in their boots". I bet his family hates him.
You are welcome on my lawn.
I have no problem with him requiring his sales people to know how to program.
But when you come by looking to sell ads for our hospital, you need to demonstrate knowledge of least a couple of basic surgical procedures. Someone who doesn't understand surgery shouldn't be making ads for us. You don't need to be able to fix an aortic dissection on your own, but you should at least know what instruments to use, and the overall procedure.
Support microSD: in a post 9/11 world, it is unwise to carry your data on media that you cannot comfortably swallow.
You make lists in english and execute the instructins youself, or give them to another.
The government is stuck in an endless loop as well ;)
I'd say meh anyways.
My major is graphic arts. In terms of programming, I know enough about coding to make an old-school "punch the monkey" interactive ad that sort of works. (Made at least one "fun" game with limited reference, and scratched the surface of a few ECMAscript style languages at times.) I also suspect that I'd know enough such that you still wouldn't want me to touch anything involving much on the backend of anything interactive or around fidgety database stuff. All to easy to break dependencies if you try tweaking stuff while not sure how it ties together. I know my limitations, and when it comes to programming my vocabulary and fluency is limited. However my code although not great is probably good enough for a competent programmer to figure out what I'm trying to do in a half-assed manner and go about fixing it in under half the time I took to write it in the first place.
Despite having some skill and crossover knowledge, I'm still fairly unemployable in the job market which relates to my field of study. Primarily because there's no magic way to get five years experience in the relevant field after graduating from college. That's the big thing few are able to get that every hiring employer out there is looking for. Sure some would say to do pro-bono work, but my time is still worth more than that. (And still true even when considering the amount of recognition one gets for those kind of jobs. Which often isn't much, as most outfits are happy with boilerplate CMS templates that any fool can copypaste into. And trust me, lots of websites out there half assed with unused lorem ipsum pages and other hints that makes it all too obvious about how much they care.)
They are always the one's doing the minors in High School.
"Teach yourself just enough of the grammar and the logic of computer languages..."
I'd be happy if they knew grammar and logic, period. Screw computer languages.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
Imagine the glowing reviews she gives a gross nerd, who still talks like a 16 year old boy.
While going to school for technical knowledge I spent many years learning biology and English appreciation, If I needed to be able to debate the meaning of Shakespeare for a CS degree, then why cant some waste of time English major at least write "hello world" in a loop?
Reading these kinds of stories always puts the fear of God in me that I may suddenly find myself "job free", and scrambling to find work. It reminds me to keep working on my off grid cabin where I can ride out such turmoil.
People that intentionally seek useless degrees are naturally satisfaction seeking and ignore risks. I.e. people with crap degrees will be more likely to bone people in general and therefore it is much easier to land a desirable mate from that category.
Yeah, back in the day, I used to kick ass in monesweeper. I would get high score and everything!
"Good, Fast, Cheap: Pick any two" -- RFC 1925
Yeah, I've worked with a number of programmers at ad agencies who would tell me straight to my face, "I don't need to know math in order to write code!." Come to think of it, there might be something to Kirk McDonald's statement: PubMatic only wants "muppet(s) with a technical degree," and not someone capable of logical and analytical thought. If your employees can't think for themselves, they certainly aren't gonna question the horrible way you manage your company.
"Good, Fast, Cheap: Pick any two" -- RFC 1925
You want a job whereas you need to work in the first place.
Where were you during your 5 years master? No experience gained?
Thats it. The all for the diploma approach.
I failed my masters, since I worked. I have experience, you have a degree. I get your much wanted job.
How many people here took physics?
The US produces approximately 7000 professional physicists a year, yet almost every student in the country takes physics classes.
These "everyone" physics classes are insufficient training to do any sort professional physics. What they do accomplish is help expose people to physics so that 1) they can see that physicists think a bit differently and 2) they can think about physics as a career. The classes are designed to do this instead of actually teaching useful modern physics (this is why you're repeating 400 year old experiments in a college class).
So yeah, physicists have to deal with crackpots and managers who haven't actually learned any physics from the last 150 years, but in the end, it's a net positive experience for all of us. Doing the same thing with programming would be a good idea.
because you have to have the right mindset ... being able to write valid programs in any language doesnt help you if you cannot structure and break down your problem into meaningful blocks (be it classes, functions, ...).
So people who know "how to code" are essentially the worst because they think because they know the language syntax (and often even that only barely) they know everything there is to know about "programming" (as in: from problem to elegant solution).
"English major Kirk McDonald, president of online ad optimization service PubMatic, informed college grads that he considers them unemployable unless they can claim familiarity with at least two programming languages"
We're talking about the *advertising* industry, right?
In that case I can claim familiarity with two programming languages, no problem. I also claim familiarity with advanced astrophysics, quantum mechanics, and Elvis Presley, who I met in his vacation home on the Moon.
Visual Basic and Perl? What could possibly go wrong? No, hold that. What could possibly go right?
I don't have to - stuff like ImageMagik or bits of gimp (both cross platform) already do all those things so it's just a matter of writing a shell script (ImageMagik) or python script (gimp) to call them in the order desired. Or if it's vector graphics I could use any version of AutoCAD from about 1988 on and do it in lisp.
McDonald's tells grads that cannot code to go flip burgers.
News at 11.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
Computers are tools. What makes them useful is the things we tell them to do. We tell them to do things through code. Therefore, to properly use a computer, you should know a little bit about how to code, and a bit about how the thing works, shouldn't you? I'm talking about general-use computing here, not things you would do with a kiosk or point of sale system.
If a big part of your job is to use a computer, to analyze and share data, then yes, you should know how to code. I certainly expect people who work on my house, my car, etc, to know how to use their tools.
If you create content or processes on computers, you should know how to properly tell them how to do things. Not knowing this leads to spreadsheet 'databases', single images in powerpoint (or powerpoint at all), word attachments in email that state what could have just been written in the email itself, and all of the other associated idiocy that I'm sure you all deal with every day. I don't expect my mechanics to know these things. In this analogy, they are the computer drivers, not the ones building and fixing the car.
Remember, SQL was originally written to make querying and correlating data easy for managers and NON-PROGRAMMERS. That's why it is so english-y. Now, it is considered 'programming' to understand how to create a SQL query, and management has to rely on other people to use the tool for them so they can have a non-flexible set of buttons they can push rather than just tell the system what they need at any given point themselves. Let that sink in.
If McDonald is insisting on some familiarity with coding in order to maybe weed out a particular kind of applicant, then I can kind of understand where he's coming from. And by the way, a person can manage to have some familarity with coding and APIs by using CodeCademy (which is free. If just takes some time and effort). But if he believes that the individual should be able to contribute coding based on just this, yeah it's not really going to work I think.
I think what he's asking for isn't that unreasonable. Everyone should have some exposure to coding, even if it's not for them.
And drop the Bo Burnham glasses. Then jump off the roof.
But the objects are bolted on in Java, it is a procedural partially 00 language.
As for your "Add 1 to X", I'd retort myCamelCaseMethodSoTypicalOfAJavaDweeb()
I'm a programmer, and there's little worse than having someone in Marketing or Sales come to me to ask for a specific task to be done in a specific way, because half way through the project I'll generally figure out what it was they were trying to accomplish and have to start from scratch to deliver a product that actually meets their needs. Because they know some of how things work on the back end, they try to solve a problem themselves and then send it to IT for implementation. What I prefer is that they present us with their problem or need and we can go over, with them, several possible deliverable solutions and their relative merits, time to deliver, and cost to deliver. Reading this, I can now see that it could actually be worse. They could be versed in programming languages we don't use and come to us with solutions that use their own personal hammer, not the full tool set we possess.
wageSLAVERY
I am a DBA. Managers who dabble in technical skills get in the way. They know just enough to know some of the buzzwords, but generally think they know more than they do. They tend to get in the way of people who really know what they are doing. You try to explain stuff and it is in one ear and out the other because they don't know which keywords are important. They don't know enough to know what they missed. Then either blow it off because they don't get it, or put their interpretation on it and get it completely wrong.
This is doubly frustration to a DBA because our operational responsibilities require us to carry pagers. We get paged overnight and the manager is sleeping. Something was 'fast' in development and there 'just is' level of knowledge can't grasp that something is then 'slow' in prod. You get these 'just is' responses back. However, I am the one carrying the pager and gets woken up at 3 AM on a saturday because a job they wrote is 'slow' since they didn't do what I told them to. I am supposed to 'monitor' this, then send email updates (managers don't like being woken up). Monitoring amounts to losing sleep staring at a screen.
This happens to the developers too when they deal with 'pseudo-technical' managers who act like know it alls.
I worked with a statistician once and I had to create tables and manipulate data in a way that his SAS tool could handle it. I didn't understand what the hell he was doing with his stats models. They looked like greek to me. I had a couple of statistics classes in school, but I was smart enough to realize that this guy is an expert. He has a degree in stats and its what he does all day for years. I didn't go 'dude, there is this feature in SAS use this to get a cool picture on the screen'. I got out of his way.
That's what my old boss said!
I'll never take a programming job again...
When my previous employer (a Fortune 20 company at the time) analyzed our marketing, sales and support processes (I was on the team), we found that 80%-90% of even these "lib arts" types of job activities were "information or information processing". Whether that means you need to be a programmer to "do sales" is debatable (in some case our sales people *did* need to have programming knowledge just to know how to sell the product). But certainly you needed a higher level of "information processing" tool, skill and abstraction knowledge than merely learning Excel.
The situation: You've got a thousand applicants. You've got one or two job openings.
There's your first problem -- you don't know how to specify the job you are hiring for.
If you don't have the slightest idea what makes the internet and the information age run, you probably don't deserve the job.
There's your second problem -- your operation is not organized enough to take advantage of highly skilled specialist.
Sure, everyone should have some broad knowledge of many fields. However, can you imagine demanding that all programmers understand how to write marketing copy, or sell ads over the phone?
'Big picture' is the insight that one may gain over years. To some, it never comes.
One of the worst parts of my job was interfacing with a system written by an MBA who "knew how to Code". He knew nothing of structured programming, or flow charts or no concept of unique records, or the normal forms in database construction. So when he cane across some tests that could have Y/N, Pass/Fail, and numeric values with different ranges he solved the problem by combining the test id and the product id. Sounds simple enough until you have to interface a system that expects unique tests like maybe SAP, or a lab information management system. Of course there were thousands of these tests. Thanks, but after many hundreds of hours of seeing (and fixing) the results of that approach, lets keep coding to people who understand structured programming at least. Although they are unlikely to write a compiler, current state and next state arrays can be handy too.