jaynate

I too, have issues from my childhood that have driven self-criticism. Over the past 18 months I have been able to put those things behind me.

For me it was, and is, all about my faith. This article doesn’t acknowledge that aspect of healing, but this has been very real in my life. I’d recommend reading the book Wild at Heart by John Eldridge for anyone curious.

Saw this two weeks ago. Amazing exhibit.

The irony of Trump mandating a no-social-media policy is palpable.

I agree with the sentiment wholeheartedly. MVP has been bastardized in most shops I have been in. What's actually built is a "minimally compliant product." We need a better name for the idea that we are searching for something valuable for customers to buy. How about Market Viable Product which is the anticipated end result of the process of searching for product/market fit?

I get it, definitely frustrating. But we know the world - especially the business world - is not a kind place and that we have to protect ourselves or we end up in these situations.

Several rookie mistakes in here by the Shred team. First of all if you are gong to start a company while working for someone else, get an explicit agreement in writing before starting that venture. Second, there should have been an agreement/contract in place for doing the additional work which was requested by Smule. The claims of theft could still be made by Smule but Shred's story loses credibility for me because these basic business practices weren't followed. Who is to say that the lines weren't blurred when it comes to leveraging the assets of the former company? And if a laptop is obviously the property of Smule then nobody can force you to keep it.

I feel much empathy for the Shred team but the story has a bunch of challenges buried within.

Would highly recommend this book by Joe Sutter the engineering leader for the 747 program: http://www.amazon.com/747-Creating-Worlds-Adventures-Aviatio...

Like the idea, but it feels heavy to me and like it may suit slower release cycles better. Maybe that's because MS is still shipping installed software tools (TFS in this case).

"We’ve done it 3 times now over the past ~7 years and have been happy with the results every time"

This comment confirmed it for me. I'm interested in companies who are using this model in a context where software is released continuously or at least multiple times per year?

This doesn't aound any different from any other company on the planet if you look at it from this angle. The author seems overly entitled and disgruntled. Any job is what you make of it.

Cool solution for folks like us. Best way to diminish password as an attack vector and secure services for the thronged masses is to reduce the number of passwords required to use the Internet. And couple a master (eg My google account) account with a second, biometric factor.

In the world of enterprise software it's also easy to overlook the cost of implementation/setup of features on the services teams and customers. Is helpful to define nonfunctional requirements that deal with these ancillary concerns.

Also all of these issues highlight why product management needs to have a working knowledge of technology and the related costs of various trade offs.

Any developer worth his/her salt understands the value of open source these days. Keep in mind that these engineers don't actually run the business.

This web site is crashing safari on iOS.

Any chance you can elaborate on:

"(i.e. powerful as in ability to do something, not in terms of performance)"

Do you mean smaller units of functionality which perform at good levels? For example, I wouldn't want to deploy a large, monolithic service this way?

Ah, I see. Perhaps you can use Analysis & Design tasks not to estimate the actual work, but further research tasks necessary to get to a more solid answer. Setting the expectation that all issues can be analyze and designed in 6 hours seems arbitrary.

Many times the Analysis and Design of a solution encompasses trying things out and actually experimenting with changes. By the time you're done with Analysis and Design you've virtually implemented the solution. Of course there is the documentation and reviews that you could also estimate separately.

This is a classic human problem - we suck at estimation. And if some pointy haired boss is demanding perfect estimates, you should give him or her good estimates for the next piece of work you can predict rather than the finished task.

Can you clarify what A&D is?

I'm quite sure that gmail's services are also based on open source software and operation systems.

That made me feel a little sick. But very cool.

If you think lock in on SQL server is bad wait til you're locked in on azure.

For years Microsoft-sponsored SQL Server consultancies have been telling us to use the database to its fullest extent. Use Stored Procs and non ANSI SQL features, they're fine! Logic in the database? We love that.

That's what ISVs and Enterprises are being told to do and that's exactly what they've done, at least the ones who couldn't see Microsoft's business angle. Now many are left to choose to either accept Microsoft's ever-increasing licensing costs or a high cost to switch.

I agree with @BrentOzar, time to find other options.

Lock in due to the usage of proprietary features like PL/SQL. Switching costs are too high for existing systems.

Agreed. And across business and personal use. "We will be all things to all people." If I'm a Microsoft employee there is not much here for me to get behind.

He must have used the Dilbert reorg memo generator.

Complete and utter lack of focus is what I read:

"Going forward, our strategy will focus on creating a family of devices and services for individuals and businesses that empower people around the globe at home, at work and on the go, for the activities they value most."

In that case I would say you have architected an app for aws, then, and we should be careful not to do that for portability's sake. Http://www.12factor.net/backing-services

Google backup service seems like a valuable proposition. I assume someone's already implemented that.

"file synchronization is just not a killer application"

...is still true. Solving for the problems of not having having my files when I need them, on any device I'm using and without having to map drives and deal with complex, technical setup IS a killer application.

Customer experience and usability changes everything.

Completely agree with this. They are giving away massive amounts of platform time to seed usage. Better question is when Azure will break even (net, including R&D and internal marketing transfers to the Azure business).

non-production

I wonder if the $1B number doesn't also include internal marketing "funny money" microsoft is using to seed the business. There are companies who have been given large stipends of free services to wet their appetite for the platform.