62 karma · joined September 27, 2017
I keep a large production Java codebase and its deployments up-to-date. Short of upstreaming fixes to every major dependency, the only feasible way to continue upgrading JDK/JVM versions has often been to carry explicit exceptions to new defaults.
JPMS is a good example: --add-opens still remains valuable today for important infra like Hadoop, Spark, and Netty. If other, even more core projects (e.g. Arrow) hadn't modernized, the exceptions would be even more prolific.
If libraries so heavily depended upon like Mockito are unable to offer a viable alternative in response to JEP 451, my reaction would be to re-enable dynamic agent attachment rather than re-architect many years of test suites. I can't speak for others, but if this reaction holds broadly it would seem to defeat the point of by-default changes.
The tool is for drawing "technical analysis indicators", one of the most convoluted ways to ascribe meaning to a random process and something that will only ever be true in the self-fulfilling sense. I don't think it's a surprise that some users are willing to blindly trust the tool, when all users of it are blindly trusting concepts that are built on sand.
Although I'm sure the author is burnt out from the experience now, I'd be interested in hearing how their next side project venture goes- is the experience more enjoyable when you're dealing with a user base that self-selects differently? Or do all users suck equally, just in different ways?
- scalar value
- feature toggle
- URI/enum option/human readable display text
Having float/long/boolean is trivial to validate in the config language itself, and if they're useful and simple enough isn't it nice to be able to validate your config as early as possible?
I'm really excited about https://jspecify.dev/, which is an effort by Google, Meta, Microsoft, etc to standardize annotations, starting with @Nullable.
If you run a bunch of different microservices with distinct allocation profiles, all with high allocation pressure and performance constraints, and you've accomplished this w/ the help of a very fine-tuned CMS setup, migrating that over to G1/ZGC is non-trivial
Their small class size and heavy new-grad hiring also means that they're usually more flexible with recruiting and some would probably welcome a new pipeline for talented new grads like this.
I’m just as surprised to see the number be this high. I can’t help but wonder if this might be due to survivorship bias: crossovers are, after all, self-selecting. Perhaps not all engineers would say the same, if forced to swap roles.
Regardless, I’m excited to hear more from these crossovers. As a (soon-to-be) recent graduate, I think there can tend to be a great difference in perception between CS students and Engineering students, particularly at institutions without rigorous CS programs. Many tend to view CS students in the same way that some CS students view bootcamp students- people motivated by an “easy path to success”. I’ve found this opinion is rarely held of engineering students, given the reputation of engineering programs. I think it’s very useful to profile the motivators, mindsets, and general attitudes between the disciplines, if only to see that perhaps the difference isn’t as large as one might assume.
Is this because it's easier (obviously) to teach a quant engineering than it is to teach an engineer quant finance? Or rather because it's expected now that traders will become the bridge between researcher models and implementation, and engineers will simply provide the underlying infrastructure to power these implementations?
For regular classes, A: 4.0, B: 3.0, C: 2.0, D: 1.0 (with some variance depending on + or - grades offered). For Honors/AP classes, every grade is essentially bumped up 1.0 point.
So yes, a 3.74 is around an A- average, but that's an A- average in less rigorous classes, without competition from top students. That's more of a B-/C+ average in AP/Honors classes (obviously the calculation is far from perfect, though, because every school has it's quirks- at mine, you couldn't get above a ~4.5 overall). For reference, I graduated high school with a 3.6 with multiple Cs and hardly any As, simply by virtue of taking the maximum number of AP/Honors classes. The point being, a 3.74 is not a terrible GPA, but good students are generally over a 4.0 these days.
[1] https://en.wikipedia.org/wiki/Media_cross-ownership_in_the_U...
We can see this pretty clearly looking at consumer reports[1], where you'll find that vinyls, compared to CDs, are actually being propped up largely by generations (18-44) that never properly experienced them. CD usage, on the other hand, is generally supported by older generations that are slower to adapt to modern streaming. Vinyl is almost vicarious nostalgia- most vinyl users I know (generally from the same age bracket) enjoy it as a deprecated technology that feels exotic. CDs aren't necessary for us anymore, and since we grew up with them, they aren't as enchanting and romanticized as vinyl.
[1] http://www.riaa.com/wp-content/uploads/2019/05/MusicWatch-Co...
The time of the people eligible for this program is worth more than $20/hr. This amount of money is never going to be a primary source of motivation for them. As the article said, "A side effect of building a company culture around OSS is that the kind of people who gravitate to work at Formidable are passionate about their open source work, and won’t stop contributing when they clock out at 5 pm." I did a bit of volunteer work in high school as part of a program, and upon graduation the program granted everyone a small, $250 "scholarship". I spent ~10 hours per week, for a year, as part of this program, thus making my "wage", if you will, about $2/hr. I can promise you, nobody participated in that program for the "scholarship". It showed that our time was appreciated, but wasn't nearly enough to incentivize the program to anyone who wasn't going to do it anyways.
I see nothing wrong with a token payment like this. It makes contributing to open source a more attractive option, but still only a viable option to those who were already motivated to contribute out of altruism. Obviously 20/hr isn't a token payment for a lot of us, but the concept itself of a token payment isn't something that necessarily invalidates altruistic intentions, in my view. I'll contribute to open source projects irregardless of whether or not they have a Bountysource, but I'll still accept a reward if it's offered. The purpose of this program is to reward people who are already motivated to contribute to open source, which in turn signals to its employees that Formidable appreciates open source contributions.