3 ms·
My pet peeve is how these brilliant architects end up writing so much code that does nothing. These 1 line functions just end up calling another 1 line function
by goalieca 12y ago
My pet peeve is how these brilliant architects end up writing so much code that does nothing. These 1 line functions just end up calling another 1 line function. At some point someone actually has to write the code. You know, that thing that actually does the work.
I always figured OOP programmers actually hate coding because they try so hard to avoid actually writing code that does work.
- nickbauman 12y agoI would consider myself lucky that someone with the word 'architect' in their job title on my team wrote code that did nothing. Careful what you wish for.
- slowmovintarget 12y agoThere are Marchitects, Tarchitects, and Farchitects (Market-oriented, Technology-oriented, and umm... "freaking" architects). Sounds like you have a team of Farchitects. I have the title "architect", and I write code. It's usually code that lets the other thirty programmers write one or two lines of code instead of 200 lines, 30 times, in 17 different ways. Because it is framework code, I'm often providing them the Lego blocks to build the rest of their system in... With unit tests... and examples... and at least one real implementation... and a Wiki page explaining it... and a Powerpoint session teaching them how I expect them to use it. I do get the occasional grumble ("Uhh... Can't I just use Doohickey V directly?" "Sure, take a look at the interface, and don't forget the externalized configuration." "Oh.") Just sayin'. There are architects and there are Architects.
- deleted 12y ago[deleted]
- pjmlp 12y agoI have seen architecture skyscrapers in Assembly, Clipper, C, C++, you name it. It is something that is part of enterprise culture, it has nothing to do with programming languages.