In no order, and in a list that will be augmented over time, here's some best practices that I've developed for work. This is tech heavy.
YMMV. No animals were harmed in the creation of this list.
YMMV. No animals were harmed in the creation of this list.
- If you are bored doing a thing, go do a different thing.
- Microsoft OneNote is your friend. It should be always open on every computer you use and you should be effortless with its usage.
- Assign a Windows HotKey to OneNote. Windows+7 (lucky number) gets me there on every computer I own.
- Create a diary tab. Every day gets a diary page in that tab, which will have cruddy notes about what you're working on.
- Do NOT curate your diary entires. Write it and walk away. Curation is a suckers game here and you will lose; The idea is just to write something down as you're doing it.
- Create a contacts tab. That's where you list who you know & what they do.
- Create a TODO tab. This contains checkbox lists of parked things that YOU and YOU ALONE are working on. Check the boxes as the jobs get done. It should be effortless to add a TODO.
- My TODO tab has 2 pages, one for personal TODO and one for subjects I need to discuss with my supervisor that do not require immediate attention.
- Create an interview tab for notes during interviews, duh.
- Other tabs for more significant projects that you're working on, pages in those tabs.
- OneNote is designed to be a hot garbage mess of your thoughts. It's ok.
- Tasks that require collaboration or more ceremony should be thoughtfully put into whatever task tracking system you use. We use Azure DevOps. Others do not.
- While trite, "Be the change you wish to see". Seriously. Complaining = volunteering to own a problem.
- Everything is absurd.
- Make a good playlist for getting stuff done. Here is mine.
- Allocate an hour of time a week to go over your backlog of work. Block it on your calendar and don't let anybody schedule over it. This is time for you to go over any personal or group tasks and curate them - is it really active? is the language precise about what needs to be done? We're not writing Tolstoy, but collaborative tasks should be written in a way that all stakeholders can understand them.
- Going from 0 to 1 is hard. Going from 1 to 2 is easy. Better to get something written and iterate towards better than wait until the initial delivery is perfect.
- Do you work out loud and model good behavior for those around you.
- In computer programming, there is no magic. Everything happens deterministically for a reason. That reason can be highly complex, but is not magic.
- Eat your own dog food. Use the tools you create, so you can make them better.
- "Make the space better for me having been there". Every time I edit a file to make a change, I see if there's other work that I can do that would be safe but make the file a little bit better - better comments, more tests, etc. See safe refactoring rules.
- Everybody's time is precious. Remember your "pleases" and "thank you's". Politeness is a sign of a well functioning social order.
No comments:
Post a Comment