Speaking of your tests - your general coding skills one has an actual bug in the code, as of a few hours ago (I sent an email about it, hopefully it gets fixed)
215 karma · joined March 2, 2011
You can read about some non-degree holders in the industry here: https://www.nocsdegree.com/
I'm not saying it's easy. There's a vast amount to know and master, and it will require a lot of practice building things to get the skills required. Not to mention study to get through the hiring hoops of algorithmic problems candidates are expected to solve at major companies during interviews.
Age may make it more difficult, but in the end what you’re able to do matters most.
A better source might be the Bureau of Labor Statistics - https://www.bls.gov/cps/demographics.htm#age - which shows
* 68% of "Computer Programmers" older than age 35,
* 45% of "Computer Programmers" above age 45.
* 29% of "Web Developers" above age 45
So I'm curious how they define hard/easy.
If I'm unsure on how long before there will be a worthwhile upgrade, am I paying $80 for this app, or $400? Its a bit like being told that you can buy an item but won't know its real cost upfront.
I understand subscription models where they offer something that's ongoing (remove disk, sync, whatever) but I find this model annoying and its forced me to change software I use quite a bit in the last few years (most recently moving off 1password).
Charge me more if you have to, but stop this "keep paying forever" madness.
Try to remember, this is the country where a range check function resulted in a lawsuit:
private static void rangeCheck(int arrayLen, int fromIndex, int toIndex {
if (fromIndex > toIndex)
throw new IllegalArgumentException("fromIndex(" + fromIndex +
") > toIndex(" + toIndex+")");
if (fromIndex < 0)
throw new ArrayIndexOutOfBoundsException(fromIndex);
if (toIndex > arrayLen)
throw new ArrayIndexOutOfBoundsException(toIndex);
}I'm not sure that's true. I've lost track of the number of software engineers I know who are in at least the low 200's Total Comp (in Texas).
Common? Probably not. Rarified? Not as much as you think. There's two just on my current team.
It lets them use it as a jumping off point for some hardware: https://www.google.com/chromebook/find/?utm_source=en-ha-na-...
And it appears they now have an enterprise version: https://www.blog.google/topics/connected-workspaces/introduc...
I'm sure there's more, but I imagine, financially, I could have stopped after the first one.
* how a B-Tree index is structured (and how that affects range queries, and wildcard queries)
* how a query uses a single index per table, or can create a merge index
* how a covering index increases performance
* how composite indexes affect queries, why you don't need an index on both (col-a) and (col-a, col-b)
Diceware, 6 words 2.2 x 10^23
Diceware, 5 words 2.8 x 10^19
Diceware, 4 words 3.6 x 10^15
a-zA-Z0-9, symbols, 10 4.3 x 10^19
a-zA-Z0-9, 10char 8.4 x 10^17
a-zA-Z0-9, 8char 2.2 x 10^15
The engineer with a compensation package worth 150k in Silicon Valley isn't the same as the guy with the same package in Austin.
* People contribute between 0 to X% to a 401k.
This couldn't be deduced from take-home.
* Many companies have a Employee Stock Purchase Program,
which is deducted from payroll.
* Some (Many?) programmers get a large chunk of
compensation in options or RSUs.
Still impressive!
The characters are pleasing, easy to read, and really I just find them nice. http://www.lucasfonts.com/fonts/thesansmono/thesansmono-offi...
These folks with many "senior" level positions on their resume can't manage a task our last hire did in about 6 minutes.
There's a gap between knowing concepts and knowing how to apply those concepts. There's actually a certain (limited) amount of artistry to writing code. Hiring a programmer without seeing code is like hiring an Architect without ever having seen a house he's designed.
You can do whatever you want with open source software once you have it, but saying its open source and charging for access to it are not mutually exclusive options.
They can write code but they don't understand half of the libraries or technologies used. They learn the abstraction layers but have no interest in knowing how things work. And these symptoms get worse with age.
There's a point where most people get tired of relearning their skills; they no longer peruse new information in spare time, or even at work. If you aren't always learning, and examining things on a deep level, yes you'll be sunk by your forties. But I believe this is a choice on your part.
To begin with, Joe isn't working for you; you're Joe's product. That answer would be enough to turn me away.
Where are Joe's Interests aligned? With yours? No, Joe wants to place you in a job, at any salary. Joe's company gets 30% of your first year's income from the employer, and Joe himself gets a much smaller slice. Joe's slice of $120k is similar enough to his slice of 130k that he beneifts most from placing you at any salary he can get you to accept, and then moving on to the next position.
Ah. So Joe's interests must be aligned with the hiring company, right? Only to the extent that Joe needs them to hire you (or someone like you) and he needs you to last at least X months so he doesn't get a claw back. His interests are more closely aligned with the company than yours, but ultimately its about filling seats for Joe. He wants to convince the company that each candidate is THE candidate.
Does this sound like a guy you want to help you find employment?
And finally, in the form of purely anecdotal personal experience, I've had recruiters flat out lie about aspects of the position. At the time I was too naive to verify facts with the employer.