Yunk
If who is OK with what? The Maldives is a republic and has to follow its laws and process to consider arresting someone on a foreign nations behalf and then consider the extradition.
Republics with executive branches that don't consistently enforce their mandates need to be punished by the world community before a mafia of rampantly criminal executive branches emerges and undermines all democratic republics. Oh wait.
> I won't say anything about Python.
I will try to learn from your wisdom.
Transitioning first classes from C to go would make great sense, but it looks like a lot of schools already replaced C with Java and C++ as first languages.
Personally, I do think there is merit in teaching a primarily imperative language first, if only to appreciate other paradigms later and get an inkling of what is really going on beneath your code.
Adding further difficulties to international transfers may encourage expats to recalculate their positions. Then there will be further network damages. I would rank the average US Diaspora as less positive about getting involved with a US based business partner than the average European due to familiarity with the US' regulatory style and its chaotic results.
For example, significant genetic factors may be: healing or failing to heal without permanent damage or being flexible in a way that causes or prevents a frequent injury.
For many star players the fact that they can keep playing at all may be the freak of genetics or initial behavior that allowed them to get to their level.
For example, football helmet impact data seems to support the direction that many should be dropping out due to traumatic brain injury. Yet some players deteriorate remarkably slower than medical science previously predicted.
Personally, I went back further in the domain to avoid admitting I never had more than zero interest in what RFC writers chose to call something. Really, I view domains as bastions of useless information aside from the harvestable concepts for problems in other domains.
But I am beginning to suspect the industry has 'matured' into the same crap as the auto industry.
I'm curious if others have comments on remaining a generalist in this environment?
This is a false dichotomy. The path to getting rich involves being moderately successful and then being willing to risk entering poverty again. If your goal is to not be poor then your best odds are to try to be moderately successful and then reinforce that position rather than playing double or nothing forever.
In development, who would do design, code and review on only one change in a straight sequence? It is like asking half your brain to shut down and the gods to smite you.
If Barclay's could get HFTs out of their products then their situation wouldn't be much different from diet cola and they could raise a fair amount of FUD against the competition irregardless of quality of evidence. But you can't sell the same product yet claim you have removed the "harmful" component. Claiming you know it is not really harmful just means you were up to 2 fraudulent activities to deprive the market and your customers of a better arrangement.
These odds are hardly a compelling reason to continue warning about lighting safety given that the resulting behavior changes might be leading to more of the common causes of death.
Personally, I am a long time C developer but I simply ignore any postings with "C/C++" and no longer use C very much when I have an option to use a language that is easier to find alone in job listings.
If you are serious about C++ part time then I would suggest something rather write-only in a small group. For example, I did consider learning some OpenMP and working with research scientists. That is a nicer situation since most groups end up using a reasonably small dialect to stay focused on the task and you probably wont waste limited experience time reviewing arbitrarily bad code that misuses esoteric features. But that is exactly why it doesn't adequately prepare you for situations like Banks or make you a "C++ Developer" instead of a good programmer who happens to be using C++.
Fast + Legacy = Finance
But based on complaints I hear here in Zurich, the OP would never become qualified learning C++ part time to be the local expert directing offshore junior engineers.
If you want to compete with people who will have more hours of experience then choose a playing field with a reduced instruction set so you will also have had adequate hours with everything and you will only lose out against the minority who continue mastering the subject instead of just getting good enough.
C++ is the wrong direction for someone with a life because it rewards almost every hour of learning equally (or equally poorly depending on your opinions and futures predictions.)
I like your hypothesis, but I also don't care if the gratification test was flawed due to alien possession. They still point to something earlier in development that probably isn't equally distributed among 'cool' and 'nerd' kids nor fully segregated. If there is a socioeconomic component then the relation to this hidden variable would be similar for eye color too.
So the point of the study verse another study using eye color is questionable to me.
But I'm not really saying behavior inhibition has an adequate explanatory power, just that it is confounding. Just one quantitative measure like gratification delay is enough to make a qualitative measure like coolness a worthless subject.
Our 'coolness' meters collapse metrics, for example: inhibition may make you cooler in one case (not quoting sci-fi) and total nerd in another (not being rebellious.)
Therefore the question doesn't necessarily work given that the ability to inhibit behavior is strongly correlated to success.
But I think it is an ironic part of social nature that we continue to reward those who take it too far on the social side of the spectrum (just complaining about them we seem to make them into a necessary quirk of the place or create a miscommunication that gets them a new position) while we let a lot of brilliant people go just because they look like they are on the other side of the spectrum to people who don't see their quieter exchanges.
If managers could account for the hours of utility he stole from others, I think it would be a separate reason to put him on probation. (I know he was on probation for his own output since that was the topic of many of his visits to one of my neighbors who in turn wasted my time complaining about his tedious visits just as I waste yours now. So ends my postmodern fable.)
Yep, we had an engineer who spent 40 hours a week going around and building social connections.. Where did he find the time?
But the subtext in the article makes it pretty clear. They are tracking cost of design as accurately as unit costs.
It is largely an "in for a dime in for a dollar" scenario for each internal engineer when they approve a design direction that appears to cut a cost. The larger oversight is unaware of some of the hidden issues and each engineer is motivated to paper over them to some extent to protect their relative standing. The engineers who are completely transparent are completely unemployed.
(For example, Solaris x86 clearly favored 1-2 specific windows/mac laptops --which could be ordered on a fast track internally-- and supported the bundled devices on those laptops if the device's type was supported at all. Swapping the external reference every few years was annoying but cheap and limited the arguments to selecting among actual configurations rather than future possibilities.)
I would hope there is another reason is like getting a reliable ABI and clear licensing for the DSP side software? Otherwise, offering a better OS on a few models of android phones will be more useful now, and then again as used Android phones enter the emerging markets.
There is a purpose besides leisure, selling to the leisure group or building technologies to improve the internet's effectiveness for selling to the leisure group?
Looking at pictures of cats, pornography and buying trinkets are all clearly leisure activities.. but commenting on vaporous articles about living underwater is something I expect to get academic credit for according to the social norms established by scholastic reports.
Content providers that depend on the US may want to synchronize on specific day of the week to limit each ISP, for example Comcast Thursday, while foreign providers can conservatively cut off all of the US so they don't have to worry about missing any future pay networks..
This sounds like an oxymoron which would imply the two sides of the transaction have separate expectations.
As reasonable developers, do we build out the system, security, data backup plan of a "prototype"? As reasonable buyers do we "launch" an application without them?
Personally, I mark everything I think is meaningful to a human and check that google thinks it is validly formed and how they would display it, but I don't rely on whether they do. With good and consistent metadata, Client side code+CSS can be a bit cleaner and better abstracted and it seems to help a little in the long tail of search engines/aggregators, etc.
Of course it helps if the junior developer also has a project (or any other tasks) matching their current skill set to work on so issues don't have to be solved in real-time to prevent idle+frustrated engineers.
I've actually had more trouble with local mentoring. It is hard to get people thinking deeply about how something works and how to solve problems when they know an answer is a few grunts away.