In theory it shouldn't, but in practice people don't make perfect code that doesn't have vulnerabilities. But a lot of people would argue that by having many reviewers, you're reducing vulnerabilities. Thus, my stance is that "it depends on the situation"
There are various reasons that people may ask to be exempt. Two that most comes to mind are:
1. Explicit or roundabout pressure from the managers
2. Being expected to produce the same outcome despite reduced work time
Both of which seems like a inertia issue with the culture not following the change. That would probably stabilize over time if a actual rule sets in place.
"It will protect against both malicious activities and accidents (e.g. an employee’s child accidentally wiping a mailbox)."
Can someone help me understand how a child accidentally wiping a mailbox is related to encryption? Isn't this just a matter of putting a password on your computer and not related to encryption?
which is pretty ineffective since mosquitos are quite good at finding the body part that's uncovered. If you sleep like a cocoon and don't move i guess that works.
Very true. As a Korean, it really annoyed me that there were products that Korea or Japan had the first foot out on but could not go globally because it's not based on USA.
Although nowadays I don't think that's so much the case. Currently, I think America has more ideas coming out because it really is more innovative
Hey I'm curious about your journey than the final result. I only skimmed through the code, so I don't understand everything, but it seems that the list of things it will identify is in the "yaml" files. Did you write out all of them or was there a pre-existing database somewhere?
Ironically though, equipment that is supposed to last a long time and hasn't progressed that much over the years are lasting shorter. Examples are cars, microwaves, fridges, washing machines, etc. Recent cars for example on average malfunction quicker than ones 20 years ago.
So in that sense, technology that does not progress fast does not necessarily improve reliability
I agree. It's no brainer that repetition helps retention. If you gave your mind a time to think about what you learned, obviously you would retain it more.
Depends on how much protein she's consuming. If she consumes too much protein, she'll no longer be on ketogenesis. It doesn't say in the article how much fat she's consuming vs protein, but judging by her saying she's mainly eating meat, I don't think she's on ketogensis.
In that case, there would be a generally expected hours. You would still have to allocate expected finish time based on how many hours you are expecting to work per day.
Similar experience here. For me, the changing point was meeting a coworker who wanted to study and work on personal projects with me. So, one suggestion I can make is trying to work in various companies and find a buddy that can help u find your interest.
I was actually interested in Sourcetrail, but the biggest drawback for me was not being able to use it without GUI. Is there any way to get an option to work with the dependency tree from the commandline?