122 karma · joined November 21, 2021
I write about software development on my blog: https://tiberriver256.github.io
For a more nuanced and careful discussion of the topic I like to reference: https://martinfowler.com/articles/feature-toggles.html
I know parallel ATA cables were all the rage. They had a higher theoretical throughput when compared with serial ATA cables but there was too much cross-talk involved to make it actually faster in the end so now we have serial ATA cables everywhere with much higher throughput than parallel ATA cables could ever achieve.
Should we move back away from parallelism and focus on handling synchronous stuff faster instead?
I think maybe they need someone to help write some user friendly documentation.
Hold off on loading and playing the videos until they are visible: https://web.dev/lazy-loading-video/#video-gif-replacement
Automatically pause the video when they are scrolled off the screen and no longer visible: https://benfrain.com/automatically-play-and-pause-video-as-i...
So if you have a like button with the number of likes totalling 3, and someone were to hit the like button to increase the count to 4 the only content transferred would literally be a string value of '4'
Honestly, I'm still not sure if people could breathe without things like air.
Such a sad trend :( but seems to be very prevalent
https://github.com/ShaunLawrie/PwshPaint/blob/main/PwshPaint...
I've done considerable work with it and niche cases like this the at a teensy bit of web to PowerShell is a perfect usecase
There is no mention of estimates at all lol.
From the outside it appears that they only have two nameservers assigned per organization, contrary to the recommendations in RFC2182 section 5 and the nameservers are intermittently coming online and going back offline again.
He made the point that micro-services are a deployment method not an architecture. A good clean architecture shouldn't care how it's deployed. If you need to move from plugins to micro-services to be massively scalable your architecture shouldn't care. If you need to move from micro-services to plugins to make your app simple to host and debug, your architecture should also not care.
This strategy has been implemented in frameworks like abp.io very successfully. You can start your application as a single collection of split assemblies deployed as a single application and move to deploying as micro-services when it's necessary.
https://ckrybus.com/static/papers/Bainbridge_1983_Automatica...
Automation makes people dumber.