This is such an important point: A system with 99.99% guaranteed uptime must be 50 times(!) as reliable as one with "only" 99.5%. The cost of building and operating a system in a way that guarantees 99.99% uptime is several times as expensive as 99.5%. world.hey.com/itzy/how-much-β¦
Good post about learning Git: roadrunnertwice.dreamwidth.org/596185.html The only way that works is to understand the objects that make up its conceptual space (blobs, trees, commits, branches, remote-tracking branches, remotes).
The frontend community wants to wash its hands of the decade we lost without naming the causes and consequences of the dogma that swept away better, more grounded approaches and replaced them with MBs of JS. That's not a recipe for healing what was broken.
Git making me want to pull my hair out yet again. One of the most unintuitive, clunky interfaces of any software I've ever used.
Yesterday I saw a senior fullstack [web] engineer who couldn't close an <input> tag in React because we asked them not to use Material UI π and that's why we need interviews
We complain about the level of difficulty getting into tech while leaving out how much more easier it is to do the same things ten years ago.
New βDevs adding JavaScriptβ analogy just landed pic.twitter.com/ihtcF87gBX
The "JSON is lighter that HTML" argument is π₯΄ Most SPAs I see in the wild, will show a spinner with every page navigation, load "a little JSON", then decorate with HTML and render the page. Why not just update a piece of the page with HTML from the server?
When I started getting into programming, all these massive frameworks and CLI tools were so intimidating. JavaScript was such a breath of fresh air in comparison. Just add a script tag and off you go. I sometimes worry we've recreated the environment that almost scared me off.
My nephew is studying HTML and CSS in college. When he was telling me about it, there was a sparkle in his eyes when he told me that he can learn HTML by using a thing called "Inspect / View Source" in the browser. β¨ Now if only modern tools didn't ruin this for him.
In Hardcore Software "What Is Software Bloat, Really?" βtrying to define bloat was the first step in a major redesign effort. While many thought they knew it when they saw it, that wasn't really what the data showed. 1/ β¦rdcoresoftware.learningbyshipping.com/p/077-what-is-β¦
Isn't it weird that web browsers β 16 years after Gmail was released β still have *no idea* what a web application is? π‘ Browsers don't understand the meaning of: π€·ββοΈ A user π€·ββοΈ A single-page app π€·ββοΈ Reactive, client-side state π€·ββοΈ Templating π€·ββοΈ Inline editing π€·ββοΈ Auto-save
@darklang I'm actually over here screaming at some of the replies. Google analytics! Firebase+now! Lambda+SQS+S3! GitHub pages and hosted Redis! How did we let simple programs get so complex? We had this solved in 1997 pic.twitter.com/IaQvykYwhP