Search results
"tag:"role""
| Title and summary | Date/time | |
|---|---|---|
|
21
|
Technology selection
Technology selection is generally seen as one of the most fun parts of the software architect role because you get to sit down, download something new and learn how it works. And it is fun, but my view of it has changed over the last couple of years. ... |
04-Dec-2007 19:51:48 |
|
22
|
Once an architect, always an architect?
I'm currently on holiday. It's not much of a holiday admittedly, as it's doing development work. I thought I'd try "going back" to development for a bit as the project sounded interesting and it would give me a chance to experience being downstream of ... |
29-Nov-2007 14:34:15 |
|
23
|
Why do so many technology projects fail?
The Financial Times published an interesting article earlier in the week entitled Perspectives: Why do so many technology projects fail? (registration required) detailing a court action between BSkyB and EDS. In summary, it's about the failure to ... |
23-Nov-2007 14:48:00 |
|
24
|
London User Group - December 2007
Here are the details of the December Coding the Architecture London User Group. Title : From Developer to Architect Summary : The transition from software developer to software architect is often shrouded in mystique and few people talk about it. But ... |
20-Nov-2007 17:02:29 |
|
25
|
Where's the coffee machine?
I have recently moved into a technical architect role at a new client. Over the last month or so, I have asked lots of questions. Here are some that I found particularly useful... Who is that? - I always ask for a new client's organisation chart, or ... |
16-Nov-2007 08:36:00 |
|
26
|
Technical Architects in Investment Banking
I had an interesting conversation with a recruiter the other day who claimed the job title of "Technical Architect" was nearly redundant in the City of London's investment banking sector. Instead of looking for technical architects, he claimed that city ... |
14-Nov-2007 09:55:06 |
|
27
|
Performance tuning Java systems
One of my current projects involves me performance testing a third party Java system. In essence, it's a distributed/n-tier Java EE web application and we're hitting it with a high simulated load thanks to Apache JMeter. One of the things we found is ... |
05-Nov-2007 12:23:34 |
|
28
|
Trusted advisers
If you take a look at most organisations, it's fairly obvious that technology is there to support the business - it's there to enable new business, make existing business more efficient, reduce costs and so on. With technology taking on this subservient ... |
22-Aug-2007 09:39:00 |
|
29
|
Architects during the transition phase
If you view the software development cycle from a RUP perspective, the transition phase is all about ensuring operational quality and moving the system into production deployment. Nothing new here, but what's interesting is that most architecture roles ... |
13-Aug-2007 20:45:00 |
|
30
|
Role Profile for Software Architects
The role of the software architect is a frequently discussed topic and changes depending on any number of factors. Even with a large amount of existing material available (e.g. the RUP role definitions, the IASA Skills Library, etc), defining exactly ... |
31-Jul-2007 14:22:44 |
|
31
|
Poor execution
Let me paraphrase an interesting statement I heard last week about a software system. The high-level design is fine, but the execution was poor. I found this interesting and started thinking about it from several perspectives. You can define the ... |
30-Jul-2007 19:23:00 |
|
32
|
Time zones
When I start a new project, I can be sure that there are always a number of common tasks that need to happen. These include defining document templates, the source code structure, a build file, the development environment, the continuous integration ... |
24-Jul-2007 10:52:00 |
|
33
|
Positive energy
As a hands-on architect, you're probably the person that everybody in the development team looks up to the most. The main reason for this? Many of the team are probably aspiring software architects themselves. Although this is a flattering situation to ... |
24-May-2007 08:36:00 |
|
34
|
The great rate debate
Here's an interesting one for those of you working for a consulting/product/p... |
23-May-2007 08:31:00 |
|
35
|
Delegation
I briefly mentioned delegation in my post yesterday about authority and I wanted to expand on this further. I talked about delegation in the context of having the authority to make decisions - you don't actually have to make all of the decisions ... |
22-May-2007 09:14:00 |
|
36
|
Authority
Related to responsibility is authority. Having responsibility for making things happen is one thing but, if you're going to be successful, you must also have the authority to do it. If you're responsible for the overall architecture of a system, you must ... |
21-May-2007 17:13:00 |
|
37
|
Role titles across the world
We all know that the meaning of the "technical architect" role is ambiguous and varies depending on who you talk to, but what about the name of the role itself? Here's a list of the role titles I've come across here in the UK, grouped where I ... |
16-May-2007 12:33:00 |
|
38
|
Responsibility
Somebody once told me the following and it's particularly relevant for software architects. Share the successes with your team, take on the failures yourself. From a software architect's perspective, you can't necessarily blame the development team for ... |
16-May-2007 09:49:00 |
|
39
|
You don't have to give up coding
I've already written that architects should get involved with the code and there's a flip side to this where I'm constantly asked whether architects *can* continue to code if they are to climb the corporate career ladder. This is a shame, particularly if ... |
15-May-2007 13:07:00 |
|
40
|
The hand-off
I've spoken to, interviewed and screened a lot of CVs/resumes from senior developers and architects recently and there are a lot of baton hand-offs going on. One of the great things about small or agile teams is that the same people capturing the ... |
14-May-2007 15:04:00 |
