I remember times in 90's when we planned a software system in UML powered tool called Rational Rose. Oh my god its was clumsy and slow process. But yes, sequence diagrams are very useful tool.
It may be dumb question, but is there any realistic use case to use this vulnerability to reveal SHA-3 hashed secrets? Or is it just that attacker can crash systems with suitable input?
We should reduce pollution, not panic about weather. Seas are full of plastic and organic waste, dry land too, rain forests are burned down to make more field. I don't claim that human would not affect to climate, but it is extremely difficult to prove statistically when the data we have is something like 100 years from the full 5 billion years of existence of earth. How can you take all factors into account in this kind of statistical analysis?
Actually I agree with you as I would not be able to program much without Google today. But many reported here about interview situations where they had like white paper and task to develop something. It is something they never face in real work.
I developed software professionally over 20 years and I get impression that I would not have survived any of these interviews. I remember the times in 90's when I had most of the Java classes & methods in my "working memory", but after that came syntax helpers and search engines. That ruined whole concept of programming with just text editor. I don't know if anyone else has similar experiences.
How can the jet length to be determined? In my very limited understanding jet is a continuous stream of particles/radiation. Doesn't it continue forever, unless the flow hits some barrier?
I still feel somewhat that Mongo is blamed for things that it is not supposed to do. Removing millions of records surely is not a usecase that Mongo is comfortable with. Or if you absolutely need a schema to protect developer doing silly things, then traditional relational database is surely way to go. Mongo is superbly quick to serve read-heavy applications. I did one project with Mongo & Sinatra and the app was able to reach high transaction/second rates compared to the hardware stack it was running on. Of course we faced issues to design trustworthy design for very high scaling. I think it is one culprit with Mongo, sharding and things. But anyway, we as developers and architects, just need to have right tools for the task we try to solve!
Options for employees are typically worth of nothing. I've seen sad stories of stupid+greedy employees who have taken huge loans to buy them and lost serious amount of money.
Much boils down to the question about the quality of the metrics. In my work they are just numbers that are manipulated to look good so that everyone gets their bonuses and the bosses are happy.