nfrankel

11 ms·

91.
by nfrankel 5y ago
> If your build has really custom stuff That's the biggest problem. Nearly every developer thinks their build has *really* custom stuff whereas it's wrong in 99% of the cases. Then comes Gradle with its so-much-vaunted flexibil
92.
by nfrankel 5y ago
I was a consultant and I used the rule of 3 whys. When a customer asks for a feature, get back to the root concern by asking "why"?
93.
Gitlab as your Continuous Deployment one-stop shop(blog.frankel.ch)
1 points by nfrankel 5y ago|0 comments
94.
by nfrankel 5y ago
Rust newbie here. I confirm both the friendliness of the compiler and of the community.
95.
Rust and the JVM, Stronger Together(blog.frankel.ch)
3 points by nfrankel 5y ago|0 comments
96.
Rust on the Front-End(blog.frankel.ch)
3 points by nfrankel 5y ago|0 comments
97.
BlockHound: How It Works(blog.frankel.ch)
1 points by nfrankel 5y ago|0 comments
98.
JVM Ecosystem Report 2021(snyk.io)
2 points by nfrankel 5y ago|0 comments
99.
Study on link rot/content drift on the NY Times links(twitter.com)
1 points by nfrankel 5y ago|0 comments
100.
Hacking third-party APIs on the JVM(blog.frankel.ch)
2 points by nfrankel 5y ago|0 comments
101.
Security and Trust in Open Source Security Tokens(eprint.iacr.org)
1 points by nfrankel 5y ago|0 comments
102.
Matter is the new name of Project CHIP that promises to simplify your smart home(theverge.com)
2 points by nfrankel 5y ago|0 comments
103.
The Medieval Census Problem(infoq.com)
1 points by nfrankel 5y ago|0 comments
104.
by nfrankel 5y ago
That's because you don't deal with state
105.
An example of overengineering – keep it WET(blog.frankel.ch)
2 points by nfrankel 5y ago|0 comments
106.
Property-based testing, a hands-on example(github.com)
2 points by nfrankel 5y ago|0 comments
107.
by nfrankel 5y ago
This. I found that most people focus on size and forget about reuse. Sure, each layer adds size to your final image, but you can reuse them, so that you don't need to transfer the complete image but just the layers on top of the one th
108.
by nfrankel 5y ago
Colin Powell, Mr "weapons of mass destruction" himself side-by-side with Jimmy Lai of Hong-Kong fame. I don't know whether to laugh or to cry.
109.
by nfrankel 5y ago
The biggest issue I see in this list is that it compounds multiple concerns: grammar, Google and socio-political (or however you choose to call it). While it makes a lot of sense for Google, I have no reason to use it if I'm not a Goog
110.
JEP 411: Deprecate the Security Manager for Removal (with no alternative)(openjdk.java.net)
4 points by nfrankel 5y ago|0 comments
111.
by nfrankel 6y ago
The bigger the company, the easiest it is to get away by doing nothing. Find a Big Corp, be nice to your boss and your colleagues, don't make waves and you can basically have an above-average-pay while being able to slack most of the t
112.
Changing a field's type in recent JDKs(blog.frankel.ch)
1 points by nfrankel 6y ago|0 comments
113.
by nfrankel 6y ago
That's a great question! In the context of this post, I wanted to check how much work the Spring team had done so I did the trial-error-fix process on purpose. On real-world applications, I suggest you use the Java agent that comes fro
114.
Spring and GraalVM and Kotlin = Interesting Results(blog.frankel.ch)
3 points by nfrankel 6y ago|2 comments
115.
Russian, Chinese hackers targeted Europe drug regulator(reuters.com)
1 points by nfrankel 6y ago|0 comments
116.
Goodbye Minikube(blog.frankel.ch)
1 points by nfrankel 6y ago|3 comments
117.
Beyond “Hello World”: Zero-Downtime Deployments with Hazelcast on Kubernetes(hazelcast.com)
2 points by nfrankel 6y ago|0 comments
118.
Blocking violations in reactive Java frameworks (paper) [pdf](diva-portal.org)
1 points by nfrankel 6y ago|0 comments
119.
by nfrankel 6y ago
I wholeheartedly agree!
120.
Distribution of JVM Desktop Applications(blog.frankel.ch)
133 points by nfrankel 6y ago|122 comments

More ›