this post was submitted on 02 Aug 2023
114 points (98.3% liked)
Asklemmy
43946 readers
606 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Your coding skills are not dead. I have been in dev since the late 90s and find myself managing a few dev teams (some have a manager that "reports" to me, some are herds of cats and I just try to explain their behaviour to others). I regularly find myself in meetings where "why isn't this done yet" is the topic and the developer is stuck on a technical issue. Despite not even being that fluent in a particular language I can often point out things they should do or two that lead to determining the root cause. I'm also often in conversations about optimizing systems.
That sort of thinking is programming. Typing instructions into an editor is probably the least interesting part of the job.
At your level, you can make deep and broad impacts by designing systems that work, are easy to integrate with, run smoothly, etc. You can empower and inspire tons of people.
Yes, meetings can suck and the report I'm currently working on feels like an exercise in futility, but there's so much more to the job.
The level I'm at right now is so abstract that I hardly ever even see the applications themselves or have contact with the developing teams. When I am dealing with an application, it's just an acronym supporting a list of business capabilities. Any effect I could have is extremely intangible.
I'm aware of the fact that this is just like developing software but on a very, very high level. And I thought I would like it, and I hoped it would get better after I acclimatized to the company. But I'm realizing I am uncomfortable with the level of abstraction, and that I hate corporate politics.
Something else - if you've ever had imposter syndrome as a developer, imagine what it's like as an enterprise architect!
Ok, yeah, I wouldn't like that. :) I have a job title that makes it sound like a job like that but the reality is I'm still very operational some days.
I have no advice (but I do have imposter syndrome!). You could try leaving your job for a smaller, stable company (not a start up). Part of me thinks that you should look back on that as a phase of your career you liked and just focus on being happy in other areas of your life and collect that sweet paycheck. :)
Good luck!