Nice. We made fridge-magnets in my last project to help generate excellent names like these.
Haha, I need to try this but for the whiteboards at work. We sometimes try to come up with ridiculous names too
Java: Real or Not?
51–60 of 68 posts
Re: Java: Real or Not?
#52Like any other primitive, dogmatic religion, Java will stay for ages, because there will never be a shortage of idiots to repeat the dogmas and mediocries to have a decent living by manipulating the crowd.
Java is triumph of the "packers mindset".
http://the-programmers-stone.com/the-original-talks/day-1-th...
Re: Java: Real or Not?
#53[deleted]
Re: Java: Real or Not?
#54Nice job blaming all of Java for Spring's foibles
Re: Java: Real or Not?
#55Like any other primitive, dogmatic religion, Java will stay for ages, because there will never be a shortage of idiots to repeat the dogmas and mediocries to have a decent living by manipulating the crowd. Java is triumph of the "packers mindset". http://the-programmers-stone.com/the-original-talks/day-1-th...
This post perfectly sums up a mindset I detest. Engineers get shit done and don't care about whatever the most recent hipster programming language is. They can probably spell "mediocrity" as well.
Re: Java: Real or Not?
#56Like any other primitive, dogmatic religion, Java will stay for ages, because there will never be a shortage of idiots to repeat the dogmas and mediocries to have a decent living by manipulating the crowd. Java is triumph of the "packers mindset". http://the-programmers-stone.com/the-original-talks/day-1-th...
This post perfectly sums up a mindset I detest. Engineers get shit done and don't care about whatever the most recent hipster programming language is. They can probably spell "mediocrity" as well.
I'm with you.
I really don't think people with that mindset could put together the sort of shit we do on the enterprise mindset side of things. The tools are carefully picked to be entirely the opposite to the contrarian mindset.
So we have a system that has about 500 HTTP endpoints, 600 service endpoints, 4MLoC, several TiB of data, several TiB of documents, handles 5000 concurrent users 24/7 ramping up to 2 million euro consumers (not concurrent) and 10 full 42U racks of kit in two facilities. Oh and strict security isolation through several layers.
Java+c# is the only answer.
But 50 times a day someone says, hey rewrite it all in Ruby and Monogo. That's a joke.
Re: Java: Real or Not?
#57It never hurts to study the masters in serious enterprise software: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
This is great but it brings up a serious question I've always had. Taken to the extreme, things like the single responsibility principal, the open closed principal, etc, result in messes like this. I've been wondering if anything has been written around a concrete methodology of doing OOP that doesn't naturally converge onto something like this, and why it happens.
OOP is seldom the best model for software construction. A model (using relational, graph, set operations, etc.) can be implemented using enties given in an OOP language but if the software engineer 'thinks in objects' mess will probably ensue.
Re: Java: Real or Not?
#58Earlier quoted context omitted.
This post perfectly sums up a mindset I detest. Engineers get shit done and don't care about whatever the most recent hipster programming language is. They can probably spell "mediocrity" as well.
I'm with you. I really don't think people with that mindset could put together the sort of shit we do on the enterprise mindset side of things. The tools are carefully picked to be entirely the opposite to the contrarian mindset. So we have a system that has about 500 HTTP endpoints, 600 service endpoints, 4MLoC, several TiB of data, several TiB of documents, handles 5000 concurrent users 24/7 ramping up to 2 million…
Out of curiosity does your system need to be this complex? Could it have broken down into smaller sub-systems that maybe aren't as integrated, but get the job basically done?
Re: Java: Real or Not?
#59Like any other primitive, dogmatic religion, Java will stay for ages, because there will never be a shortage of idiots to repeat the dogmas and mediocries to have a decent living by manipulating the crowd. Java is triumph of the "packers mindset". http://the-programmers-stone.com/the-original-talks/day-1-th...
This post perfectly sums up a mindset I detest. Engineers get shit done and don't care about whatever the most recent hipster programming language is. They can probably spell "mediocrity" as well.
Exactly! The very term you use is telling - "shit" is exactly what comes out of Java sweatshops. They call it Enterprise Software - write once, run away.
BTW, how many languages do you speak well enough to hold an intelligent conversation?
Re: Java: Real or Not?
#60Earlier quoted context omitted.
This post perfectly sums up a mindset I detest. Engineers get shit done and don't care about whatever the most recent hipster programming language is. They can probably spell "mediocrity" as well.
I'm with you. I really don't think people with that mindset could put together the sort of shit we do on the enterprise mindset side of things. The tools are carefully picked to be entirely the opposite to the contrarian mindset. So we have a system that has about 500 HTTP endpoints, 600 service endpoints, 4MLoC, several TiB of data, several TiB of documents, handles 5000 concurrent users 24/7 ramping up to 2 million…
How come that most of recent 3G and 4G GSM systems runs Erlang order of magnitude more efficiently?