452 karma · joined December 2, 2011
Why are business SO reluctant for a standards "pay for what you get" business model?
I really just care about how well they problem solve, not problem solve in a fox-hole with bullets flying over their head.
I also hate the actual interview itself. So little time to try and learn something that for the most part cannot be learned in a high pressure, nervous, anxiety ridden situation (I realize I am also being interviewed, assessed, and reviewed). However, this is a different point altogether from what the author is discussing.
I do think it's great to try and understand how someone
1 - Problem solves 2 - Approaches asking questions, interacting with other people, etc
And quizes can sometimes be a way to figure that out.
I've just found that when using quizzes it's better to openly communicate with the person what you, the interviewer, are trying to better understand. I always pre-amble a quiz (if and when I do use one)
"hey, I'm going to ask you a question/quiz/riddle. It's important to note I could CARE LESS about the answer. I'm really looking to better understand how you would go about solving this. So please, make sure to walk me through your thought process and don't hesitate to ask me any questions along the way".
I also like to make it clear how it ties into what the person will be working on. For example
"the reason I ask, is one of the first projects you will be working on is ___________, so knowing how you approach nebulous problems will be important"
The best response I had to this is
Well, I might do X,Y,and Z, but to your real question, I have a great example, mind if I share that?
Also, this is just a data point. Going back to my second paragraph, I've never once "not hired" someone based on how well they think on their feet in an anxiety ridden, pressure filed, hour of their life in a room with total strangers.
BE WARNED!!!
Totally kidding, I think.
SUPER IMPORTANT!
All their amazing R&D didn't make W8, their phones, or their tablets any more enjoyable or purchasable.
In fact, the longer in the field the the more dated the education becomes. Our field is changing and knowledge is turning over so fast that a ten year old degree is borderline irrelevant vs someone who has experience in "today's technologies, methodologies, etc".
There are fundamentals which hold true from college, but a large majority of the technologies, techniques, etc are no longer relevant.
I used the word Jihad as it best reflects how personal it becomes to some people. It's not a matter of taste, but a matter of "being".
My main point, which clearly wasn't well articulated, was STEP YELLING AT ME. I can't change it. Nor do I care.
Yell at Apple, or Google, or whoever can act on it. Boycott them all you want. Just don't vilify me simply because I happen to like the platform you happen to hate.
You do that, and I promise to not yell at you for the platform you like that I happen to hate (as an example, I honestly could give two shits about Apple or Android .... it's a god damn phone).
If more people just bought what they liked, shut the hell about it, and didn't rage jihad against the opposite platform, the internet would be WAY better.
My general reaction to Craftsmanship is they pull toward an equally unhealthy end of the spectrum. Only focusing on quality is equally as bad as never focusing on quality.
Software Craftsman, on average, trend towards the code is the ultimate goal and/or product. The job WILL NOT get done if they don't like how the code will be written. They've swung the pendulum too far in the opposite direction.
Ultimately, its a give and take between the business and software. In fact, this holds true FOR ANY DEPARTMENT in a business. Marketing I'm sure feels some of the same feelings development do, as does UX, as does finance, as does sales, etc.
I am truly disgusted by the "on average" behavior and attitude that accompanies most "software craftsman".
Per your point of disagreement, and depending entirely on the type of app, I stand by my point. You're anchoring the disagreement "quality". A down and dirty "test the waters" app is a lot less expensive than a "quality" app (ignoring apps that can't really have a down and dirty, like complex video games or something).
I would agree, that on average, a "quality" app would take longer then a down and dirty "test the water" app. However, so long as you can get a down and dirty out the door so easily, we will see crap in the app stores.
Nothing will stop this from happening ... especially when the cost of build/deploy <= cost of comprehensive research
In regards to the site ...
Asking someone "yeah, I'd use that", vs getting them to download and use (ignoring pay, but that's also key :)) is totally different
I think a lot of early stage startups are staffing less graphic art/design via their dependence on Bootstrap.
All in all, it is a sweet front end visual framework!
I've also viewed "mobile first" as thought/design methodology that doesn't mandate you must then "build" mobile first.
What's the end goal? I find it incredibly more insulting, demeaning, and counter productive to include someone JUST because they are white, black, female, asian, etc. It's just as discriminatory as excluding them.
In fact, in my opinion, it's far worse. It's discrimination masquerading as equality.
You want everyone treated equal? Awesome. The best speakers get in, period. You vary from that in either direction, and you are embracing inequality.