8 ms·
A few years back, I had the opportunity to lead the Product Team of a 200+ people company. It took me over a month to understood who does what, and I tend to tr
by Brajeshwar 5y ago
A few years back, I had the opportunity to lead the Product Team of a 200+ people company. It took me over a month to understood who does what, and I tend to try to know things around me and at least have the idea of “what to do in an emergency.”
I stumble on one DevOps guy who wrote every bloody thing happening in the system. He likes doing it, but from the way people were asking questions in the common chatrooms, group emails, I knew nobody read them. He loves plain text, nicely formatted with the old-school Unix-styles et al. I had talks with him outside of work and found him fascinating; I asked him help with my hobby, home-lab tinkerings, etc.
By that time, I had already started internal blog groups and was encouraging people to write. And indeed, a lot of people came out to write about engineering, marketing, product, and it became a routine for people to show off what they can do, what they love, and what they are good at.
In one of my regular company-wide emailers, I dedicated a big piece to the DevOps guy, pointing to his work and the beauty of his documentations. People loved it, and they began reading it. He remained a friend. That mailer was the only way I could highlight people I encounter doing good work, to the whole team up to the CxOs.
By the time I left the company, I was responsible for many vital things in the company, but I could transition everything smoothly with the documents and credential details (thanks to 1Password).
In the last year or so, I have been thinking more about -- always be dying. I think the similar vein of Always be Quitting; I try to document, write out details, just in case I die and my family has to figure out the intricacies.
- gary_0 5y ago> just in case I die and my family has to figure out the intricacies I'm reminded of how so much of what we know about history is because of the diaries and correspondence that happened to survive to the present day. There are surprising gaps in what we know about day-to-day life in the distant past because nobody bothered (or was able) to write it down.
- eru 5y agoTo be slightly flippant: we get even more valuable information out of garbage dumps. People usually bias their writing towards what they consider to be important information. And they leave out what they consider obvious context. So we have a lot more information about battles and kings, then about daily life. People are less biased towards highfalutin in the ways they produce garbage.
- rpmuller 5y agoThis is a very wise observation. The most important things are always the ones we think are so obvious that we don't mention them.
- FridayoLeary 5y agoBattles and kings are not garbage.
- egypturnash 5y agoKings are definitely garbage.
- eru 5y agoI was talking about literal garbage dumps. They are incredibly important for archeology. Battles and kings and things that seem important when they are current, but aren't as interesting in a few hundred years as insight into daily life.
- CRConrad 5y agoNo, but all the ancient historians wrote about battles and kings, so we have that info all written up already. Very few of them wrote about the life of the average peasant, so to find out about that, one of the richest kind of archaeological sources are literal garbage dumps: https://en.wikipedia.org/wiki/Midden https://en.wikipedia.org/wiki/Midden
- eru 5y agoWhenever I hear people complain that our digital media won't leave much for future archaeologists, I always think of our enormous output of plastic, metal and glass garbage.
- dan-robertson 5y agoOther places that tend to provide this sort of information are tax records and wills, both of which tend to be somewhat likely to survive. Even if you can only see tax laws it can tell you a lot about how the society fitted together.
- b0afc375b5 5y agoI'm that guy in my current company. When I get brought in to an existing project, the first thing I look for is the README. To my disappointment, it either doesn't exist at all, it's the default generated, or it's 1 or 2 years outdated. So during project on-boarding, I document everything I can, create or update the README, then commit and push to the repo. In all of my coworkers across all projects, I'm the only one who does this. I'm pretty sure nobody reads them either. I don't mind though, it has paid for itself countless of times already, since I always reference it.
- hpoe 5y agoHonestly it is so frustrating for me when I have a new project that is written by someone on my team and I need to do something to it and so I go to view the repo in Github and everytime without fail there's never a stinking README.md and so I have to go message my coworker on teams and harass them to help me figure out things about the project that 10 minutes of writing some basic documentation could help.
- xaner4 5y agoI want to be that guy that document everything, because I have seen the need for system to be completely documented. however, every time I start to document some system or code the info change or I'm away from it for a small while and the documentation and the system drifts apart.
- Salgat 5y agoExactly. Documentation is expensive and time consuming and needs to be maintained. They're absolutely great to have and can be vital, but it's up to management/leads to prioritize it because, at the end of the day, they decide where the money and man hours go.
- cteiosanu 5y agoThis. Good documentation could easily take much more time than an actual implementation of a feature / system and what is an initial X days/weeks/months of estimation is not swallowed as easily by (some) management when you tell them it should be doubled if quality documentation is desired.
- sul_tasto 5y agoI strongly recommend that everyone with or without dependents look into disability insurance. You are much more likely to survive an injury or illness and be unable to work, than you are to die.
- bradleyjg 5y agoHow reasonably priced is this to buy individually?
- pc86 5y agoThe short answer is "next to nothing" especially for tech salaries. I did a generic search and questionnaire to see what actual quotes were. For a 35 year old non-smoker male in my zip code, with an office job, $84/mo gets $6400/mo in benefits if I become totally disabled. There's a ton of caveats (90 day waiting period, 10 year term benefit, medical exam etc) as with any insurance product. You can get partial disability insurance as well (this is total only).
- bradleyjg 5y agoWhat you really want is insurance that pays out if you cannot work in your given profession (e.g. software engineering) not insurance that only pays out only if you can’t even work as a greeter at Walmart. I’m under the impression that this is very expensive because of adverse selection effects.
- deleted 5y ago[deleted]
- phlipski 5y agoThis is great advice. My father-in-law recently passed and my mother-in-law literally knew nothing about their finances. She's been calling insurance companies and banks trying to make sense of it all. This is more an indictment of their lack of communication over the years, but the principle still stands. My wife asked me to write out on a piece of paper all of our bank, investment and insurance account names, numbers and passwords just in case I died during my last business trip.
- jethro_tell 5y agoGet a password safe and put everything in it. Share the password or use a password manager with sharing. I still probably need a technical executor for some of my encrypted stuff as that's a little more complex.
- devonkim 5y agoI use 1Password for this purpose essentially and I’ve printed out backup codes and put it into an emergency box. One other problem is that the MFA every other site has now with SMS means that in a disaster recovery situation one will need access to the original phone number associated with an account when logging onto for the first time on a new machine. So this means a shared voice / SMS capable account is also necessary in conjunction with e-mail to avoid more complications. I realized with Apple’s system if I lost all my gear on a trip that nobody would be able to login to my Apple account because all my devices would have been lost. Like any backup plan, unless it’s regularly tested it should be presumed to not be working
- StavrosK 5y ago> I had already started internal blog groups and was encouraging people to write. Can you give some advice around that? Was it one blog in general, one per team, per person? What tool did you use for it? What else do you think is notable about it?
- Brajeshwar 5y agoFor the blog part, it was a simple Multi-WordPress Setup. The idea was that anyone could start writing independently or as a collective and can be made private or public. It became rather evident that most people were comfortable writing in groups -- engineering, marketing, future-tech/R&D, etc. Initially, I started writing pretty much weekly, and then the crowd picked up. The notable thing about the system was that people began to know their colleagues better, discover stuff together, and partner up to do interesting experiments. Before that, I started by writing fortnightly newsletters to everyone in the company. It was just what happened in the last two weeks. I was just the messenger. I highlight designers, developers, DevOps, QA people, etc., with snippets of their exciting work. It became an instant hit. I'm not particularly fond of managers/leads who do the talking for what their team or juniors did. So, I had to bring in that culture of every doer doing their talks or bringing them to the forefront. The only way to start that was to write to everyone who did what last week. Now, when I get in that junior developer to talk about what he did, his thinking behind it in the next meeting, people know and are prepared. Also, even if some managers/seniors continue to talk over their junior team, people already know who did the work.
- StavrosK 5y agoThat's excellent advice, thank you!
- runawaybottle 5y ago‘always be dying’ I dig that saying. It’s a sad thing, but a good developer should make themselves obsolete by the end of their run. It’s our form of ethics.