5,407 karma · joined January 14, 2010
The right current skills and the ability to learn future skills aren't incompatible. After all, how do you think those people got those current skills? I don't have to choose one or the other and I've rarely met anyone in IT who isn't willing to learn new skills.
Generally I have two or three core skills I'm looking for for a role for and the rest are nice to have. To me it's a given you'll basically be smart and that you'll need to learn stuff but I also know from experience I can get smart people who have a core set of knowledge which will make them productive early on.
I certainly have no interest in someone who can copy and paste keywords and if that's all you'd done you won't get past first interview. All I'm asking is that you present your experience in a way which is most relevant to me to help me understand.
What I would say is that there is a difference between hobby code where you get to do what you want and code where you didn't control requirements and had to deliver to unreasonable people in unreasonable timeframes (aka commercial software development). Obviously it would depend on the projects but generally someone who has commercial experience would probably be viewed more favourably as it's more directly comparable to what I need you to do.
All that said, I deal in corporate style CRUD apps (there is a bit more to it that that but that's the core). That's an area where OSS - the best sort of out of work project as it's team based, real world and so on - isn't that active so it's not a consideration I have to make too often.
I accept people leave when their salary diverges more than a certain amount from the market rate but that would normally - even in a good market - take time.
Personally I wouldn't expect a major pay rise within the first 12 months of a job (if you do then you've probably not negotiated your starting salary properly). Add to that a couple of months after that to find another job and a month notice and the shortest stint relating to poor pay I'd expect is about 15 months. If you're staying 15 months or so in places which are bad payers and a few years in places which are good then your average is probably going to be 2-3 years. To me at least that's not a problematic amount of time (particularly not if you've shown you can stick at least place for 3 years or so because that says to me you're not inherently disloyal).
So short stints don't say anything, at least not much, about money when I read a CV.
1) Hiring someone is a big deal. You want the people best placed to judge whether they're right involved.
2) You're selling the company to someone who may/will have other choices. Put the people forward who are going to do the best job of that.
Point 2 is important. I have no interest in candidates who do the whole "you'll make all the effort and bend over backwards because I'm in demand". Similarly I have no time for companies who demand days of preparation before interview as if I have no other options and they're the only game in town. In almost all cases the person isn't good enough to put up with that attitude and the company isn't the only place the person might consider working.
Jobs are a coming together of two interested parties and both sides need to show respect and be fair and reasonable. As a result if I'm recruiting then beyond a slightly tailored CV and some basic research into what we do (and maybe the technologies we use if you don't know them) I don't expect preparation. In exchange I'm going to spend time telling you about the role, the company and the project, I'm going to answer questions and I'm going to be as honest as I can be to make sure you can make a good decision.
I write a job spec which lists what we're looking for which is advertised and passed to recruiters - if you're interested in the job you've almost certainly seen that.
Assuming you do have the experience, using the spec you should be able to tweak your CV in about 5 minutes to highlight the key things we're looking for. If you do that, you've cleared this (very low) bar with a very small time investment and it's not a problem. If your CV makes it past the recruiter (or HR department or other non-technical screener) I then know that the CV I'm looking at is worth my time and the following interview is more focused as I know a bit more about what you've done where.
Yes you are having to spend time but, as I say, this should be a very short tweak to your existing CV so it doesn't feel like a big ask given that I'm going to spend longer than that reading it (and hopefully interviewing you about it).
Obviously if there is no job spec then this doesn't work so well but there's usually something, even if it's just stuff you've gleaned from the advert or conversations with the person you learned about the role from.
As an aside, please don't ever try to get round the keyword thing by listing everything you've done or used. I had a CV the other week which listed 43 skills, tools and technologies for one nine month role. From that I have no way of knowing what you used in passing and what you really know - you've provided so much information it just became noise. My rule when I'm working out what to put - if you put it on your CV you'd better feel happy answering (proper) questions about it and I don't believe that you passed that threshold with 43 things in a nine month period.
If I take you on I want some indication that you're going to stay around long enough for the investment we're going to make in you to be worthwhile. We'll normally pay a recruitment fee and then we'll pay you while you're learning about our product, our industry, our processes and the specific technologies you haven't worked with that we use, and we'll be paying our existing staff to take time out from coding to do those things. That's not inconsiderable.
Obviously your experience may render some of that irrelevant. If that's the case then if you're massively better than the other candidates I may take the risk but if you're not, then I can take you or I can take the person who is as good but will stick around longer. That's not a tough decision.
I'm not looking for gold watch territory or even an indication that you might be around for 5 years, and I'm not looking for a guarantee, but if your CV shows a pattern of you moving every 15 months I need to work out why I think I won't be your next 15 month stint and if I think I think I am whether it'll be worth my while.
Essentially it's just a more representative sample than these other horribly unrepresentative samples he's listing.
Still, personally if I had concerns about privacy and secrecy I'd be looking to limit the number of devices in my own home which had an always active microphone.
With this it's running on mains, it could upload in the middle of the night when it would probably be undetected
Plus, why do one or the other? Sure you want to get someone's phone but why not another device too?
If it's not listening how can it hear the wake word?
The flow is directories on your machine > BackBlaze.
Anything in the other direction is manual.
* I love my kids.
There really is no limit to what beautiful people in their 20s can do with this sort of product.
Cook is clearly a prime decision maker in where Apple operate but the poor situation for Chinese workers can't reasonably be laid at his door.
The wages are controlled by market forces, even if the market is being manipulated by the Chinese government.
But Cook isn't responsible for Chinese economic or fiscal policy and pulling Apple out if China would hurt the workers who may have shitty jobs but at least have jobs.
As it is Apple face higher scrutiny than most of their competitor in the same situation and as a result actually behave marginally better when it comes to worker treatment.
It's not something to be particularly proud of but the overall plight of Chinese workers, even those at Foxcon, is not a situation for which Cook can realistically be held significantly responsible or categorised as nasty (nasty being the original characterisation I was refuting).
It's the consequence of a capitalist economy which Cook may be a small part of but is neither the creator nor the controller.
But if you believe that, that's a pretty intolerant view you have there.
The question of tolerance of intolerance isn't perhaps as simple as you make out. It's been well discussed without a clear answer: http://en.wikipedia.org/wiki/Paradox_of_tolerance
Underpaid in what way? Are there many other jobs those people could be doing which pay them better? They're not paid much by US standards but the alternative is subsistence level farming. Is anyone who puts their production into China (and let's remember that's basically everyone in hardware before we single out Apple) being nasty by offering people a better income than they can get anywhere else?
It's the market rate, something incidentally most people in tech in the West are pretty happy about when it's driving massively above average salaries for programmers and the like.
In terms of overworked - Foxcon workers recently went on strike because the amount of overtime they were being offered had been reduced. If they're overworked it would be very odd behaviour to strike to demand more.
Essentially Foxcon workers get to choose between two things - a shitty life working at Foxcon and a really shitty life not working there. That's unfortunate, but it's not Tim Cook's fault, it's in part the fault of the Chinese government, in part the result of them having been dealt a shitty hand and a consequence of global capitalism which most of us are in some way complicit in.
To place this at the door of Cook is pretty naive.
Just the proportion of people who play computer games who see them in this way is shrinking rapidly.
It may not be official Google Android, but low cost generic Android tablets are massive in Asia. Most of them are low spec devices but that's all you need if all you're doing is watching movies and a bit of web surfing.
Isn't the whole point of standards to stop that sort of thing happening?
I get that you may feel that someone is just appropriating your work rather than doing their own but if your aim is to build a standard then reusing things is probably going to be part of doing that.
This is true, but the point is that this is now a very small (and very rapidly shrinking) fraction of what constitutes "computing".
Digital photography - used to involve a PC, doesn't need to now. Casual video editing (which lets remember is the vast majority of video editing) - used to involve a PC, doesn't need to now. E-mail and electronic communications - used to involve a PC, doesn't need to now. Basic productivity/note taking/sorting/keeping - used to... you get the picture.
It's not just that SmartPhones/tablets are replacing some PC tasks, it's that there is a whole new swath of users for whom what might previously have been thought of as computing has nothing to do with a PC.
Think of it in terms of shooting video. 40 years ago if you were shooting video there would be a good chance you were some sort of professional (or at the very least an enthusiastic amateur). Now, if you're shooting video, you're probably just a regular person. That doesn't mean that Smartphones have changed what professionals do or use, but it does mean that professionals are a very small fraction of the video now being shot.
The PC is the same, it's still there and still needed, it's just shrinking in terms of it's proportion of what's being done.
For kids, their default go to device isn't the PC. That's what they use when they have to do something which isn't great on a tablet.
The other interesting thing is what they think "isn't great on a tablet". Non-professional photo or video editing - if you're a 15 year old today, that's a tablet thing, not a PC thing. A lot of gaming is phone/tablet rather than a PC.
A PC looks to me to be primarily homework using something MS Office-ish.
But being nice? I see no evidence that old businesses are nice (we're just more used to their nastiness) and I certainly see no case that new, disruptive businesses are any way worse. If anything I think back to the likes of Google in the don't be evil days - young idealists who just wanted to make the world better and would work out the money side of things later.
Even if that weren't true, I still want to be optimistic about change. I accept that it's not all great, that everything comes with a cost, but if you're doing something that's so obviously potentially positive, surely something is wrong if people don't feel good about it?
> Sorry but I can't read past that.
Come on - setting up an on-line store is trivially easy - Amazon can provide services covering you for ordering, payments, fulfillment...
The discussions around the conflict have, to me at least, shown pretty clearly that book publishing as it currently is isn't a model which stands up to too much scrutiny when you look at how well it works for anyone outside it.
On the other hand I think we'd all rather it wasn't Amazon, a company who many seem to like using but don't trust much further than they can comfortably spit a dead rat, giving it a kicking. The old metaphor about frying pans and fires springs to mind.
Maybe we just live in a more cynical time but it would be nice if our disruption was something people generally felt optimistic about.
The usual logic runs - from 8am to 6pm I'm at work. From 6pm to 8.30pm I'm dad (or mum but realistically it's usually Dad). Once the kids are back in bed I get back on to e-mail, catch up with what I've missed and start planning the next day.
That's great - you've covered work and your kids/family as a whole, but where are you fitting in time just as a couple? I'm not talking about weekends away or big nights out (though those are tough enough), I'm talking about just fitting in time to talk and catch up and remember why (and indeed that) you like each other.
For me that's the toughest one. You or your other half can find time on your own - that's easy, the other one takes the kids. Time as a family is always a default for any spare time because guilt drives you towards your kids. The tough one is time as a couple because it's the one that by default comes after everything else and is therefore the first one to get squeezed.
Play "Space War"? As if games on a computer will ever catch on - we're all too busy making turtles and drawing men with them...
Overall it feels that Apple's take is for day to day login it's better than a four digit PIN and it's better than no PIN.