|
Jacquers wrote: My app checks the file size and last modified date and uses this to detect renamed files.
That would work fine for files above a certain size, where there's a bit of leeway in the file size, but I'd guess that it could cause errors if used for a lot of small text files, where files with the same number of bytes being saved at the same time isn't so rare.
E.g. the source files for a code project.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Valid point  It was initially meant for large video files. For smaller files I can implement something like a md5 hash check.
|
|
|
|
|
I've used FreeFileSync very successfully but be careful if you use the installer, it's crapped on my browser in the past.
|
|
|
|
|
...and I don't (necessarily) mean you have the title of Software Architect.
I believe many people are Architects -- because of what they do -- but do not have the title.
Also, (unfortunately) many people have the title, but aren't actually Architects.
Big Question
So, if you are an Architect, what is it that you believe you do that a software developer doesn't do?
CodeProject : Developer Heavy, Architect Light?
I'm asking that as a question, not trying to rile anyone up. I notice a lot of codeslingers around here, but curious if CodeProject also attracts Software Architects. What do you think?
Interesting Question
What value do you think a Software Architect really brings?
What skills do you expect from an Arthitect?
Can the value a Software Architect adds be put into words / definitively measured?
Just curious about your thoughts.
|
|
|
|
|
I suspect that a Software Architect designes applications which bend in a high wind instead of breaking... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
TBH you're on the right track. Anyone who is really a software architect will be designing the system, but more often than not they will not be full on coding.
veni bibi saltavi
|
|
|
|
|
That's a very Zen answer. Bend, Grasshopper. Do not break.
|
|
|
|
|
Nailed it in one, Griff. I understand the sentiment regarding codeslingers, but the write-ups I like here are the ones where someone explains why you would or wouldn't use a capability. Sure, we'd all like to have a triple-redundant quantum cloud cluster to perform sorts before they are requested, but here on Earth, maybe a call to sort() is good enough...
I would extend the argument that a "pure" coder (software developer) implements what the customer wants, but a "Software Architect" designs and implements what a customer needs. (And "customer" in this case is anyone who wants the software...even the coder his/her self.)
In reality, neither group is "pure"--a beautiful set of code, even to precise customer specs, is a failure if it doesn't get the real job done. And a perfect design doesn't mean crap if no one will use it.
vuolsi così colà dove si puote
ciò che si vuole, e più non dimandare
--The answer to Minos and any question of "Why are we doing this way?"
|
|
|
|
|
Well interesting Question, i personally can't differ the both but by architects do the design on an abstract basis to get a view of the whole system, sw-devolepers mostly focus on the single modules.
But as far as i got into that, by designing, programming, developing my very own project management application for my company i think i did everything on both sides.
That means i made graphs of how modules work together, how single modules are set up and what they can do, programmed it, reworked it, tested it.
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
HobbyProggy wrote: That means i made graphs of how modules work together...
I believe what you are really saying here is that you communicated how the system would work at an abstract level -- and then you developed the specific pieces to build the actual system.
This is the interesting thing about an SA that really should come out: The SA must be able to communicate what s/he is going to do, how s/he going to do it and why s/he is going to do it so every role within the company understands at the time. Then the SA must be able to write the code that does what s/he said it would do.
|
|
|
|
|
Exactly
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
I do it all from end-to-end.
My title is Systems Architect, but that's because when I was hired I was put in a group of actual Systems Architects -- who architect the network, storage, and computing infrastructure for the enterprise.
|
|
|
|
|
PIEBALDconsult wrote: hired I was put in a group of actual Systems Architects
I've seen that happen numerous times also.
And I also understand that since you honestly do it all end-to-end that you really are a true Architect.
It's an interesting thing to attempt to measure and explain.
|
|
|
|
|
PIEBALDconsult wrote:
I do it all from end-to-end. |
Yes, this is my 2nd reply to this.
As this conversation has moved along I see that what companies really want is "someone who can do it all". That has been my experience in the industry too. They attempt to assign roles but then you basically have to know everything -- fortunately I do. 
|
|
|
|
|
Architects design systems that they think just takes bricklayers (programmers) to build, whereas, in fact the programmers need to be structural engineers to build safe and robust systems from the architect's plans, as architects have little knowledge of how things actually work in the real world.
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
Chris Quinn wrote: Architects design systems that they think just takes bricklayers (programmers) to build, whereas, in fact the programmers need to be structural engineers to build safe and robust systems from the architect's plans, as architects have little knowledge of how things actually work in the real world.
I am hearing the subtle humor in this as I've experienced that exact same thing.
So much truth in that and that is the discussion I'm really talking about.
Great input. Thanks.
|
|
|
|
|
I disagree. Software architects need to be able to understand systems and how they work as a cohesive unit. We might not know the ins and outs of a particular subsystem, but we know the importance of that subsystem to the system as a whole. We then do our tricks with crystal balls and mirrors to display the system to non-software types (the ones with money) in a format they might understand. Without software architects, we wouldn't have the payroll systems that ensure we get paid. Where we stumble and fall is trying to anticipate the next development that meets the needs of the next government that comes to power. Every so often, we are left with part of a system that is incomplete due to limits on funding midway through the project. It's those incomplete systems that make us look bad.
The difficult may take time, the impossible a little longer.
|
|
|
|
|
Chris Quinn wrote: as architects have little knowledge of how things actually work in the real world.
Some of them.
Chris Quinn wrote: in fact the programmers need to be structural engineers to build safe and robust systems from the architect's plans
That of course is too generic.
- It ignores that doing that in any complex system is a significant challenge and one that cannot be achieved by any one individual.
- It ignores that to do that there are in fact implementation details that must be done which really have nothing to do with architecture unless the architect is going to a very low level. For example avoiding injection attacks.
- It ignores that the knowledge required to do this in a significant enterprise is probably beyond the capability of any single individual. For example locking down a web server and locking down a database server (and apps) are very different.
Chris Quinn wrote: Architects design systems
Architects can have other roles of course. For example insuring that customer requirements do not subvert long term corporate goals and that customer requests can be correctly munged to produce something that is cost effective to implement.
|
|
|
|
|
Simply put, an architect is expected to have both wide and deep knowledge that spans operating systems. An architect should be able to provide effective guidance for hard problems such as software security, scalability and reliability. Architects are also expected to be aware of technical directions being taken by vendors who provide software infrastructure and tools, such as MS, Google, Oracle, etc.
And of course, an architect should be an experienced developer.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: And of course, an architect should be an experienced developer.
I like the definition you provide and especially that you added that last part about the SA (Software Architect) being an experienced dev.
It's so important but we've all experienced someone who has Architect in their title but who is definitely missing the development experience. IT can be quite terrible.
I find the difficulty that many here are having explaining what an Architect does/is interesting bec. then how do you prove Architect abilities to a prospective employer.
Thanks for your great input.
|
|
|
|
|
newton.saber wrote: someone who has Architect in their title but who is definitely missing the development experience.
IMHO, that makes no sense at all.
newton.saber wrote: how do you prove Architect abilities to a prospective employer.
By describing detailed solutions you came up with to non-trivial problems such as security, scalability, integration, reliability, etc. If all you've done is written a lot of code but have never had to address these kinds of issues, you would be considered to be an experienced developer (which is good), but not an architect. At least that's how it works in my company.
You might find this[^] classic interesting.
/ravi
|
|
|
|
|
I agree with you. Someone who is an Arhitect but doesn't really have the development chops to back it up isn't an Architect at all.
Also, I've read that book, 97 Things Every Software Architect Should Know[^]
Not a bad read because it's from so many viewpoints.
|
|
|
|
|
newton.saber wrote: Someone who is an Arhitect but doesn't really have the development chops to back it up isn't an Architect at all.
I agree. Software architecture is highly technical, not just conceptual. Anyone with a CS background can work at the conceptual/design level, but it takes a high degree of technical knowledge to know how to do that in a way that will actually work as needed in the real world. Plus, programmers are not likely to listen to an "architect" who can't speak their language and understand what they are doing. I know I wouldn't.
It's like someone being semiconductor architect without ever having been an electrical engineer, something's fishy about that. A software architect without a programming background is someone I'd consider a glorified project manager, or a misplaced academic.
Part of the problem, I think, is that it's a prestigious title but rarely needed. Any experienced programmer can do basic architecture, it's part of the skill set, and it's all that's needed on most projects. It's really only the large, complex projects that require a specialist to come in and work on the architecture. And that's really how I think of it, architecture is a specialized programming job in the same way that being a DBA is a specialized IT job, someone you bring in when the needs are beyond what the programmers can/should do on their own. But everyone seems to want the title, whether a full-time architect is needed or not.
|
|
|
|
|
You can find the original free .PDF version of the book I mentioned in my previous post here[^].
/ravi
|
|
|
|
|
newton.saber wrote: how do you prove Architect abilities to a prospective employer.
That's easy.. you show them that you already have the title someplace else. The implication is that, since you weren't born with the title, someone, somewhere thought you deserved it and christened you with it. Whoever that was, they trust them.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
