Aviran Mordo 🪐’s Post

In the heart of every enduring codebase at a massive, high-throughput internet company—serving millions of requests every second—you’ll find something striking: simplicity. The code that has stood the test of time is incredibly clean, almost obvious in its design. You look at it and think, “I could have written this in a day.” What’s invisible, however, is the journey behind it. This code has likely been rewritten, iterated upon, and refined hundreds of times. It has shed all unnecessary complexity, leaving only the essential, honed functionality. This simplicity isn’t accidental; it’s deliberate. Every line of code you write, you should feel a weight building in your shoulders. There’s this pressure to write as little code as possible, or better yet, no code at all. Every line written is a cost—an ongoing burden the company must carry. And yet, nothing happens without some code. It’s in this tension—between doing nothing and doing just enough—that the diamonds are forged.

✨ New Blog Post! ✨ Check out our latest article on "Understanding Compound Patterns in React". Learn how to build flexible and reusable components using the Compound Pattern and React Context. Perfect for tackling complex UIs with ease! Read more here: https://lnkd.in/gFJGmmtF

The reconciliation algorithm it's a core concept about React. If you're a Frontend or a Fullstack Engineer I'm sure that's something that you should dedicate a bit of time to understand deeply and one thing that could help you it's my new article in my Blog 🚀 🤘 https://lnkd.in/dCvt7wkk

Second article on ArchTorrent is out now! In the second article I cover the project structure and how BenCode encoding works! https://lnkd.in/dXXDw7qv

#DevSecOps high #maturitylevel example: #design and #threatmodeling #TrustEverybodyButCutTheCards Based on a detailed #threatmodel defined and updated through code, the team decides the following: • Local #encrypted #caches need to expire and #autopurged • #Communication channels #encrypted and #authenticated • All secrets persisted in #sharedsecrets store • Frontend designed with #permissions model integration. • #Permissions matrix defined • #Input is escaped, #output is encoded appropriately using well established #libraries. #TrustEverybodyButCutTheCards

An optimization technique : A state that need to react to multiple inputs : - useReducer with Memo Why?. - The reducer function is the same in memory - Therefore, it doesn't trigger a re-rendering https://lnkd.in/d9HphNMe Personal notes : https://lnkd.in/dzxRayDQ . . . . . #business #react #coding #user #interactions #core #architecture #design #performance

I wrote 4500 words diving into the evolution of React since Hooks. 🥵 I had so much fun writing this. It really helped me understand the ins and outs of React, including the Fiber architecture. 😁 https://lnkd.in/esVNE5W4

There are two major costs* to maintaining software. 1. Spelunking = the time and effort spent navigating, reading, and understanding the existing code in order to come up with a solution. 2. Risk = the possibility that fixing your bug will create a new issue somewhere else. We can automate away a lot of the risk cost through smart test writing, but how do we make our code “spelunk-able?” A couple ideas: - Mirror the operation of your application in your architecture. Hierarchies in your code should match the hierarchies in your UI. - Define your variables close to where they are used, and use naming conventions. - Typescript over JS every time in my experience. Typing is great for readability. - Line-per-file limits (though these should be generous) or component-per-file limits You'll thank yourself later (and so will your team) if your code is easily readable and requires no digging. _________ *Bob Martin, "Clean Architecture"

How to find cheapest ticket for your weekend? 😉 Just use A* algorithm... https://lnkd.in/dzgiqj7N Tree almost everywhere, since that every developer should know DFS and BFS algo! https://lnkd.in/d29s3gTy Explore this one lecture by UBER: #react #nextjs #algorithms #javascript #frontenddeveloper #tree

For IDE freaks, there's a new one, #Zed, which recently has been released, https://zed.dev/. It's written in #Rust making it significantly faster than VSCode and Jet Brains. Funny, the AI integration is already there. So, no worries :) It gives a nice and smooth feeling with a flashback to Sublime when working in it. Also, it gives some hope that the JavaScript hype & madness is calming down and soon, at least in part, some software would switch back to better suited technologies without the urge to write everything in one language and package as a web browser. #livingthedream