Reminds me of SK751 [1] where an automated system prevented the pilots from powering down a broken engine, resulting in both engines failing and the plane crash landing in a field north of Stockholm.
Programming is a skill just like management. I would argue that if you spend 5% writing and 95% reading you won't be maintaining that skill.
If you come from a strong technical background when first promoted (Being the go-to expert on the team or similar) then you can probably keep the respect of the team for a while but eventually others will rise to fill the gap (After all there is 95% of a rockstar programmer's time missing in the team). At that point your comments on code reviews will mostly be seen as micro management.
I would say that there are two ways to go about it, either fully trust your developers and let them develop and review their own code or stay as an active member of the team, doing as much coding as you can fit into your schedule. Which route you pick of course depends on the workload of managerial duties.
This doesn't mesh with my experience. The skill of programming is not in writing code, it is in constructing solutions using code. For someone who has already written software for a long time, I believe critical reading and discussion of code keeps the skill just as sharp.
Reading lots of code also gives a broader perspective than writing lots of code, which requires a sort of tunnel vision. Both the deep and the broad perspective are useful on a team.
>I would argue that if you spend 5% writing and 95% reading you won't be maintaining that skill.
The amount a developer (not manager) should code varies from domain to domain. In my work, 5% may be on the low side. But I'd argue in most domains, if you're spending more than 20-30% of your time coding, you're overdoing it and creating too much technical debt.
I'm not a manager, but if I were, I'd promote the folks who find (good) reasons not to code than to code. Some problems need software to solve a problem. But writing software should be a last resort.
Of course, if you're writing throwaway code on a code base that won't last more than a year or two, code away. Technical debt is not a big concern.
But if he's worried about the Swedish police violating Swedish law, why would he care about whether or not the case is closed? If the CIA/Swedish police were to snatch him, in blatant violation of a number of laws, it's not like they would hold back just because some rape charges were dropped?
The fact that he was in Sweden already? And the fact that he fled to the UK, the closest ally of the US in Europe as well as a NATO country, unlike Sweden? And perhaps the fact that he now plans to seek asylum in France, another NATO country?
It's very convenient how this conspiracy theory of the US snatching Assange from Sweden cropped up just as he was accused of a crime in Sweden I would say.
None of this requires a conspiracy theory or 'snatching'. Assange is scared of being arrested, and once he is in custody, being extradited to the US somehow. The Sweden/UK details are irrelevant.
The conspiracy theory is the one that he will be extradited to the US on "secret charges" as soon as he is arrested in Sweden. Some others in this thread compared it to other CIA grabs, for example one in Italy.
It does not but it limits the possibility to prosecute which is what the prosecutor came to terms with, at least according to her comments on the Swedish evening news. Basically the statue of limitations for this crime is 10 years, it's now been 7 and there is no resolution in sight so it's basically just a waste of time and money. Embarrassing if you ask me but that's the way it is.
