883 karma · joined August 20, 2017
Signal: @jasondclinton.11
[ my public key: https://keybase.io/jasondclinton; my proof: https://keybase.io/jasondclinton/sigs/DL7kLNV4-17_G3NlqgNDOzGigaqZ72Z8MDwwBybZT9k ]
FWIW, this ShaderToy doesn't seem to work in either Firefox or Chrome for Android. Had to view it on a Linux machine.
Do you have any feedback on that article's thesis that the closure syntax could have been handled better?
No, this isn't true. https://blog.rust-lang.org/2018/07/27/what-is-rust-2018.html... was the last change and it was optional and automated migration.
The only counter example that I can think of is the way that the actix unsafe maintainer's behaviour was handled (brigadiering bands of Reddit evangelists flaming him for his own flaming). However, I chock that up to an anomaly caused by Reddit's toxic community and not representative of the Rust community.
Edit: I donated to the admin's Patreon account in excess of his hosting fees. But, that didn't cover his time, apparently. The admin is still active on GitHub after the server crashed; I guess he just lost interest.
> Employees at this level are astoundingly uninterested in performing well, or, in other words, there is a reason they are working entry-level positions. This makes management yet more difficult because managers may have to become near micro-managers of cat herds trying to get the company to produce whatever it is supposed to produce.
which very much sounds like an indictment of all low skill workers. If you didn't mean that, perhaps you could reword that paragraph.
I haven't managed a business employing low-skilled workers because--and the reason that I grew up on food stamps--my father owned his own small business employing two to three such workers digging ditches or running electrical and construction type work. And the margins were incredibly thin and he paid them almost nothing and we still didn't have enough to eat. At various times throughout my childhood, those workers would inevitably have a heated argument with my father or otherwise steal from or slight him in some way. I think about that time a lot. Part of the reason that I think he continually failed as a manager/owner was that he had worked for medium sized companies when he was younger and went about replicating their management style in his own business. I often wonder if he would have done better if he made and treated these employees more as co-founders in a venture and allowed them have a sense of ownership and self-direction. I'll never know.
And before you accuse me of being upper class, I grew up on food stamps, didn't complete college because I was working full-time to pay my way through it and it just didn't work out, and I worked plenty of terrible, low-skill jobs before I landed a job in tech.
Agree with your post (and upvoted) but wanted to point out that these labor practices common to capitalism and so you're likely to find it just as bad outside of tech. In some industries, worse than others, for sure. But this is the Faustian bargain that we signed up.
(Personally, having worked some really terrible jobs outside of tech, I wouldn't leave it.)
These things are running on technology from the late 90's virtually unchanged. Even the most advanced ones are low end silicon with terrible thermal designs and horrible user interfaces (scrolling through pages of residents on a bad monochrome display one line at a time). Nothing competes with them. They have no high-failure parts and can last for decades. (And some have.)
FAANG compensation is much higher than you think. $200k/year (including stock) in the Bay Area for new grads is common. Yes, the prep for these interviews is insane but what has effectively happened (and this is supported by the article) is that companies have offloaded the selection work to the interviewee: they will only be able to pass if they are willing to do the ridiculous prep work. And yes, the interview questions have nothing to do with the job; that's not the point. Sadly, the process is often selecting for intelligent, compliant worker bees and not, what I would prefer, more creatively-inclined people. I agree with you: depending on what team you end up on, you could be asked to clock-in, crank out code, and clock-out without much creativity or input into anything.
BTW, Google doesn't use brain teasers since 15+ years ago. But, there is the occasional interviewer who asks questions about trivia that only they know about. This is supposed to be banned but there's no consequences for interviewers who do this. Hiring committees (who make the decision) usually throw out these questions when they see them in the list of interview feedback that they are using to make a decision.
Re: age. I worked on a team at FAANG that has tried very hard to hire folks with industry experience and we haven't found any resistance from interviewers to that. However, when talking to potential interviewees, we have found that very few are willing to subject themselves to the interviewing process for the reasons that you've outlined above. I don't blame them.
And please don't reply, "But there are programs!" Governments and NGOs convince voters and donors that they are doing something by creating programs for domestic violence and then make those programs so difficult to enroll in that they spend half of their funding creating labrythine beurocracy. Anyone already at their mental capacity with abuse struggles even starting these processes.