Talk:Software architect

message: Completely rewrote the software architect article.  Removed the stub indicator.   normxxx 19:27, 29 December 2005 (UTC)
thread_title:  untitled 

message: The article is too dry and coupled to a particular style of developing software.  I propose removing all aspects that talk of document deliverables and specific workflows, and instead focus on the communication aspects, as well as attempting to define the core of the role (what does a software architect do for the business).  216.17.5.44 13:13, 5 September 2007 (UTC)
thread_title:  Proposed new rewrite 

message: Hello: I wonder if the author of the latest edit would be kind enough to comment on his or her reasons for undoing my re-writing? I do not believe I have made any material alterations to the article; I merely have been trying to improve the writing. Thanks! --Wspencer11 (talk to me...) 02:47, 10 November 2008 (UTC)
replies: text: I think it was an accident, and took the liberty of reverting.  That editor attempted to add an external link, and I think started from a previous version of the article (he's a new editor).  If it's a good link go ahead and re-add it.  Antandrus  (talk) 03:08, 10 November 2008 (UTC)
thread_title:  Latest edit 

message: Yes citation is needed for such generalisation.  In my experience it just differs from organisation to organisation.  The organisation I currently work for the opposite is true.  Application architects are almost always not active software developers.  — Preceding unsigned comment added by Hseldon1234 (talk • contribs) 14:59, 26 March 2012 (UTC)
thread_title:   The application architect is almost always an active software developer? 

message: Discussion at Talk:Enterprise_architect#Architect --Ronz (talk) 18:42, 5 July 2012 (UTC)
thread_title: Legal ramifications of using the title of architect

message: "Software architect is a computer programmer who makes high-level design choices and dictates technical standards, including software coding standards, tools, and platforms."
Gabriel K.: 
First you don't dictate, you "strongly" suggest, otherwise you limit the innovation in your team. You need feedbacks and tips!
My description of a software architect correspond to what you have in a startup.
In my junior years, I was a dictator, but it doesn't work. Then I've learned the job.
- Visionary: You need to have  a vision of the product. What you do now, and what you expect to do in the future. How can you reach this target.
- Strong in IT: You need to be strong in development, strong in system infrastructure (what we call a DevOp).
- Strong in process and coaching: Then your goal is to help your team to reach his goal. You need to understand how you can help you team to perform better (the description of a scrum master is quite good). You perhaps need to create new process, or remove some process! How can you help your team to perform better? Do things make sense?
- Strong in Business: You need to understand and sell your architecture to your people, and to the CEO / management / sales. You need to understand what is the role of everyone and how the architecture help them to reach their goal.
An architect is a communicator in a team. You are part of the top management, but part of the "workers".  — Preceding unsigned comment added by 128.179.67.173 (talk) 14:58, 4 October 2013 (UTC)
replies: text: This is pretty hopeless. I put a lil lipstick on the pig. Hope that helps :) 98.4.124.117 (talk) 02:49, 17 July 2018 (UTC)
replies: text: I've started my draft of this article with the first 3 §§ redacted. Will have comments enabled there in a while. I don't generally contend content in public venues. 98.4.124.117 (talk) 16:08, 22 July 2018 (UTC)
thread_title:  Please moderate the description of an architect :) 

message: This page had no citations and a dispute about whether information was factual. The page at the time was very short and did contain opinions. A software architect is someone who does software architecture. That page is of much higher quality, so rather than spend any time duplicating information, I think its best to direct readers there.
Hodl-baggins (talk) 04:58, 29 June 2022 (UTC)
thread_title:  Duplicate of Software Architecture