Oasis’ Post

Surprise, Surprise. Vercel overestimated the power of Edge and now they are back to old pal Node. I was not too fond of this feature and did not want to use it as long as possible. It looked suspiciously good to me. It is not as fast, cheap, and secure as Node. Moreover, the new Node is fast and rapidly improving, it is still the best choice. I have a similar opinion about all these Bun, Yarn, Pnpm package managers that eventually get slower than npm or equally slow. Whereas, NPM is getting better and better by learning from the mistakes of its competitors. You can read the post about Vercel's rollback here (Lee Robinson tweet): https://lnkd.in/eWEFKKgw

In case you're not yet aware - our engineering team shares a monthly post about progress in the code, what we're working on, important release updates, and news from around our developer community. The series is called "Trunk & Tidbits" (related to our mascot, but also "trunk" as in, the main code repository; and tidbits, as we share bits of news). You can find these updates as part of our main blog. In last month's update, we wrote about the final changes that were merged ahead of the recent 4.3 release, and our new project for Fediverse Discovery Providers, aka "Fediscovery".

Pull request code review is an essential quality step in your SDLC, but with 'lightning PRs' - where a Pull Request is submitted / reviewed / merged within 5 minutes - this may mean that minimal actual reviewing is done, and the opportunity for correction or improvement is missed. What's your best practice for code reviews? And how do you track this?

Measure twice, cut once... ✂ Or if you're reviewing PRs, give yourself more than 5 minutes ⏲ The push for an Elite LTTC might mean you're putting your code quality at risk. ⚠ Have a look at our latest report breaking down the challenges of wanting to be Elite.

This took some time and creativity, but this client we consulted for now passes the Interaction to Next Paint metric. Meaning that their overall #CoreWebVitals are passing as well, since LCP and CLS were already in the green 💚 → We looked into the impact of third party scripts during an #INP → Made a small design change where the "load more" button on the listing page now shows "loading" while fetching new products. → The developers rewrote some code, since this was more time efficient than fixing the old code And to make the INP stay in the green we started to use scheduler.yield 🚀 So yep, it took a month or so to fix INP, which is insanely fast considering the size of the project. Well played devs :)

Quick Tips Clarifying Jargons in Software Engineering ! Noisy Neighbor = An app/service using too many shared resources Ex: One service on a server using all CPU, slowing others Do you find managing noisy neighbors in real world as challenging as dealing with Noisy Neighbor in complex software architecture? #noisyneighbor, #resourcecontention, #serviceisolation, #cloudperformance, #resourcemanagement, #microservices, #performanceoptimization, #concurrencyissues, #loadbalancing, #capacityplanning, #ratelimiting, #faulttolerance, #servicereliability, #qos, #scalingstrategies

In this video we take a look at how to pull validation out of our Web/UI layer and move it closer to our business/domain layer. https://bit.ly/3Py191n #FluentValidation #ChainOfResponsibility #CleanArchitecture #validation

Concurrency and parallelism often cause confusion, but let's break it down: 👉 Concurrency: Multiple tasks appear to make progress over time. It's an illusion—the processor switches between tasks. 👉 Parallelism: Tasks actually make progress simultaneously, requiring multiple processors or cores. In reality, tasks can execute in different ways: sequential, concurrent, parallel, or both. Key points: 1️⃣ Concurrency deals with managing many tasks simultaneously. 2️⃣ Parallelism executes multiple tasks truly simultaneously. 3️⃣ An app can be concurrent but not parallel, or vice versa. 4️⃣ Not all parallel executions are concurrent. What are your thoughts on concurrency vs. parallelism? Let's discuss! 💬💡 #SoftwareEngineering #Concurrency #Parallelism #SystemDesign #Architecture #Multithreading #MultiProcessing #TechDebate #DeveloperDiscussions #TechTopics #LearnAndGrow #ProgrammingConcepts #TechCommunity

You don't need a whole team of platform engineers to build your digital platform. Reduce the developer toil of building a platform. #platformengineering #digitalization

In this video we take a look at how to pull validation out of our Web/UI layer and move it closer to our business/domain layer. https://bit.ly/47D1WV3 #FluentValidation #ChainOfResponsibility #CleanArchitecture #validation