Hacker News new | ask | show | jobs
by ipnon 2108 days ago
I don't get paid to give tech presentations. Preparing for them would affect the work that I am responsible for. So giving tech presentations would ultimately make me look worse at my company. This explains the passiveness at my company.
5 comments

This is my observation across several companies/teams. The options seem to be either sacrifice "real work" time to make a good presentation or make a half-ass presentation and have people criticize the low quality.

Do people here think "no prep" presentations could work? Where it's agreed that nobody will do any prep but simply talk about something they're knowledgeable about? Or share their screen and walk through their current project? Everyone in the audience knows that the presenter wasn't "allowed" to prepare so the expectations are lower, but people still get exposed to other engineers' work.

In medium-large companies, work and promotion are about showing off. Even if you do real work it's more important to be noticed than to do it.

In that light, I don't understand how you and the OP could consider that it's preventing to do real work. Powerpoint is the real work. And it shouldn't be difficult to justify spending 1-2 days on it, with 100 people assisting to the presentation as witnesses, unless your manager really doesn't want you to give presentations (it's showing off your team so it's good for your manager too).

I get it that it's not part of the engineer mindset of course. If I have to give some advice to strong engineers who do good work, that would be to take credit for your work.

That captures a lot of what I was trying to capture. However, the intent was for people to cover work that they are doing (lowering prep time, immediate understanding), tech they are researching (again lower prep time, immediate understanding).

A lot of technical presentations we did are no different than what you would do explaining tech within your team. A few diagrams, and understanding of the core of the tech. Scaling to more than the safety of the team is really where I think people would rather have 3 meetings with 3 different teams to do a knowledge transfer than take the risk of being in front of collecting 5-10 teams worth of engineers.

Looking over the comments, the real gap I expect is the lack of peer management support and encouragement. And expectation that mentoring and teaching peers should be part of the leadership expectations. My view are is the the strongest engineers are the ones that accelerate and multiple the work of themselves and their peers, but there are a lot people who subscribe to the "army of one" 10x engineer philosophy.

It is a part of the "engineer mindset"
This was exactly what it was.

Demo, deep dive/narrative on your work. Demonstrating something cool. It was clear the prep was not expected or needed, and it would be scrappy - just like lightning talks at conferences.

The exposure and sharing of ideas was critical.

We even had times where someone would suggest a topic during the meeting and someone would step up and do a deeper dive into it.

Understanding is all relative. You don't need to be an expert to know more than your peers. You just need to accept that your extra knowledge adds value. And be honest where your limits of understanding are.

That's where you need buy-in from management. One of my past employers had a presentation series like that above, and if you were scheduled next, it _was_ considered work that you were responsible for, and counted towards more or less a half-day.

I haven't been at my current employer long, but from what I've heard about our frequent engineering meetings and their presentations, they do the same thing.

At my team we "ticket" presentation prep just like dev work. So if you wanna do some sort of story point / ticket anlalysis per dev is no different.
Make it 5% of the work time. Make it part of the job (I also doubt you're working 8hrs at full productivity mode)
That attitude is asking to get a "needs improvement" on your APR.