Spending 3 months investigating a 7-year old bug and fixing it in 1 line of code

Re:Spending 3 months investigating a 7-year old bug and fixi... by dehugger on Friday June 21, 2024 @07:30PM (#40754926)

My view as a burgeoning senior dev is that the "senior" bit is generally less about coding and more about domain knowledge.

Understanding the business processes of your industry, how to solicit feedback from and interact with end users, how to explain things to management/sell on ideas.

If you put a junior dev in front of a panel of executives and ask them to explain requirements for a project odds are quite high they will info dump tech mumbo-jumbo. A senior should be able to explain risks, benefits, timelines, and impacted areas of the business in a manner that non technical people can easily grok.

[ Parent | on HN ]

Re:Spending 3 months investigating a 7-year old bug and fixi... by vsuperpower2020 on Friday June 21, 2024 @08:37PM (#40755234)

For me, "senior" just counts the amount of time they've been doing something. If someone isn't very good at something after putting ten thousand hours into it, they just might work at microsoft.

[ Parent | on HN ]

Re:Spending 3 months investigating a 7-year old bug and fixi... by truncate on Friday June 21, 2024 @09:20PM (#40755408)

>> they will info dump tech mumbo-jumbo

I'm mid-level engineer. Honestly, several staff+ engineers may not be spitting tech mumbo-jumbo, but they do dump all other kind of BS. Political BS, "tactical tornados"[1]. May not necessarily mean they were good at engineering, but just good with people skills. Obviously, not everyone is like that, but I would say many are.

[1] https://news.ycombinator.com/item?id=33394287#:~:text=The%20....

[ Parent | on HN ]

Re:Spending 3 months investigating a 7-year old bug and fixi... by skydhash on Saturday June 22, 2024 @09:02AM (#40758848)

If it will be BS, it should be understandable BS.

[ Parent | on HN ]