bvrmn

29 ms·

391.
by bvrmn 4y ago
Wow, you just gave me an idea to make retry code with a loop: for _ in repeat_until_success(timeout=10, backoff=0.1): if success(...): break
392.
by bvrmn 4y ago
> It is hubristic in the extreme to sit in judgement over the architectural choices a team has made on a system you don’t know or understand, and just downright rude to conjecture all the worst failure modes of that architecture and then
393.
by bvrmn 4y ago
I don't agree. Almost every candidate during interview likes to talk how their team of 3-5 people manages multiple microservices. It's pretty much hype driven approach to develop a backend application.
394.
by bvrmn 4y ago
$my_properly_named_array[$#my_properly_named_array] doesn't look like QoL.
395.
by bvrmn 4y ago
This. It makes more sense to bind apps to homerow keys with some chain or modificator to "snipe" often-used applications instead of F-keys.
396.
by bvrmn 4y ago
But it's original intention was to fix this very issue.
397.
by bvrmn 4y ago
You really should not rely on OS and make small `send()` syscalls in hope it would magically work. Too much overhead.
398.
by bvrmn 4y ago
Always curious how Ada solves ABI issue with such optimizations in place.
399.
by bvrmn 4y ago
Funny thing that 100% coverage really helps for dynamic typed languages. It's easy and helpful.
400.
by bvrmn 4y ago
Could you elaborate with python-oriented examples? I tend to agree for static typing languages like Java — to fully test you have to go a total DI path. It leads to bloat and additional layers. I don't see anything similar for python b
401.
by bvrmn 4y ago
> I've seen 100% code coverage with tests for all the getters and setters. These tests were not only 100% useless, they actively hindered any changes to the system. It's a red flag to blame high coverage for fragile tests. Use
402.
by bvrmn 4y ago
> Coverage measurements are too easy to “game” — you can get to 100% coverage without meaningfully testing all or even most of your code Still it's a good low bar for testing. It's easy and rises code quality. I have very good
403.
by bvrmn 4y ago
It's a cursed notion that unit-tests are "set up mocks around functions and call them with different arguments". It's more useful to categorize tests by how hard to setup an environment. In reality cost/usefulness l
404.
by bvrmn 4y ago
This. So many "do not cover" hints for exception handler blocks. So many lost root causes when handler tries to format a error.
405.
by bvrmn 4y ago
It seems DSL proponents grow from environment without rich standard library. And classic Knuth argument, of course. It's so hard to count words. General purpose language: >>> from collections import Counter >>
406.
by bvrmn 4y ago
And how to make it work with largely unstable crypto/fiat ratio?
407.
by bvrmn 4y ago
> Most of the projects start as monolith, but as time goes on, the project turns into a big ball of mud. Start as microservices and you get a bigger and dirtier ball of mud. Guaranteed. Because you have no notion about boundaries at star
408.
by bvrmn 4y ago
And how to change a dozens accounts on others services to a new email without old one?
409.
by bvrmn 4y ago
> Microservices also can have incredible performance improvements over monoliths At this point it's like "Mongo is Web scale" meme. It's so false on so many levels without a proper context. Not surprising inexperience
410.
by bvrmn 4y ago
> Usually the work crosses several layers in at least one place You are doing it wrong then. It's basically a violation of SRP. Your changes should touch only one layer. If it's not, you have fragile abstractions. I agree there
411.
by bvrmn 4y ago
To add to explanation: inner fillets relax material stress in the corners and make final produced thing more durable and strong. You pretty much can't use CAD without fillets for real industrial applications.
412.
by bvrmn 4y ago
OpenSCAD required bottom-up approach, starting from smallest features to be able to transform their position in a final model. Too hard for actual real things to make reason about. I'm a programmer for 20 years and can't use OpenS
413.
by bvrmn 4y ago
The trick is to make clean layers with distinct responsibilities. And magically you have no to keep all details in a memory. Unfortunately there is no good formal method to make clean layers. Currently we practice it via bruteforce through
414.
by bvrmn 4y ago
Does it calculate generic Shore?
415.
by bvrmn 4y ago
In what parallel universe auditors make anything meaningful? It's like buying an indulgence and have someone to delegate risks to.
416.
by bvrmn 4y ago
Wow. 4 hours of my life have disappeared.
417.
by bvrmn 4y ago
It looks pretty difficult to exploit. Untrusted 4GB input with non-chunked update.
418.
by bvrmn 4y ago
Rewrite it in Rust. /s Implement transparent APIs from AWS, Azure, GCP for OpenStack, so we can reuse Pulumi and Terraform. Make it easier to install it. Make it easier to work with Prometheus stacks, Service mes
419.
by bvrmn 4y ago
> The problem is most engineers don’t want to do operations work. My experience tell that most engineers don't want to do any work and it's ok.
420.
by bvrmn 4y ago
This! There is no additional security for aware users with MFA. Make MFA turned on by default, ok, but for god's sake if you provide only SMS-based 2FA, allow it to be disabled.

More ›