yearolinuxdsktp

10 ms·

91.
by yearolinuxdsktp 11mo ago
Max browser security levels and a good ad-blocker will not prevent you from getting phished or hacked more than an encryption-audited cloud-based zero-knowledge vault, where server compromise is irrelevant. All competent #1 cloud-based pass
92.
by yearolinuxdsktp 11mo ago
You can only avoid rotation on passwords that are MFA-protected. If you implement a password manager, you must mandate auto-fill only and actively discourage (via training) copy/paste of credentials to a web site. Train the users to vi
93.
by yearolinuxdsktp 11mo ago
The 10K cycle insertion rating for USB-C is an idealized metric that does not include lateral force, torque, device movement, or real-world wear patterns. These non-axial forces are a known cause of USB-C port failures and are explicitly no
94.
by yearolinuxdsktp 11mo ago
Not to mention that perfectly normalizing a database always incurs join overhead that limits horizontal scalability. In fact, denormalization is required to achieve scale (with a trade-off). I’m not sure how formal verification would’ve pre
95.
by yearolinuxdsktp 11mo ago
This is intentional on Google’s part. It’s anticompetitive behavior, to make YouTube service’s app shitty on Google’s competitor’s ecosystem. But no government seems to care—-and what will you do, stop watching YouTube?
96.
by yearolinuxdsktp 11mo ago
YouTube app on Apple TV is inexcusable garbage, likely intentionally so. Google doesn’t want you to have a good experience on an Apple product.
97.
by yearolinuxdsktp 11mo ago
IMO Pulumi and CDK are an opportunity to simplify your infra by capturing what you’re working with using higher-level abstractions and by allowing you to refactor and extract reusable pieces at any level. You can drive infra definitions eas
98.
by yearolinuxdsktp 11mo ago
Well Bayesian stats can be a superior stats tool vs frequentist for A/B testing applications, especially around digital traffic, where it builds with time and it’s different than calling up a sample size of people, and when you want to
99.
by yearolinuxdsktp 11mo ago
What about the Republic of Ireland?
100.
by yearolinuxdsktp 11mo ago
Makes sense, I agree then that #1 as you exactly define it is insane.
101.
by yearolinuxdsktp 11mo ago
This is an organizational/tech leadership problem. Good technical leadership will put a kibosh on working on hypotheticals, because what you don't do is as important as what you do. Good programmers pride themselves on striking co
102.
by yearolinuxdsktp 11mo ago
Facts! #1 is not insane as long as you keep your internals modular (all-in-one deployment doesn't mean ball of mud... you can avoid putting service calls into your domain objects or your data plane code). And you can go from #1 to #2 o
103.
by yearolinuxdsktp 11mo ago
Being saddled with an old code base with a mountain of tech debt does not invalidate the OP's argument about modularity and microservices. I feel for your pain. You describe a great approach of how to tackle a monolith with mountains o
104.
by yearolinuxdsktp 1y ago
I agree that a business should use Kubernetes only if there is a clear need for that level of infrastructure automation. It's a time and money mistake to use K8s by default.
105.
by yearolinuxdsktp 1y ago
Running EKS on AWS was their problem. If they didn't run EKS on AWS, they would've had a considerably simpler setup running Amazon Linux, not having to upgrade Kubernetes every 3 quarters, managing network security using security
106.
by yearolinuxdsktp 1y ago
I think it’s a far cry on the original author’s side to call the use of map().filter().map() an obsession with FP. Underscore.js simply provided super-useful functions over arrays and objects, which IMO makes for more legible code. Often ti
107.
by yearolinuxdsktp 1y ago
I agree that saying that no-one uses backwards compatible stuff is bizarre. Rolling deploys, being able to function with a mixed deployment is often worth the backwards compatibility overhead for many reasons. In Java, you can accomplish so
108.
by yearolinuxdsktp 2y ago
Luckily, in right to repair states, Such as Massachusetts, Subaru chose to disable Starlink altogether instead of making Support documentation available under the law.
109.
by yearolinuxdsktp 2y ago
Every line of documentation is a line of code and is a liability as it will rot if not maintained. That’s why you should be writing self documenting code as much as possible that’s obviates the need for documentation. But unlike code, stale
110.
by yearolinuxdsktp 2y ago
Nothing about computers is intuitive. Not even using a mouse. A late-breaking change is a business advantage—-learn how to roll with them.
111.
by yearolinuxdsktp 2y ago
That keeps the history but not the annotations of the lines. Git blame will shows basically all lines as last changed by Kotlin transform.
112.
by yearolinuxdsktp 2y ago
Not really—-most CI reporting is based off junit/testng report XML files. I doubt your CI reporting is parsing out test names with regexes out of log files.
113.
by yearolinuxdsktp 2y ago
Spock is an exercise in syntax cleverness with regular confusion opportunity and little gain IMO. Way too much implicit syntax that IDEs struggle with. Refactoring Spock tests sucks due to how the context is different based on the clause yo
114.
by yearolinuxdsktp 2y ago
Ah thank you for actually reading the referenced study
115.
by yearolinuxdsktp 2y ago
Jeez what an ugly option.
116.
by yearolinuxdsktp 2y ago
I cry for the years of lost got blame history. It sure must suck to delve into an issue in a 10M-line-code base and have all your lines be annotated with useless language conversion commits.
117.
by yearolinuxdsktp 2y ago
A whole lot of pie in the sky architects, which seems to be all of Kotlin authors and all of Kotlin-writing cadets, sure love to dream that closed by default is a good design choice and think of times when something open was extended or acc
118.
by yearolinuxdsktp 2y ago
From experience CI test reports are vastly more comprehensible at a glance. That study compared camel case to underscore spaces. Well underscore space is still not as readable as methods with spaces and dashes.
119.
by yearolinuxdsktp 2y ago
If you use a good IDE it will select the whole method name. In general you would not use spaces for method names of anything that’s a shared/common use facility. They are best used to give test methods readable names. E.g. “test parall
120.
by yearolinuxdsktp 2y ago
all-open plug-in is the only sane way to operate Kotlin.

More ›