I think this, in some way, can be interpreted in a way favorable to the original parent's comment. Kids being stressed by climate change to the point that their feelings overwhelm all of their coping mechanisms is not an effective strategy for actually fixing the root cause.
Ideally, kids would develop, by trial and error, effective strategies for identifying solvable problems and dealing with them, and not being extremely negatively affected by (directly) unsolvable problems. It would be beneficial for society if people heard about climate change and thought, "Okay, that won't be good, so what are some things I can do in the short term and in the long term to make a positive impact?" The great thing about such an approach is that it's omni-applicable, such as when one's car breaks down on a long drive, etc.
Parents who constantly hover around their kids presumably interfere with this vital process, perhaps because these important lessons can only be discovered, not forcibly taught.
Yep, the fastest way to spot a fake positive review is to notice those seem to be written from the perspective of HR, focusing on things like "fast growth" and "lots of opportunities" that are of little to no concern for the typical person, especially if they're listed as the sole positives. A typical dev is less concerned with the growth rate of the company and how many offices are opening in places thousands of miles away -- they're more concerned about their local delivery team, their local office, etc.
First time taking a look at that site and I'm pretty sure a lot of it is trolling. Lots of threads starting with something semi-ridiculous or controversial to solicit lots of responses to which the OP spends an unreasonable amount of time responding to. Classic flame baiting.
Agreed. Think of how ridiculous it would be to make a half-day task for figuring out X -- sometimes I've spent days, even weeks, trying to figure out how a module works.
In practice, being able to break things down meaningfully and accurately to such a minute level implies that a lot of time was spent in grooming, which means we're just back to waterfall again. (Or the tasks at hand really are just that simple and/or the people involved have a lot of expertise.)
This is just my experience, but I know that many people weren't enthused by the fact that computer science classes were absolutely packed with people. Obviously this depends on the school, but if class sizes of 200+ persist even after the first few intro courses, it'll whittle down the number of people pursing the major for a variety of reasons, such as poorer quality instruction and the inability of those who need a bit of help to get it as the line outside the TA's office is in the dozens.
It just strikes me as amusing, since the tremendous amount of whining about how much of compilation time (compile-time) generics would add makes the issue appear important, yet here we have a 2-10x compilation time slowdown, but in this case it's suddenly totally fine -- the Go community is obsessed about the wrong things.
I'm not sure about your sampling of "many". I can count the number of interviews where my code was actually looked at on one hand; no doubt this is different for unicorn-type companies.
At any rate, enter the law of triviality. Making something simple that lots of people will understand is more likely to lead to more stars than something brilliant but complex, yet more indicative of development skill. This selects for gaming of the system and/or salesmanship; no doubt said employers will screech about a lack of "qualified" candidates before long.
I'd advise people in that position to do the opposite: go to work for a year or a few years, after which you're in a much better position to decide whether you have the drive and/or discipline to finish.
As someone who did this, there's a caveat not typically mentioned. It's much more difficult to get an internship as a CC student than as a university student. Thus, by the time you transfer to university, you're going to be competing for your first internship with people who have already done 1-2 because they were already at university for 2 years.
The issue comes down to whether it's reasonable to expect a very large number of people to try to emulate the work of the true professional theorists. For the average programmer, it might be nice to know once in a while, but why this continued emphasis on a (formal) theoretical background?
I'd expect there to be a higher proportion of intelligent immigrants via controlled immigration. Those who merely have to just hop the border are less likely to be engineers, doctors, etc., while Europeans and Asians have no choice but to deal with the legal system which can vet them.
There's no geometric complement in my mind. At times it's useful to think of "wholeness" base 10, so 4 and 6 fit together, and when adding numbers, I sometimes find the nearest multiple of 10 and then go lower from there. I don't picture numbers in the abstract (e.g. 178); when they refer to something else (e.g. 2 coins), they're a description or a property.
The advantage that Go has with regard to green threads is that the language and its standard library are built around them. There's no easy way to introduce them into a language via a library with the same level of simplicity.
Somewhat unrelated, but AP courses can often be easier for brighter students as they generally keep disruptive clowns out and offer more engaging material instead of boring busywork. The classes are thus more like college classes and less like babysitting sessions.
It's basically an unremarkable C-ish language with an advanced green threading library built in. Channels and green threads aren't that difficult to replicate, but select is.
This happens because almost every time there's someone who more or less asks what in the world generics are for since they can do everything they want to with Go's type system. Sure, it's possible, but it's missing the point.
Well, will great programmers line up at the "great programmers" H1B line? Probably not. Will the government screen applicants in order to increase the concentration of "great programmers"? Hah. There are no means available to us to increase the concentration of great programmers in a pool of programmers without great cost, and this inevitably means that in order to get more great programmers, one has to go through more programmers.
Are those the problems that are best solved by throwing more and more programmers at them? If anything, the people doing the grunt work would be PhD students (save the shaders, perhaps).