mattiemass

I've worked in a large organization that had a huge QA group. QA was taken really seriously. At various times, I had both a QA role and a development role.

Then, I moved to an organization where developers were responsible for their own QA. What I found was an incredible difference in the mentality around ownership of quality.

I began to realize that, perhaps obviously, quality was owned by the QA group, almost exclusively. It wasn't uncommon for developers to find a bug, but leave it untouched because QA would file it eventually.

So, while I completely respect QA engineers (I was one!), and think it is a pretty useful mindset to have, I also have observed how negatively it can impact an organizational culture. I'd be interested to hear from others about their experiences.

I am so nervous/excited for this reveal! I can only imagine the butterflies and sleepless nights for the actual team involved. Good luck everyone!

I love that you can still download a 68K version!

I've experienced very similar problems when experimenting with TDD. Really appreciate you sharing!

I'm such a sucker for stats like this. Thanks for doing this!

Love the shared lessons! Good luck with this!

Great, open reflection on the product. Thanks for sharing!

Shame on me for thinking that you needed other languages for good concurrency. This looks awesome!

Very cool article. Amazing how much tooling Netflix has built themselves.

I'm sooo happy to see prominent developers advocating for leaving sanity checks (via precondition) on in released builds! Love the article, but love that recommendation more.

Looks great - well done!

Does not look like my cup of tea, but I'm trying to reserve judgement. Anyone have any experience with this?

Perf for sure, but I was typically more concerned about availability.

Interesting stuff. In all my distributed systems work so far, I've assumed that a distributed lock is a thing to avoid. I really should take another look at them, just as a tool to have at my disposal.

I've always found people skilled with debuggers look like they have super powers. Symbolic debuggers really are tricky, and these are some good tips.

It's taken me perhaps longer that t should have to get here, but boy oh boy do I think this is spot on.

Holy moly. I've been through an acquisition, and it was the complete opposite experience. But, I have a bad feeling this post is completely right and this is typical. Must really feel terrible. I'm glad this person shared, and I hope they don't get into any kind of trouble over it.

I was hoping for an insider leak...

I'm always facinated by things just like this. Does anyone know of something similar for software development personality types?

Wow, looks incredibly powerful if you're willing to put in the time to learn. I wish I wasn't so lazy.

I definitely go through times where I struggle with the team dynamics, product direction, management. Perhaps all fields have similar analogs. But I'm not sure I'd be able to stay away from programming. It's been a lifelong pursuit and I have just as much fun now as I ever did. I am definitely happy, and I think I would be quite unhappy were I to stop.

Agreed.

I took it as good news more for the Facebook investor. The piece didn't convince me of that, but I think that's what it was going for.

Thank you for posting these

Love stuff like this. There's so much momentum around TLS lately, so great to see.

I admitted it was irrational! Twice!

Interesting ideas, and they do feel intuitively correct. Sone evidence would make it more compelling.

It's unfair of me, but I'm always turned off when I see a desktop app that works on multiple platforms. That irrationally soured my first impression, because I think it otherwise looks like a great tool.

Welp, stupidly I dropped the www with zero research because I saw others do it. Love the explanation of why keeping the www is useful.

Love the idea of trying to a) make 20% time better and b) encourage it to be open source. Wonderful stuff!

now that is an answer