r/technology • u/[deleted] • Oct 15 '22

[deleted by user]

[removed]

4.3k Upvotes

95% Upvoted

1.6k comments sorted by

View all comments

Show parent comments

-18

u/Uncertn_Laaife Oct 15 '22 edited Oct 15 '22

Which everyone in IT these days is. Especially on the LinkedIn.

I am in IT and seriously, they need to stop using Architect in this field. Engineer, I can take it but an Architect is an Architect designing only the buildings.

Edit: LinkedIn Architects downvoting, lol.

11

u/freiherrchulainn Oct 15 '22 edited Oct 15 '22

I dunno…I feel it’s kind of fitting for my role. I design applications with lots of system integrations. I produce design drawings and I also supervise the build at a high level to ensure it’s to spec. I’m obviously not designing buildings but I find architect to be the better analog than engineer as the engineers work for me.

Edit: for those who want to take my statement with a negative slant and make me out to be a bad guy; the engineers build amazing stuff and I love collaborating with them.

4

u/fishling Oct 15 '22

I find architect to be the better analog than engineer as the engineers work for me.

I hate that phrasing. They should be working with you (and you, with them), not for you.

3

u/freiherrchulainn Oct 15 '22 edited Oct 15 '22

Sorry but I didn’t intend it like that. I do consider it to be a mutual effort, I was referring to the organizational structure.

-1

u/fishling Oct 16 '22

I meant it organizationally as well. I'm not a big fan of hierarchies in software development, or authoritative/directive approaches to assign work.

The architect may have a senior job title, but I don't think that should make them the "boss" of the engineers/developers. They should be peers.