3 ms·
>>So yes, it's not really the architect's fault. And I actually think architects, with the right skill set and organizational support, can be fantastic. Sorry,
by kamaal 14y ago
>>So yes, it's not really the architect's fault. And I actually think architects, with the right skill set and organizational support, can be fantastic.
Sorry, this looks like the same line of talk used to defend MBA's. And 'Architect' titled are basically MBA equivalents of the programming world. They want to manage things they can't do or understand too well in deep.
If you can't write code, you basically can't design large software that requires tons of code to be written. Architecture isn't merely black boxes represented as classes interacting with each other.
If you are an architect you should be able to write code which you can use to do prototypes, or demonstrate a proof of concept, or verify what somebody else is trying to show you, or you would like to show them. You should be able to point out bottle necks, pain points in large software code bases and correct them. You should know how to refactor and all other best practices in software world.
UML/Black box diagram only architects, aren't architects.
- codeonfire 14y agoThe architects and MBAs will counter by blathering something about siloing, antisocialism, poor communication skills, and anything else that will attempt to disparage and marginalize people who strive to understand things at all levels including the very deepest. Some people are insane about this. I've heard some messed up things like academic advisors telling me to avoid computer science professors because they are 'hard to talk to.' Asimov's "my ignorance is just as good as your knowledge" anti-intellectualism is really horrifying to behold and will be used against people who strive to know the high level and the bare metal. There is really no defense against this career-wise either except to get out in the open market where it's just you and your knowledge against the idea guys and their talk. In most organizations the idea guys like you describe will posse up because they have to.
- jmduke 14y agoMan, these are an awful lot of strawmen you're building up. I don't have any experience with/at Yahoo, but I imagine that there are a lot of good employees and a lot of bad employees and its important to identify which is which.
- statictype 14y agoAs a counter point to your hand waving: This guy: http://codahale.com/about.html http://codahale.com/about.html has 'Infrastructure Architect' as his job title. I'd be wary of painting everyone who has Architect in their title with your broad brush strokes.
- kamaal 14y agoI am sure infrastructure architects or senior sysadmins have their own variations or equivalents of writing code. Like knowing command line usage to the teeth. Making sense of any documentation by just reading man pages, without having to hit Google in dark server rooms. Or being able to building a Working Linux machine from scratch by compiling the kernel, and installing the utils. Or being able to network and administer a cluster of servers in a data center. This is vastly different than, a guy who would just draw a block of servers on MS paint and connect them through some lines and then call himself an architect.
- Retric 14y agoIf you can't write code vs I’m a software engineer who says Writing tests for your code may not reduce the number of bugs, but it will make fixing the bugs you inevitably find easier. Sorry, not the same type of person.