Experienced Devs

3978 readers

1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

snowe@programming.dev

jmk1ng@programming.dev

drewsiferr@programming.dev

151

Senior Devs in huge corps: Do you even code? (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by van2z@programming.dev to c/experienced_devs@programming.dev

45 comments fedilink hide all child comments

I have been working at a large bank for a few years. Although some coding is needed, the bulk majority of time is spent on server config changes, releasing code to production, asking other people for approvals, auth roles, and of course tons of meetings with the end user to find out what they need.

I guess when I was a junior engineer, I would spend more time looking at code, though I used to work for small companies. So it is hard for me to judge if the extra time spent coding, was because of me being a junior or because it was a small company.

The kicker, is when we interview devs, most of the interview is just about coding. Very little of it is about the stuff I listed..

you are viewing a single comment's thread
view the rest of the comments

[–] sbv@sh.itjust.works 10 points 1 year ago

Seniority typically means the scope of your role increases - you interact with other teams more, you spend time on high-level design, etc.

From what you describe, it sounds like you're doing that.

If you miss coding, you can assign yourself a few small bugs/features. That keeps you familiar with the codebase. It's probably a good idea to choose stuff off the critical path, since the meetings are what you're actually paid to do at this point.