Give it time. MS does what it has always done to competitors (even to MS internal products) that it acquires. Takes awhile sometimes and you younger kid will get to live through what others already have.
64 karma · joined May 18, 2018
Only in theory. In practice, they are 1:1 - You initiate pork A here, I help you add pork B there. You own pork B company, I own pork A. We both win money, forget the constituents.
It's code for above-the-median-wealthy, enough to influence opinion outside of the populist opinion. Why you choose to go partisan over a systemic issue, is beyond me.
I'm not sure how you could have confused what was posted, to be interpreted that way.
What is a manager but someone who has control over the controlled? I'm surprised with so many ppl nodding their head at this list of complaints about bad software processes at bad companies, masquerading as analysis. If you think it takes more than 2 days to learn _how_ to be a Scrum master, you don't understand the role. It's not complicated, difficult, and time-consuming enough to require a singular employee...unless your process is already screwed up. Good luck finding whatever magic bullet you think will save you that isn't Scrum-based teams.
I've never seen this. It smacks of terrible practice that would not last long in a daily CI system. Once you have a good version, locking on to that version is one thing. Just randomly downloading new code versions for a daily build is impractical.
That's not how it appears to everyone. That's often how they are crafted, but this is not a problem with the concept.
http://www.dailymail.co.uk/femail/article-2644251/Un-scrambl...
Not all eggs are treated the same. I don't see how this study accounts for what kind of eggs or how they have been processed. It matters, a lot, if your eggs are bleached or how they have been stored.
It's a terrible idea. Writing and running scripts from Scala is incompatible with certain actions. Specifically provisioning and kernel configuration. There are lots of tasks that Scala is a bad tool.
> https://www.theatlantic.com/education/archive/2016/02/will-t...
> https://jelastic.com/blog/functional-programming-is-a-ghetto...
The concept is that placing a focus on a specific technology is a path to decay (poverty, obsolescence, self-destruction, etc).
> Like these things known as "pen" and "paper", for example.
When you need to share this pen and paper, you use a whiteboard. I don't understand this hate for whiteboards, which are a cross-industry cross-profession standard (including medical) when collaborating.
One of the more interesting things I have noticed is that happy engineers have a little free time each day. They aren't under crushing pressure at all times. To this end, it's very common for whiteboards to accumulate drawings and doodles. This is often turned into "the elaboration game" where one doodle is built upon (by a little or a lot) every now and then. This is probably because coding is problem solving, but also because it's a creative endeavor. Engineers who are happy tend to work around other happy engineers and those engineers are all creative with free time.
That's a pretty common claim and has been for a long time. It's not just verification of identity, but verification of integrity that the encryption is supposed to enforce. Instead, it throws a warning for one case and will not decrypt for another. The binary client is broken, as a security tool (insofar as it fails to provide the security it claims). If the integrity of the message is compromised, why show a version of the decrypted message at all? There's no guarantee that's correct and has led to this.