@Sharas_ @alpengeist_de Not a bad definition at all. Architects will often decide to create additional constraints though.
1
Most enterprise developers overestimate their systems' inherent complexity by about as much as non-enterprise devs underestimate it
1
14
2
Something is really wrong on the Internet: vlt.tc/hnk (via @cornelis)
9
4
@mtnygard You didn't listen to music in the 80s, did you? //cc @scottdavis99
1
@louisck Rarely enjoyed anything on TV as much as that series. Please don't stop anytime soon.
1
@christo4ferris @stevevinoski Very impressive, particularly youtube.com/watch?v=FLT3Cb96… //cc @neal4d
@sshishkin Interesting, don't know if I can make it, but will try
@sshishkin I can only assume you believe I'm talking about UML tools, not the notation itself. I'm not.
@sshishkin If you really believe there is a causal relationship, I guess we'll have to disagree
2
@Eigenbrodtm I think architecture is what happens if a bunch of guys like you finally agree on something
@scottclasen @cowtowncoder +1. You'll know a coding architect from a non-coding one in a minute if you're a developer.
1
@CMontemuino I agree re. EAs, but then they shouldn't be allowed near a software project anyway :-)
1
@sshishkin So using boxes and lines with defined semantics is somehow worse?
1