>Companies find it incredibly hard to reliably staff positions with hard-working generalists who operate autonomously and have high risk tolerances. This is not the modal employee, including at places which are justifiably proud of the skill/diligence/etc of their employees. I'm not sure if he's saying these hard-working generalists are hard to find, or undesirable to employ?
Could someone elaborate what specifically is meant with having high risk tolerances?
I wouldn't dream of speaking for Patrick but I believe it's something along the lines of:
unreasonable deadlines, non-existent documentation for existing systems, non-existent QA processes, unavailable/non-existent support staff, undocumented/unclear requirements, etc.
There's also gulf a between what companies think they need, and what they actually need. Almost everyone hires on technologies and not the abstract skillsets required to learn said technologies.
Any Idea how to find a company that hires on that abstract skillset, potentially by throwing one into cold water to test for it? ~Someone with little resume-driven experience but good grogging skills
No, I wish. The closest you'll get is companies that might hire on transferrable skillsets (e.g., Ruby Python). The best thing you can do is have a portfolio of work that shows your understanding. It's what we had to do when I was doing graphic design and illustration work.
Your average undergrad program... CS degree never doing anything novel in CS Is this different than any other field? I was under the impression that most BS programs do not require novel research. That doesn't come until post graduate courses.
I don't necessarily mean publishable—that's doable but difficult in CS—but novel in the sense of requiring non-trivial creativity and insight within the field rather than replaying things you were taught directly. An example might be writing a compiler for a language you design with features not covered in the book. It's probably not publishable, but it is doing CS in a way that just following instructions in a book…
You just must have had a bad CS program, my undergraduate degree involved plenty of those types of projects.
I think the anecdote and OP’s statement support one another - companies have a hard time reliably staffing generalists and one of the reasons for that is that they are bad at identifying them and determining how to use them. Parent showed them a generalist skill set and they saw a lack of professionalism.
It'd be straightforward to find/get a programming job that'd more than take care of my material needs. There are a buttload of entry/intermediate level jobs out there that'd provide more money than I even know what to do with. If I wanted a job really bad, I could study up for it, put the technologies they're looking for on my resume and apply. The hard part is giving in to a job . I think my hesitancy in this area s…
A salaried job that only gives you 5-10hrs/week is a niche unto itself.
> People underestimate how effective a generalist can be at things which are done by specialists. People underestimate how deep specialties can run. These are simultaneously true. This is really, really important. In my experience, this is not just unknown but actively ignored and disagreed with (either explicitly or effectively) by a large majority of people involved in software businesses. This hamstrings: companie…
There's also often a messy transition period where a team goes from a bunch of generalists to more specialists. This can be extremely rocky for all involved as often generalists have lots of historic operational knowledge and strong opinions, but the new specialists come with external knowledge of best practices and how to scale. It is important that historic knowledge is respected for the context it provides, while…
I think companies need _both_. Specialists can miss the forest for the trees, and at some point you need to go into the last 20 of the 80/20 rule, which requires supplementing or specializing your generalists.
And I believe it's entirely possible to be both; to be a better specialist you need to be a better generalist, and vice versa.
It's not just an IQ test, it's a test of ability, which is different. Your college record shows that you a) Whether you were able to get the work done. b) Whether you were smart enough to do the work well. It's the combination that's important, not either single one. Employers want people who show up on time, actually care enough to try, and are smart enough to figure it out. The college degree has a better than zero…
I agree with all of that, though spending 4 years to make that determination seems crazy to me. A competent employer can figure out which hires are worthwhile in about a month or so. There’s another issue with using educational attainment as a proxy of intelligence: it doesn’t really help you distinguish among candidates who all have a bachelors degree. All you know is that they’re above some threshold, but not how f…
IQ test tell you how good someone is at pattern recognition, which is a major factor in abilo to learn. It doesn't tell you what they have learned, or if they have the criticality important skill of perseverance/grit. In fact, high IQ can reduce grit, since clever pattern matchers use their cleverness to avoid working hard on the toy problems of childhood.
I agree with most points except this one: >> Most open source software is written by programmers who are full-time employed by companies which directly consume the software, at the explicit or implicit blessing of their employers. It is not charity work, any more than they charitably file taxes. Most open source projects don't go anywhere... They have about 3 stars on Github and nobody uses them. To say that open sou…
You're making the mistake of assuming open source means "something you that's not your job."
This is false.
Most open source development is paid work. Many people "get into open source" by accepting a regular day job.
Your link is to a story about an employer who uses a test which is a proxy for intelligence (they even give the rough equivalency between the test they use and IQ). I think that supports my point that intelligence is one of the more important things employers are looking for. Most employers don’t have the resources to develop a hiring screening test and then certify that it is not discriminatory, so they use educatio…
IQ tests used for hiring do exist in the US - https://en.wikipedia.org/wiki/Wonderlic_test