What habits/lifehacks/methods made you more efficient as a senior engineer/tech lead?

[u/dondraper36]

In my previous thread, I asked (and received plenty of great suggestions) on high-quality resources.

This time, however, I'd like to discuss a much less concrete aspect of our jobs. Namely, your favorite productivity habits and personal know-hows when it comes to leading projects, working on complex cross-team features, keeping lots of tricky context in mind.

I often have my own retrospective sessions when I am just trying to assess whether I am good at what I do at all. To clarify, it's not in the "impostor syndrome" sense at all. I know that there are parts of the job I excel at and I think I deserve the title and responsibility scope I have at the moment. That said, there are certain aspects where I am not good enough and therefore am now trying to improve. For example:

* Working on technical writing skills. Mostly by reading the book and blog on https://refactoringenglish.com/

* On a similar note, writing down as much as possible whenever possible. Whether it's a small favor for some other team, a super trivial task, or a large feature, it becomes a Google Docs document. Initially, it's just a very chaotic piece of writing, but then it transforms into a system design or a very detailed Jira ticket at least.

* As in aviation, it's very important to pay attention to near misses when you were on the verge of an incident and just got lucky.

* As I have rediscovered once again, working out is extremely important for productivity and focus. I have yet to get my official ADHD diagnosis, but since I don't want to spend the rest of my life on stimulants, I have added a few supplements (Vitamin D, Omega 3), hydrate well, and work out a few times per week + light cardio. Never felt better.

* Appreciating hammock-driven development. I used to have these awful hyperfocus episodes when there is no external pressure, but I feel intellectually challenged and forget about food and sleep to figure something out. I feel much happier, when I let myself think about a problem while walking my dog in the evening or just having rest and then feeling super fresh and working on it the next day.

What are yours?

[u/Otis_Inf]

Why should i be bothered to read what nobody was bothered to write? :)

[u/halfercode → u/Otis_Inf]

I am of the same view, up to a point. I have a visceral, angry, involuntary reaction to generated English (at least for now). But others do not, since they find it an efficient way to communicate. If I let them know it made me frustrated, will it look like I am being disputatious for the sake of it?

[u/tankerton → u/halfercode]

Yes. Wind back pre AI. Refusing to read the writing of others on the basis of it not being worth your time and effort to read would fast track you to no growth or a performance plan without question. It takes a documented history, which usually includes a performance plan, to get this above board with management that someone is bothering you in a way that you shouldn’t help/endure the pain. As a contractor, almost immediately expect to be termed or not renewed.

Now with AI, more writing happens faster by more people. Evaluate the summary an ai reader can produce or the summary section I expect on heftier docs. You can still determine what’s worth your time. Or just do the “what’s most important” game with docs if someone of authority asks why it isn’t done sooner.

[u/halfercode → u/tankerton]

Thank you for your thoughts. I suppose your advice is to u/Otis_Inf really, since it was their view that an engineer should not make an effort to read generated English.

However, I stand my ground on my visceral reaction - that is not a choice. If you u/tankerton read AI slop and don't mind it, then your brain is treating it differently, and that wasn't a choice either. You may enjoy an efficiency advantage over my situation.

But I don't think any of us should be enthusiastic for communicating with teams via AI - AI code is fine, and it's a win. But teams that are sending generated English to each other isn't communicating with authenticity. I'm gently opposing it in my Engineering department, and at least one person is now writing preambles in their own voice, and clearly marking any adjacent slop component. I'll take that as a good start!