Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@CWins I'd roughly translate it to "the simplest solutions are the best". It's not exactly but should still be understandable by non German speakers :P
-
@Wack
It translates the content, but it doesn't translate the vibe. ;-) -
@zshh Not enough space in a reply to do it justice, but I am one of the few that does speak up. Not only do I speak up, I follow up with action. I could probably write a book on the half-assed designs these guys come up with, we argue over some 'perfect' academic solution and 100% of the time when the 'rubber meets the road', the simpler solution is implemented. Why? We're not a college or some intellectual think tank. We're here to serve customers, we're here to serve people, and we're here to serve the business. That's it.
Did I go 'behind their backs'? Not really. I was quite vocal that their solution was way..way..way too complicated for what was needed. Again, not enough space in a reply to get into the lengthy details (and the boring office politics) -
@PaperTrail I hear you. Good thing you spoke up about it! :) But by reading your first post I didn't get that impression.
Having no knowledge whatsoever about what you do the estimated time those guys gave sounds insane! I feel like I'd be able to learn AND implement that shit in 6 months.
Experience that made me feel like a dev badass?
Users requested the ability to 'send' information from one application to another. Couple of our senior devs started out saying it would be impossible (there is no way to pass objects across a machine's memory boundary), then entertained the idea of utilizing the various messaging frameworks such as Microsoft's ServiceBus and RabbitMQ, but came up with a plan to use 2 WebAPI services (one messenger, one receiver) along with a homegrown messaging API (the clients would 'poll' the services looking for message) because ServiceBus, RabbitMQ, etc might not be able to scale to our needs. Their initial estimates were about 6 months development for the two services, hardware requirement for two servers, MSSQL server licenses, and padded an additional 6 months for client modifications. Very...very proud of their detailed planning.
I thought ...hmmm...I've done memory maps and created simple TCP/IP hosts that could send messages back and forth between other apps (non-UI), WPF couldn't be that much different.
In an afternoon, I came up with this (see attached), and showed the boss. Guess which solution we're going with.
The two devs are still kinda pissed at me. One still likes say as I walk in the room "our hero returns"....frack him.
undefined
wk65