Sergey Fedorov

spakhm.com · Personal blog · on HN since 2020

Sergey Fedorov writes about engineering careers, getting promoted, interviewing, management, and reading, with some technical benchmarking.

What HN saysCommenters link his promotion and management posts as useful, but one says the advice is mixed with weaker points and lacks stated confidence.
46HN people shared it
10linked it in comments
50stories submitted
976story points
9 months agolast shared
2020people per year2026

Most-shared posts

  1. 1
    How to Get Promoted
    13 people · 23 points · first shared 2020 · discussion on HN
  2. 2
    Surviving Disillusionment
    3 people · 310 points · first shared 2020 · 170 comments on HN
  3. 3
    How to interview engineers (2020)
    3 people · 43 points · first shared 2020 · 59 comments on HN
  4. 4
    How I Read
    3 people · 6 points · first shared 2020 · discussion on HN
  5. 5
    Commit/Bullshit Ratio
    3 people · 2 points · first shared 2024 · 1 comments on HN
  6. 6
    Parallel tracks
    3 people · first shared 2020
  7. 7
    How to send progress updates
    2 people · 142 points · first shared 2024 · 29 comments on HN
  8. 8
    Please Stop Paying Me
    2 people · 14 points · first shared 2021 · discussion on HN
  9. 9
    Thoughts on Claude Code
    2 people · 6 points · first shared 2026 · discussion on HN
  10. 10
    Tech Stack
    2 people · 3 points · first shared 2021 · discussion on HN
  11. 11
    Envy
    2 people · 3 points · first shared 2020 · discussion on HN
  12. 12
    Excerpts from Jony Ive
    2 people · 3 points · first shared 2021 · discussion on HN
  13. 13
    On Ethereum Developer Experience
    2 people · 3 points · first shared 2022 · discussion on HN
  14. 14
    AI Assisted Interviews
    2 people · 2 points · first shared 2026 · 2 comments on HN
  15. 15
    Headline Driven Development
    1 people · 208 points · first shared 2024 · 69 comments on HN

What HN people wrote when they linked it

patkai · 2022-08-30
Yes, by far! The Gervais Principle is brilliant and after reading it a lot falls into place. It also corroborates with Slava's experience https://www.spakhm.com/p/how-to-get-promoted
cavisne · 2021-09-28
This is a great read on the role of managers https://www.spakhm.com/p/parallel-tracks
coffeemug · 2024-11-01
Node/V8 is insanely fast. I never quite realized exactly how fast until I worked on this: https://www.spakhm.com/ts-wolfram-bench. It's mindblowing how fast it is.
hitekker · 2024-04-08
Like others said, the good advice here is mixed in with not-so-good advice and maybe even bad advice. I think if he stated his confidence on each point, I can calibrate my trust better. Otherwise, my impression is the author has not questioned his learnings. For example, his other article, https://www.spakhm.com/bullshit-ratio, basically re-describes "cost/benefit" as "bullshit/commit", which could have worked for him, but seems too specific, if not unrealistic, to apply elsewhere. I would have expected more research or review (from others) prior to posting to a wide audience.
amadeuspagel · 2024-04-01
This is the last essay by the same author. Same tone. I think he's serious about this: https://www.spakhm.com/bullshit-ratio
q-big · 2021-01-07
> That means you have bad middle/upper management. Large tech companies have heard of the Peter Principle and don't promote this way; they have separate technical tracks. Relevant: https://www.spakhm.com/p/parallel-tracks "Why did all major software companies settle on parallel career tracks? To keep engineering managers from developing loyalty to engineers."
nopassrecover · 2020-12-10
This is another similarly interesting read https://www.spakhm.com/p/how-to-get-promoted
zby · 2020-10-28
A more cynical view on the parallel track: https://www.spakhm.com/p/parallel-tracks
cdavid · 2023-07-10
Middle management (above first line manager) in large organizations is hard to do well. I think it is difficult to understand if you have never done it, and it is even difficult to articulate why. I find it much much harder than working as an engineer or Eng Mgr. Fundamentally, I think it is an incentive and systematic issue: what is expected of middle managers, and incentivized, requires almost complete dedication to managing up and laterally. People who spend time w/ their reports are the exceptions because there is close to 0 correlation with getting promoted. Caring about your report either require crazy number of hours, or ignoring what people above you will expect. The latter will ultimately affect their report. Many people in that line of work do the minimum ? Yes, I can believe this. But the odds are stacked against you. I used to joke "as a middle manager, doing above average work requires extraordinary dedication". 1. Lack of agency: once you are above first line management (EM), you actually have much less agency. As an EM, you can tweak processes, and improve things. You only are accountable to your manager, and maybe 2-3 other people. Once you are above that, the number of stakeholders explodes, and any perception of failure will get at you. You can't say no to many useless meetings because you have to be there. If you don't go, and something goes wrong, guess whose teams/projects will be slashed next time. 2. Corollary: spooky action at a distance. Once…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close