247 karma · joined February 26, 2014
Actually, yes. No sitting posture is one the body should be holding for extended time. We are supposed to move.
I (working in the US) have a handful of friends that work in Germany and UK. The only "bad" thing about US employment is vacation and parental leave. As a male I don't see a need for 12 months but the fact that my wife get shit here (8 weeks of "sick leave" for having a child) is enough to constantly keep my ears open for opportunities in other countries.
We need to stop being surprised and should be saying "about time".
Is that really about gender these days? As a patient, I see it that way too. But that's because the doctor has significantly more education and training.
Are you trying to argue that statistics is its own field and not built upon mathematics?
Agreed.
Your words: some amount of math is helpful.
Do you not see how these are the same idea, abstractly?
Also, "if we define mathematics as 'handling abstractions in a precise manner'"
That IS the definition of mathematics. The author is not arguing for more calculus. His background is mathematical logic which is a standard course before all "real" math (analysis, topology, abstract algebra). All of these subjects handle abstractions in a rigorously precise manner.
It's aggravating. But then later when I can continue a conversation via keyboard the depth and intimacy is much greater.
Maybe as speech to text improves it'll get better.
50-100k/yr is a comfortable life in most places. That's 1.2-2.5 million in capital. Definitely don't have to start a company of be in a start-up for that at all.
But my point was about Statistics. The HR warlords for all those defense/aero companies that have set these limits have done so because it segments the pool of candidates to one with a lower chance of bust (or so they've decided as such).
I'd like to see data, I'm some HR or consulting group somewhere has it. Or maybe it doesnt exist. A simple logistic regression problem with a high number of variables (degree or not, age, major, self-study, continuing ed, etc etc).
edit: also - all my comments are speaking from the engineering side of these companies. not IT. So the actual work content is a bit different than the original article may be concerned with.
The reality is different industries have different standards. I'd probably never pass a SV interview because I'm not ever going to memorize many of the CS fundamentals. I work with EEs, Aeros, MEs that code (robotics types), math physics and chem PHds, etc. Sure there's a few CS guys here and there usually that double majored in phys or math.
On a given day, what's more important to our engineering problems is my understanding of advanced linear algebra topics, not a sorting alg (lot of work in CV recently for ex). We really don't bring anyone into an interview that hasnt studied the full gamut of math required in a math/phys/engineering degree. In such an environment, the interview questions are more about how you solved problems and never the memorization of some sorting alg. Oddly enough, when you weed out everyone that doesn't have a full math curriculum first, you don't seem to find many people that 'cant code'. Go figure.
All these companies require degrees, check GPA, and typically have managers that came from technical backgrounds. While not perfect, this combination reduces the chances that a total dunce slips through. Also, all of the above companies tend to be looking at engineers/physics folk over cs/IT, although in the past 15-20 years a lot more CS.
I work at one of the above and for a long time only EEs were hired for any software positions. In regards to math ability that's a fairly high bar. And math competency is pretty well correlated with the ability to program at all.
Not saying that someone couldn't slip through. But all of the mentioned factors tend to reduce the pool of potential flops vs some of the now-standard hiring practices (from the article).
Based on what?
Can you elaborate on this one? What do you talk about and how do you steer them to their own decisions?
And I'm not merely referring to software. The above is true for my companies 20+ different engineering positions across all disciplines they hire for (Aerospace, mechanical, electrical, materials, software, etc).
>When you get an engineering degree from a certified university, you are an engineer.
That's not true. When you get a degree you have an engineering degree. When you get hired and employed as an engineer, you are an engineer. You have an engineering degree and I have a mathematics degree. Our employers hire people for engineer positions and call them such. If I were a professor of math, i could call myself a professor. If I were a mathematician at the NSA, a Mathematician. But my employer calls me an Engineer. The degree does not do that.