5 ms·
This is great. I particularly liked this observation: > Shipping is a social construct within a company. Concretely, that means that a project is shipped when
by simonw 2y ago
This is great. I particularly liked this observation:
> Shipping is a social construct within a company. Concretely, that means that a project is shipped when the important people at your company believe it is shipped.
A lot of the ideas in here resonated with me a lot. This is the kind of article I wish I'd read before I spent a few years leading an engineering team at a medium-sized tech company!
- NBJack 2y agoThis is the reality. And if you happen to be in an environment with less cooperative folks, get your requirements to ship in writing, agreed upon, and as up front as possible. Hold them to it. Otherwise, it just opens you up for nitpicking, and in some cases goalkeeping, by folks whom end up delaying your shipping.
- didibus 2y agoYa, I think this is a great insight. In today's world, code is not released as a versioned artifact sold on a disc or downloaded. The idea of "shipping" is fuzzy. You might be 100% in production with some change and it could still leave edge case, deficiencies, etc. You can decide to address them now or later. And it's all just perception. You can say it's good enough, we shipped, let's forget about this whole thing and move to another. Or you can keep ironing out the quirks. I've "shipped" things in the past that were turned on to less than 1% of the time, and we left it at that, and moved on to other things. It was considered "shipped". Everyone was worried to increase it to beyond 1%, so we all patted ourselves in the back for the great launch and went to work on other things.
- bigiain 2y agoThere was always something intensely satisfying about walking into some retail store and seeing boxes on the shelf containing CDs with software I'd written. (On the flip side, there was that one time we had to destroy 5,000 CDs because they had a Quicktime Autostart virus on them...)
- OnlyMortal 2y agoHeh. I can relate to seeing your product on a shelf. I recall seeing IBM ViaVoice X on shelves a Circuit City. It was rather an ego trip.
- Aeolun 2y agoSometimes it’s odd to realize there’s people that can say this while simultaneously not being my grandfather. There’s a whole period of computer history I skipped.
- bigiain 2y agoFWIW, I'm 57 soon. Old enough that I could totally be some random HN poster's grandfather...
- levysoft 2y agoI bought it back in 1998 and started using it right away... it truly felt like the future!
- OnlyMortal 2y ago:-) I worked in the first OSX version. I did the AppKit UI being one of the few on the planet who had a NeXT background. It came with a UK language model as the US model didn’t recognise my accent.
- anshulbhide 2y agoIMO most engineers completely forget or don't appreciate the importance of optics, especially when working with non-technical founders or management.
- klabb3 2y agoYes but otoh that might be more of a “I refuse to accept a culture of optics on principle” kinda situation, rather than not understanding it. I liked the post because it’s honest and doesn’t put a value judgment on things, just explains how it works. It’s up to each and everyone to act accordingly, and one of those actions is to not participate in the lunacy that often arises in the higher echelons. Many people are fine keeping their integrity, mostly left alone to code, avoiding social deception games at the expense of not being promoted out of what they fell in love with in the first place. People are just different.
- superhuzza 2y agoRefusing to accept a culture of optics is tantamount to not understanding optics though. The reality is that if you work on any kind of product, optics do matter - the perception of something working is often just as important as it actually working.
- Hasu 2y agoIt can't possibly be "just as important" - in some cases, I will accept "almost as important", but any situation where the optics are "it works" and the reality is "it doesn't work" is eventually going to come crashing down on someone's head. If it doesn't need to work, then it doesn't matter and the optics also don't matter. Of course, it might be more important for your promotion that the optics are correct, no matter what the ground reality is, and the crash could come down on someone else's head instead of yours, but in this scenario someone who is against a culture of optics rather has a point.
- tharkun__ 2y agoDefinitely just as important. If you shipped and nobody important enough knows, then you haven't shipped in the eyes of the most important people. I'm the first person to agree with you that it sucks that optics are important. But they are. You can definitely ship shit with great optics and get a promotion and be far away before that shit hits the fan. But if you ship the greatest thing since sliced bread and nobody notices, then you might as well not have shipped at all.
- deleted 2y ago[deleted]
- neilv 2y agoNote that it can get trickier than it sounds. (Well, I don't know about big tech, but at least for medium and smaller.) You need to figure out who the "important people" are, and somehow make sure that they understand and buy into the product definition, delivery dates, etc. Even if they're 3 levels up from you, and you can't normally interface directly with them, try to find a way to double-check that all the "important people" are on the same page. Organizational dysfunction happens, and you have to succeed despite that possibility.
- scott_w 2y agoSame here. What you highlighted makes a lot of sense to me and it’s something that happens at every company size.
- h1fra 2y agoYes. Unfortunately, it comes with a side effect, you will see leadership use this to kill projects they don't like by not never mentioning them until people think it's a failure.
- jimbokun 2y agoIf you are working on something the people deciding on the size of your paycheck want to kill, time to find a new project or a new company. Why fight a battle you're sure to lose?
- bluGill 2y agoIf only you could figure that out ahead of time. I've been on projects that were killed with no notice anyone could see even in hindsight. I've been on important projects that senior leaders decided to out source my job to China and my boss was forced to let me go. I've seen budgets run dry many times and important projects got killed/cut with no notice (sometimes there are signs that but you think your project is important enough to escape the cuts until it isn't). Sometimes you are doing working everyone tells you is critical the day before they show you out the door. I've also seen people make careers out of taking over projects cut for the above reasons as customers still demand support. I've seen many downturns where my project was important enough to not be cut. I've seen many downturns where my project had massive cuts, but I personally was not the person cut. Most often projects are not killed outright, instead they go through a long down spiral (not always, but typically) and you can make a lot of money being the expert on a product that is making money if you are able to hang on. Someone needs to leave as there isn't the budget to pay everyone, but that someone need not be you. Often these projects pay very nicely for working 9-5 with no pressure to do overtime.
- realaleris149 2y ago> Sometimes you are doing working everyone tells you is critical the day before they show you out the door. I know this may appear so but the signs are there. We only want this to be true so we do not see it. I've been in a similar situation where all we were seeing was high pressure to deliver something. This made it appear that is because the project is important. But the underlying reason was that if we didn't, the project would be dropped. Which they did. A project may be critical but even more so is to be in a certain time frame and budget, otherwise the project doesn't have a reason to exist any more. But until that moment is still very important because, at the very least because there was a lot of investment into it.
- iknownthing 2y agoIn my experience, most things in large companies are social constructs. Good things are good because they were decided to be good, bad things are bad because they were decided to be bad. Very rarely are they driven by actual metrics.
- enugu 2y agoThere is a tendency here to pattern match the advice in this article with frustrating experiences about office politics. But I dont see this as a post about politics. Rather, what I got was that the spec is an incomplete description and there needs to be more inquiry into how the software is going to be used. This can require a little bit of 'going up the stack' to see how business need relates to the software requirement(single enterprise customer with a precise requirement, acquisition of new customer, software for some internal vision of CEO etc). Compare with a startup where one doesn't even have a spec and one is trying to find a product-market fit or when developers take sales calls and find new insights on how the software is actually being used. A completely broken spec is indeed a failure in management process. But, in general, it helps a library developer to think beyond a library spec and see how it is being used.