Wat.
969 karma · joined May 3, 2013
Wat.
Source?
Edit: Sorry, that was lazy of me. Googled: https://mspoweruser.com/cio-surey-finds-microsoft-azure-will...
A bit of a biased source, "mspoweruser".
Read a bit more.. We'll have to see how the offerings change or evolve in the next 5 years.
Edit 2: https://rcpmag.com/articles/2016/08/02/microsoft-behind-aws-... AWS is still > 30% of the overall market, Azure hitting around ~9%.
Would you be comfortable moving something fragile by hand that is worth a lot of money? Maybe. Would you prefer if the fragile item being moved was done with an automated process that was shown to best protect fragile items? I would.
"I'm really sorry I caused that car accident." "That's okay, next time take Driver's Ed and don't drive on sidewalks." "Thanks, I'll make sure to do that... by the way, why can I even drive on the sidewalk in the first place? Why wasn't it required to take Driver's Ed?"
I'm very obviously using hyperbole here, but questioning a process, to me, often shows a level of maturity in engineering. It's not blame-shifting - you clearly still made the mistake - but it's fixing a root cause.
I do think it has to be brought up carefully and with the right tone at the right time though.
That can be radically difficult because of gerrymandering.
That aside, launching a public campaign, garnering votes, and voting on a _single issue_ is often the wrong way to elect a representative.
For instance, I think the 2nd amendment is actually a good idea to prevent invasion of a foreign force (an armed population is very hard to rule over). However, I pretty much never vote for candidates that support the 2nd amendment because they often also deny climate change, vote for private prison control, etc. I can't go with their whole platform. I don't want them representing me.
So in those cases, when you have one issue - especially when it's just part of a whole (e.g. just section 1201) - it seems like the right approach, especially when you think there's a piece of legislation (like the Constitution) that supersedes and invalidates the legislation you're looking at.
Sheesh.
This is neat though. Not sure how I feel about the global packages. I feel like it's a strength to have libraries pulled down exclusively per-project.
Additionally the title is "Working at Genius", not "How code reviews work at genius.com"
It's comparing the build stage vs the literal produce-the-thing stage.
I also think the stoppage of the production line happens in software.
If my code breaks while in production, I grab as many log files and stats as I can, roll back the code, deploy, and then study exactly why everything failed, and if we recovered post rollback.
That seems like the similar case on the car production line - haul the faulty model aside (get the logs/metrics), figure out exactly what happened, fix it.
Who knows how the actual assembly line was put together. Maybe they iterated hundreds of times.
I don't expect my code to fail in production, otherwise I wouldn't have put it in production, but I understand it _may_ fail. That's why I put in logging and metrics collection, the same way those engineers hauled aside the car.
It would be very unfortunate if this turns into Gattaca though.
In this case it may just be poor wording. It doesn't say that they cared that they had to pay more, just that it was required to get people to work, which seems reasonable as you said.
These are questions for the business, but I feel like Mixpanel could add so much more context. "We noticed that 'time to first interaction' has gone down with 'watched home page video'." That would at least be a clue.
MP has the data, but all of that analysis is manual (or was, last time I used it).
So imagine what bots often don't have.
Adding JS interaction and cookies takes more effort on the part of the programmer writing a bot.
So yeah, you'd look a lot more like a robot. How else would you quickly differentiate between human vs non-human based on a single request, or even a collection of requests over time? It's a game of stats at scale.
That leads to further evangelism at conferences, more talk about how C# is great and the platform is excellent, etc. I think they hope to persuade entire dev shops to switch over, rather than single devs, in a very long-term sort of way -- even if it's just a small percentage that change, the press is potentially worth it. MS has an image problem, and this would help mobilize their core to speak to more of the good parts.
It does not sound like you can run VS on different devices.
One says "Personal", and lets you continue along without pricing being mentioned.
Then there's a "Business" link that forces you talk with Bitly -- I'm assuming because you would have immediately been notified that it cost money.
You abused a service, and now you're upset because you can't scam them. Cool.
* Who is the customer?
* What is the pain point?
* How do you make money?
There should be computer science, and then there should be software engineering. One is in the sciences school, one is in an engineering school.
I bet the engineering enrollment would be significantly higher.