joshdev

7 ms·

31.
by joshdev 13y ago
Some more context here would be useful. It's easy to assume the request is 100% ridiculous from the PM's side, but maybe the project has seen a significant decrease in quality recently. Has the bug rate skyrocketed? Have outage
32.
by joshdev 13y ago
Light on details, mainly a marketing blog post for paid DDoS services, move along.
33.
by joshdev 13y ago
Buying more RAM only gets you so far. G1 handles large heaps fairly well, but you can still run into issues with long pauses if you are not careful and those pauses increase with the size of the heap. Most real time services don't have
34.
by joshdev 13y ago
+1 for Trove. Recently when working with collections with 10s of thousands of primitive elements. We saw substantial memory savings by using Trove.
35.
by joshdev 13y ago
http://en.m.wikipedia.org/wiki/Second-system_effect not much has changed in the past 40 years
36.
by joshdev 14y ago
At my company we started a Scala project a little over a year ago. Two of us had a Java background the other two had a C++ background. We targeted Scala 2.9, Akka 1.3, and ran it on JVM 1.6. For us the stack proved to be very easy to wor
37.
by joshdev 15y ago
It's really not a bad way to go. You may still get reactions like you've come to expect from developers, but a sign of a good developer is whether after having that knee jerk reaction, they start asking about your technology choices and ho
38.
by joshdev 16y ago
It's all in how you approach programming. If you view it as a puzzle and enjoy finding new ways to optimize some workflow it can be very enjoyable. Yes there are tedious moments, but those goes with just about any career out there and I'd