Tech lead / Architect transitioning to other discipline

[Stuxnet]

I'm a tech lead / architect with over ten years of software development under my belt. I've pretty much had my fill of it for a number of reasons. Most notably, I'm tired of constantly keeping up with the design trend flavor of the month and dealing with codebases that have been enterprised out the ass.

I've thought about trying to transition to a DBA role, BA role, or maybe even a PM role. Just wondering if anyone else here has switched things up in a similar manner for similar reasons. What were your biggest challenges/regrets/oversights/etc.?

 

[Markbnj]

I'm a tech lead / architect with over ten years of software development under my belt. I've pretty much had my fill of it for a number of reasons. Most notably, I'm tired of constantly keeping up with the design trend flavor of the month and dealing with codebases that have been enterprised out the ass.

I've thought about trying to transition to a DBA role, BA role, or maybe even a PM role. Just wondering if anyone else here has switched things up in a similar manner for similar reasons. What were your biggest challenges/regrets/oversights/etc.?

Well, I have to do some PM stuff in my current job and I hate it. I guess if you like being the small insect crushed between two large animals then it might be fun.

 

[KIAman]

You're sick of being a Tech lead because you have to keep up with cutting edge tech? I'm curious, can you give examples of "design trend flavor of the month?"

I would consider stepping into DBA or BA role a huge step down compared to a Tech Lead/Architect, unless the job role is different from what I know of.

 

[LokutusofBorg]

I'm somewhat in your position. 10+ years, lead/architect the last couple. Got laid off from my last job as Development Manager due in part to what Mark alluded to... Although I don't share your dislike for keeping up with design trends and latest technology. In fact, that's what I thrive on.

What I am sick of is all the horribly written software out there. I put a few years into a job reworking the system while keeping up with requests and finally get the system to a good place, and end up moving somewhere else where I just have to start over. I am *so* tired of this. I am *so* tired of all this poorly written software that I have to work on. That has prompted thoughts in my mind lately of what sort of career change might actually be viable for me. I haven't come up with anything that sounds better than DBA, and I don't think that would work for me long-term. I have turned down the chance to move into management multiple times over the years (my last job I mentioned as Dev Manager wasn't really a manager role, more like lead/architect).

I've sort of landed on the idea that my only path out of the doldrums of constantly churning other peoples' badly written code is to just take the plunge on a start-up idea and write something of my own and see if it makes money. I've gotten so burned out on my day job the last few years, though, that I have no motivation to try to work on stuff at night. 🙁 Vicious cycle.

 

[Stuxnet]

You're sick of being a Tech lead because you have to keep up with cutting edge tech?

That's not what I said.

I'm curious, can you give examples of "design trend flavor of the month?"

No offense (seriously), but the meat/purpose of my OP wasn't to dissect and debate the undercurrent of the boredom and tedium I feel in my role as an Architect/TL, but rather what challenges/obstacles needed to be overcome by those who walked this path before me. Otherwise, I already get to debate the virtues of implementing 20 interfaces and 5 abstract classes for every one concrete class as well as designing 500k-line flow/content engines to replace Web Forms and ASP MVC ad nauseum. Honestly, I'm already nodding off just thinking about it.

I would consider stepping into DBA or BA role a huge step down compared to a Tech Lead/Architect

My goal is a change of pace that is still within the realm of technology and where I can leverage my skills and experience without being confined to a code editor for the majority of my day. That's the primary parameter/consideration.

Given that, I'm actually most interested in a role as a PM: In most medium to large shops the PM is the kingpin of the project and is responsible for coordinating a solution with a BA, an architect, one or more TL's, and one or more DBA's. They're also generally paid as handsomely as an architect. But at this point in my life, while the money is nice, I can sustain a comfortable living on the salary of any of the roles I specified.

The reason *I* am interested in a transition to that role is because there have been times when I've had to act as a pseudo PM (on smaller projects that didn't warrant a full blown PM resource) and coordinate compromise among the other members in the group above as well as with the client(s). An architect is exposed to personal relationships far more than traditional programmers are, but I still would prefer it to be a primary focus of my job rather than being limited to occasional interactions with other strictly technical people.

I'm interested in a role as a BA for similar reasons, though the role does carry less pay and responsibility than a PM. But again, it's the increased human interaction that I'm after.

The inclusion of the DBA role was an afterthought and is probably at the bottom of my list. If all other doors were closed, I'd probably consider it, if for no other reason than to venture into something new.

 

[EagleKeeper]

PM will require playing politics. Taking flak from your people when you have to play the game because you are unable to deliver. Responsible for schedule that is dependant on variables out of your control.

 

[LokutusofBorg]

The best PMs or Product Managers/Owners that I've worked with over the years were ones with a technical background.

 

[Fallen Kell]

You're sick of being a Tech lead because you have to keep up with cutting edge tech? I'm curious, can you give examples of "design trend flavor of the month?"

Well, lets see:

object oriented
agent oriented
flow-based
data-driven
event-driven
aspect oriented
role oriented
agile
waterfall
RAD
RUP
LEAN
XP
Scrum
TDD

...... I could go on.

 

[KB]

Well, lets see:

object oriented
agent oriented
flow-based
data-driven
event-driven
aspect oriented
role oriented
agile
waterfall
RAD
RUP
LEAN
XP
Scrum
TDD

...... I could go on.

Yeah and thats just the methodology. As a tech lead you often get involved in decisions to evaluate ORMs (.Net has about 50 of them and new ones coming), workflow, UI controls/technology, SOA (WebServices/WCF). I don't blame you for being bored or tired. I get the same way sometimes. Luckily as a tech lead and lead developer I usually stick with KISS. I have never once looked at a class and said to myself, "oh I wish I had 3 more interfaces on it", that would solve my problem.

 

[KIAman]

Well, lets see:

object oriented
agent oriented
flow-based
data-driven
event-driven
aspect oriented
role oriented
agile
waterfall
RAD
RUP
LEAN
XP
Scrum
TDD

...... I could go on.

The above listed methodologies are cutting edge new? Please tell me you're not serious.

 

[sourceninja]

Well, lets see:

object oriented - 1960's
flow-based - 1970's
event-driven - late 1970's
agile - Late 1970's
waterfall - 1970ish
RAD - 1991
Scrum - 1986


...... I could go on.

Seems like many of these concepts are not new or 'cutting edge' Here's just a few off the top of my head. If your company is switching design methodologies every project so they can stay trendy, you have far bigger problems.

 

[robphelan]

i think the point of that list was that at one point, each of these was cutting edge.

i think a developer is a "young" man's game. you are constantly on the look out for the latest and greatest technology.

Management principles don't change that fast.

 

[KIAman]

i think the point of that list was that at one point, each of these was cutting edge.

i think a developer is a "young" man's game. you are constantly on the look out for the latest and greatest technology.

Management principles don't change that fast.

The OP said "design flavor of the month" not "historical cutting edge software design methodologies."

And I object to your "young" man's analogy. Change or rapid change has nothing to do with your age.

And I agree with Sourceninja. If the projects are changing design methods month-to-month, there is a bigger problem. This should NOT be happening.

 

[LokutusofBorg]

And I agree with Sourceninja. If the projects are changing design methods month-to-month, there is a bigger problem. This should NOT be happening.

Few companies are ideally run. Companies with Dilbert-esque problems are another thing I've grown extremely tired of over the last decade.

Being a lead with my feet on the ground, putting the time and energy into keeping up with the latest flavors-of-the-month, regardless of what they are (design, methodology, whatever) only to have a CxO come back from some stupid round-table luncheon and implement some buzzword fad he just heard about at the expense or disregard of months of my work is maddening to the point of looking for another career.

 

[Stuxnet]

The OP said "design flavor of the month" not "historical cutting edge software design methodologies."

The OP also focused his post on a particular problem, not on debating the merits of this, that, or the other.

Besides, I don't care how narrow or wide you make the parameters - it happens at most shops across every facet of design and development: methodologies, language platform, tooling, etc. A new guy comes in at the top (Director, CIO, CTO, VP, etc), wants to make a splash, and BAM!, everyone's switching gears for the nth time and playing catch-up so they're not left behind. Oh, and the actual code be damned.

If the projects are changing design methods month-to-month, there is a bigger problem. This should NOT be happening.

You're being idealistic: it does happen, and it happens a lot. We can whine about there being "bigger problems" all we want, but the effects are there, nonetheless.

This has little to do with "having to keep up with cutting edge tech." There's a heck of a lot more involved in my position than just embracing Microsoft's latest Enterprise Library or someone's home brew take on Waterfall/TD/XP/xyz methodology.

Few companies are ideally run. Companies with Dilbert-esque problems are another thing I've grown extremely tired of over the last decade.

This man speaks the truth.

Being a lead with my feet on the ground, putting the time and energy into keeping up with the latest flavors-of-the-month, regardless of what they are (design, methodology, whatever) only to have a CxO come back from some stupid round-table luncheon and implement some buzzword fad he just heard about at the expense or disregard of months of my work is maddening to the point of looking for another career.

I swear on my grave that I hadn't yet read this when I wrote my response to KIAMan 😎. Needless to say, I agree and I sympathize wholeheartedly.

 

[LokutusofBorg]

Your version of it is very succinct as well. 😉

My last job I was the lead for three years, put in 60 hour weeks more often than not in an attempt to do the things in the code that business pressures would not allow. At the beginning of this year we got a new CTO (my immediate boss, the third in my three years, the company's 7th in ~10 years) and he threw everything to the wind. He was there to make a splash, as you say. It was a stepping stone for him on his way to the top. He brought in two of his buddies ("senior" developers that operated on par with our mid-level guys) and paid them $1000 a day. (Yes, $1000 a day. We weren't supposed to know that, but we found out.) After a few too many times of me not kissing his ass, he laid me and one other dev off. The IT manager and the QA manager quit shortly thereafter.

Luckily I got some severance and found some contract work when the severance ran out. Finding a new job in this economy, at this point in my career, is not easy. How many places want another chef in the kitchen? Most places are hiring mid-levels or juniors. Contract work sucks, but at least it's paying the bills.

 

[BadRobot]

Honestly it just sounds like your tired of your current job responsibilities. It doesn't matter what field your in, new people come in at the top and want to change everything pretty regularly. Every position you mentioned is affected by this phenomenon with DBA possibly the least.

Constant change will follow you everywhere. The important thing is finding a set of job responsibilities you enjoy doing.

 

[LokutusofBorg]

True enough.

 

[Markbnj]

I don't mind evolution and change. I do mind having silver-bullet methodologies shoved down my throat by people who don't do what I do, and don't understand what I do. Suits are always trying to "fix" my profession, when the problem with my profession is that they treat code as something you get from the output end of a production process, and they ask us to build them machines that have never existed before based on a few pencil sketches on a crumpled napkin, without any willingness to accept the risk that building a new thing entails.

 

[JasonCoder]

Your version of it is very succinct as well. 😉
Contract work sucks, but at least it's paying the bills.

Just a thought, but maybe stick with the contract work for awhile. I'm betting it might not suck as much as the old situation... here are some pluses:

1) Don't have to support bad decisions. They don't like your idea and go with a bonehead idea? Cool by you, you won't be supporting it... you'll be on to the next contract.

2) 40 hour paycheck. They need someone to support the above bonehead mickey mouse decision, fine, you get paid for every hour you are there. I'm betting at your last job the man expected you to work whatever hours for that salary.

3) Less responsibility. Keep producing quality code and stand by your designs... this is more about how you won't be awakened at 4am because of a production issue as a contractor. See #1 above.


I was a contract consultant for over 9 years. You bet your ass there are downsides but it sounds like the upside may be just what you're looking for.

 

[BadRobot]

I don't mind evolution and change. I do mind having silver-bullet methodologies shoved down my throat by people who don't do what I do, and don't understand what I do. Suits are always trying to "fix" my profession, when the problem with my profession is that they treat code as something you get from the output end of a production process, and they ask us to build them machines that have never existed before based on a few pencil sketches on a crumpled napkin, without any willingness to accept the risk that building a new thing entails.

I'll try to answer this without assuming too much.

Generally speaking:

Executive - Do things and make decisions that affect long term outcomes. Manage the people below you.
VP/Director/etc - Do things and make decisions that affect short to long term outcomes. Manage the people below you.
Managers - Do things and make decisions that affect short term outcomes. Manage the people below you.
Workers - Do what your told. Sometimes you have management that value your opinion. Sometimes your opinion is worth hearing.

In the corporate world many decisions are made because someone came up with a cool new spread sheet total somewhere and gave a good presentation to their boss.

Although after re-reading your post it sounds like you work for a smaller company. Most small companies have the problem you described.

 

[Markbnj]

Although after re-reading your post it sounds like you work for a smaller company. Most small companies have the problem you described.

Actually quite the opposite. I do work for a small company, but our management has none of those problems. We focus on certain kinds of projects for large companies, and have built a strong niche over the years. Our management are all developers and former developers, so the attitude is a lot different than what you find in a larger corp. environment.

 

[KIAman]

You're being idealistic: it does happen, and it happens a lot. We can whine about there being "bigger problems" all we want, but the effects are there, nonetheless.

You have my sympathies, don't get me wrong. I am in a position where I research and tailor design methodologies to our environment. I believe you are exaggerating when you say month-to-month changes to design methods happens a lot, and you call me idealistic for noting that?

Maybe I've been working under heavily regulated environment too long but from my experience, changing ANYTHING about the development environment comes at a HUGE cost in documentation, QA and most importantly, validation.

I have observed some very dilbert-ish scenarios from everywhere and I agree, it is irritating. But to have it affect me to the point of a career change must be more than mere irritation.

Trust me, you are considering a career change to some of your examples listed in your OP but you will find your same annoyances in ALL of those fields, hell from what little description you gave, you will find the same pattern to almost any white collar job. This situation is not isolated to a Tech lead/Architect position.

One of my good friends changed his career from software development to cabinet maker because of his grievances with the industry. After 6 years of cabinet making, he wants back into software development and cannot find a job because he is a dinosaur. The reason he wants back because even with cabinet making, he found the same bullshit he ran away from in the first place.

(Yes, $1000 a day. We weren't supposed to know that, but we found out.)

That sounds about right for an experienced software consultant/contractor.

 

[LokutusofBorg]

That sounds about right for an experienced software consultant/contractor.

It seems extremely expensive to me, even for somebody who kicks ass and takes names. These two individuals definitely did not. They were buddy-buddy, and nothing else.

 

[Stuxnet]

You have my sympathies, don't get me wrong. I am in a position where I research and tailor design methodologies to our environment. I believe you are exaggerating when you say month-to-month changes to design methods happens a lot, and you call me idealistic for noting that?

I said "flavor of the month," and perhaps you're taking it a bit too literally. Sure, there are months that are uneventful, and then there are months when we're doing a total tech refresh for no reason other than someone way too high up got bored. I've held an architect position at 3 companies, and 2 of them fit the bill I'm describing and I have numerous acquaintances who report the same, to say nothing of others in this thread who go through it, too. It happens, and it happens too much. Sometimes us tech guys just want to live our lives a bit without feeling like there are three or four books we should be consuming.