487 karma · joined June 9, 2014
However, CS fundamentals are the language of software engineering. It's important for engineers to be able to communicate efficiently about things like runtime analysis, indexes, concurrency models, type systems, etc.
Your mechanic knows how a carburetor works, (s)he knows how brakes work. Mechanics have a common set of fundamentals that they all know and share, and can use to communicate with each other about their work. The purpose of this knowledge is not to be able to fabricate new car parts, although given time and the right equipment, it could probably be done.
The purpose of CS fundamentals is not to so much to implement complex algorithms, as to understand how to use tools and libraries that are based on them.
Training flights are mostly in the vicinity of the airport so speed and range matters less. But you do still have to get places (eg the practice area and back) and a really slow plane is going to make a difference in the number of flight hours you need to accomplish the missions.
Then, all possible expertise about how to determine if the AOA input is valid (and I'm sure there are many, many, such factors, redundant physical sensors being just one) can be directed to that one AOA sensing system.
If MCAS gets an input of "I don't know" from the AOA sensing system, then clearly it is going to disable itself. So, a complex decision has been turned into a very simple one.
If you agree with me, then this is a really important example of why separation of concerns is so important.
Now he’s amending his opinion to state that estimation is not really the core issue. The core issue is that projects are doomed from the start by mismanagement. Issues such as: racing to catch up with a competitor (giving the s/w group an impossible deadline), or starting a project whose business value is so low that minor time and cost overruns reduce the actual value to below zero (at which point people start blame shifting to try and hold on to their jobs).
For example:
“We have a very skilled and competent work force and the last thing we want to do is lose them when we’re assuming this economy is going to come back,” said Craig Reider
Unfortunately, most enterprises are still not willing to outsource their IT platform to the real pros and thereby make it someone else’s problem to keep that infrastructure up and running. They want to build their own in-house competency. But the problem is, if you’re a true DevOps pro, why would you work for some random company in which IT is considered a cost center, rather than working for either a hosted platform provider or a (for lack of a better phrase) “independent provider of DevOps”?
IT and security managers are able to convince business executives that IT infrastructure needs to be kept in-house, even though today’s typical enterprise has no chance of actually building and maintaining a infrastructure that is 1% as good as what they could rent from a dedicated provider.
So is there any other advantage to ion propulsion besides quiet operation?
In any case I live in Massachusetts and had steam heat for many years and found these books super helpful. There are however some plumbers around here that know their way around these systems.
Another really common mistake is tasks being performed inside the web request that should instead be offloaded to background job processing. If something is going to take more than milliseconds, it should be a job. If you see a PR where someone is bumping up the HTTP timeout in order to keep their slow processing request from being timed out by the webserver, they are doing something inline that should actually be a job.
For example if you are trying to figure out how to add things like flexible initialization logic, security protections, clever MIME type handling, Cucumber testing, and better routing, you’ll find that Rails has these things built in.
What you can’t get from Rails is the “one file application” that’s the killer feature of Sinatra. But all those files and directories in Rails are doing stuff that you’ll eventually want.
The largest subcategory was Economics, which is considered a humanity subject at MIT.
The driver of the “phone addiction” problem is obviously direct economics. Companies are organized around profit, and more phone time means more profit (especially in ad-driven models like Facebook).
So how about addressing the problems by looking at root causes?
If your use case fits into a scenario which is handled by an existing buildpack, then the claim is that you’ll be better off using the buildpack because the infrastructure can make optimizations that can’t be made with arbitrary containers.
If your use case isn’t covered by a buildpack, then you can either (1) make a buildpack or (2) revert to raw containers.
(Although your platform may not allow (2)).
https://www.reddit.com/r/askscience/comments/2n6zo0/comment/...
I don’t think there’s any way for Bob to determine whether the particle stream has been measured by Alice or not.
I believe that using Dynamic Secrets is HashiCorp's proposal for how to mitigate this; leave the secrets in the log files, but make sure they expire in a timely manner.
In some scenarios it’s possible to at least avoid introducing another vault-specific credential. For example if your workload is running in a managed environment like AWS or Kubernetes, the platform provides a credential automatically (IAM role or service account). If the vault can recognize this platform credential and map it to a role defined in the vault, then you are using the platform credential as the “secret 0”.
It’s still not completely idiot proof because you have to define the mapping between platform roles and vault roles, and define permissions between vault roles and secrets.
And of course the detailed workflows for doing this vary between vaults.
I would like to see loot boxes out of games for players under 18. Loot boxes are not a real part of the game anyway, they are a way for the publisher add the types of subconscious psychological rewards to “increase engagement” that are now rightfully criticized in platforms like Facebook.
"A single toxic employee who is a bad fit for the existing culture can tank the morale and productivity of an entire team. "
So, is there really more to "culture fit" than the No Asshole Rule (1)? If not, can we start calling it what it is: "asshole rejection screening". Then maybe we can use the word "culture fit" less (maybe even "culture" less), because requiring new employees to "fit a culture" is pretty lacking in concrete justification.