And I've been digital since then.
277 karma · joined August 17, 2011
And I've been digital since then.
Apple's not out to get you. In fact, I'm glad they did this. That iHasApp looks creepy as hell, and it pisses me off that other devs were using it to basically spy on me. It reduces my trust in all apps.
SV has more opportunities for engineers/entrepreneurs, but then you're up against people who have done a lot more of that, plus the outrageous housing costs in the area. Oh, and the crazy traffic.
I was living in a 'burb and moved back to the city for quality of life. Being able to walk to things (grocery store, restaurants, bars) was more important to me than having a bunch of land. Also, my commute is now 5-10 minutes instead of 30-90. The cost of it was a smaller house on a much smaller plot of land, but we decided that's a sacrifice we're willing to make.
The only thing to look for in a company, in my eyes, is how well they pay their employees. They can glad-hand all they want about open workspaces and ping-pong tables and catered lunches, but none of that matters. Show us the money.
Our industry is seen by outsiders as an old-boys club full of young boys who viciously hate and destroy any attempt at diversifying. Unfortunately, when these sjw types score a small victory, they see it as a big victory. The rest of us see it like a quota system -- we're forced to deal with less talented people just so somebody doesn't get butthurt that there's not enough females or black people or whatever.
My first job was writing code for a company that took advantage of poor and desperate people. I didn't see that for a few years. But, it was a good veneer -- help people who wanted to go to school to improve their lot in life. I genuinely thought I was doing something good.
But these for-profit schools ended up abusing government regulations and guarantees around student loans, which has largely led to the student loan crisis. However, I thought that I was buying stuff in my community, it bought my family a house and a reliable car, and we were paying a lot of taxes.
Every company has some variation on this. Starbucks has been great for coffee growers around the world and has exposed many people to boutique/single-origin coffee, but like you said, it's built on addiction. But any restaurant is doing the same -- they're doing whatever they can to bring you in and have you pay money for food. I mean, you have to eat, right? And restaurants are all about flavor and presentation and unique ingredients -- they're triggering your dopamine, which they hope will entice the diner to spend more money. Car salesmen are the same way -- everybody kinda needs a car, but they try to take advantage of our lack of information, and try to cover it with dopamine-based ideas: smooth leather, new car smell, perfect paintjob, fast car, get a bunch of chicks, people will really know you've done well in life, etc.
Everything in live is built on dopamine though -- it's why we do anything. To reduce it to dopamine trigger = bad for humanity is not fair.
It's the same argument when it comes to legalizing cannabis -- people are just going to smoke it, no matter your personal opinion on whether or not it's a good idea. The state is better off regulating for safety, legitimizing the business, and collecting taxes to offset the perceived social harm.
Of course, if you assume even half of those people are lying, that's where the addiction is. You'll tell yourself stories and tell others stories, so they don't see you as a weak person.
They'll all give you a form letter "come in and talk with us" message. Apparently cost-plus isn't that appealing to them, and they'd rather lose the sale and wait for a higher-margin purchaser.
1. Anything related to trees 2. Big-O trivia and errata 3. Reinventing the wheel 4. Bit-twiddling operations
Seriously. If I go into your interview and you ask me to reverse a string, and it's not <string>.reverse(), I'm not taking your stupid job. I don't care if you want me to know the tricks for an in-place string reverse with no temporary variables, that just shows that you don't have a clue how to interview.
Good interviewers? The best I've found so far:
1. Ask people to do real-life problems 2. No "gotcha" questions 3. Let people use the environment they'll be using for the job -- this means an IDE, the internet (including stack overflow), and any library they want.
What I want to see when I'm interviewing is whether or not you have the ability to solve a problem. I'm going to look at how you abstract and break down problems, how you solve them, and at what point you say, "I think this is done."
Yes, I expect good engineers to know when to use a tree or a list or set -- but if you're explicitly quizzing for that, you're probably filtering in more terrible developers than you're filtering out.
I'm so sick of everybody trying to cater to these crybabies. They can go work for the government or something.