It's like that in the US. My spouse got all sorts of pressure to breast feed. However she was not producing enough milk and we ended up supplementing so our children can get enough nutrients. The amount of bullying in this area is approaching ridiculous levels.
I looked at the API calls on the CrowdStrike blog post and I have been using parts of these API's for calls in PowerShell for at least the past year for tracking down issues we have had in Office 365. I can understand how frustrating it can be if your competitors seem to have "secret knowledge". However that knowledge may have been gotten by calling up the very helpful people at MS support, laying out the problem and they send you a Powershell script in return.
I couldn't agree more. Why is the API not public? Is it because some sort of top secret corporate conspiracy? Or is it that management just decided to avoid the burden of publishing and maintaining an immature or lesser used API? After reading your comment that whole article seemed a little sensationalist
> just decided to avoid the burden of publishing and maintaining an immature or lesser used API
"Burden" is an understatement. Any API Microsoft documents becomes part of their ongoing commitment to eternal backward-compatibility. (Heck, even some things they never document at all still end up forced into that commitment, like the internal registry hives in Windows 95.)
So Microsoft do everything they can to only document what they're absolutely sure they have in a good, stable, "won't regret later that we didn't fix it some more before setting it in stone" state.
While that may be true for the Win32 APIs, it is certainly not true for their cloud-based products. They’ve had some very poor APIs for Windows Live Mail (predecessor of Office 365 for education) which were also quickly deprecated and replaced.
They could just flag it “volatile”, “unstable” or something.
It’s very unlikely that Microsoft did not properly document the api internally and as you see it’s leaking out anyway.
If you'll ever develop a single simple API you'll find out that doesn't work at all. People will use unstable APIs and people will blame YOU and only you when they break.
There are a lot of reasons that it might not be public, but a conspiracy is quite low on the list.
My guess is that it's due to one of the following:
* The API isn't considered beta yet.
* This was created as somewhat of a side project and hasn't been formalized yet.
* Documenting it is on the backlog.
* It's meant for internal use in that they may be building in tools in the Security and Compliance center that will be calling it.
This is absolutely not true. I called O365 yesterday (well, they called me at my request) to investigate a potential data breach. All the guy on the phone could do was to read to me out of a technicians manual and then suggest I purchase the Azure Active Directory P2 plan at $9/user/month.
I respect that fact that CrowdStrike and others have spent the time with the api and made life a lot easier for others. As someone who has spent more time than he wanted with the Office 365 API I am a fan of people who make my life easier. That being said I am not buying the drama that these API's have been hidden.
I just finished re-reading A Wizard of Earthsea and The Tombs of Atuan last week. It was enjoyable because I picked up some of the themes that teenage me missed when reading the series all those years ago. A gifted writer RIP
As a thought exercise I wonder what would people's advice be if the author was in a same sex relationship and the pair was having disagreements over cleaning and relational priorities. I am guessing most of the advice would be about how to communicate better with your partner. Now that maybe slightly easier with a same sex partner but I think the point is still a valid one. Peal back some of the feminist rhetoric and you have a couple who need to work on their communication skills.
SV has had major problems sheltering people in leadership who have used their positions to sexually exploit their female subordinates. Yet a mid level engineer publicly questions some of the company's diversity policies and gets fired. Many of publicly stated reasons about women leaving tech is predatory behavior by people in leadership. How about initiatives about getting rid of individuals like that.
I don't buy this from VW for a second. I am not sure what the work environment is in Europe but in all the corporate places I have written code for in US if I pulled a stunt like this with no backing from managers the best I could hope for is getting yelled at. Most places would have fired me on the spot. The possibility of this being a rogue engineer is extremely remote. This screams management cover-up.
Sounds like a good way to teach programming :)
I would suggest that it's because you are putting the architecture in place. I work professionally in a code base that is hitting a Norris number and is suffering from little to no architectural direction in the past and some parts are very difficult to work in.
Out of curiosity, have you gotten any press inquires about your launch from major tech publications? I know that your company is outside of the VC funding publicity bubble but I am curious if anyone has reached out?
I have talked to people who are in property management companies who are worried about (possible) rising interest rates are going to do to their profitability. It may not be a concern in SV but elsewhere very much so.
