Behnam rahimpour’s Post

Say Goodbye... While I personally still see all the value and granularity available from within this console, it still fails to intuitively translate that value to a user. Some points to steer the next iteration; - UI without direction is just art - Technical people care more about UI than I first expected (thought backend value would still translate with basic frontend) - Keep it simple stupid (webamon.co.uk) This is still available on github and will work with all issued apikeys indefinitely or fully on-prem. Focused dev is on data collection pipelines & complete overhaul/simplifying of frontend G'luck

Code Maintenance can be defined by : - How often can we ship code?. - How confident we are to change code without breaking stuff - Can we do a refactor without fear? - Can we update deps without fear? https://lnkd.in/dgweQNwi Personal notes : https://lnkd.in/dinZ7pu4 . . . . . . . . #infrastructure #ui #business #development #react #vite #playwright #web #enterprise #scalability #scale

Explaining the BFF (Backend for Frontend) Design Pattern!! • #Microservices • #MicroserviceArchitecture • #APIDesign • #MicroserviceDesignPattern • #SoftwareArchitecture • #BackendDevelopment • #BFFPattern • #APIDevelopment • #SoftwareEngineering

Choosing the right frontend framework enhances 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗲𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆 by streamlining UI components, 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗶𝗻𝗴 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲, and ensuring faster, more maintainable code with built-in tools and 𝗿𝗲𝘂𝘀𝗮𝗯𝗹𝗲 structures. #FrontendDevelopment #WebDevelopment #UIComponents #CodeEfficiency #PerformanceOptimization #JavaScriptFramework #ResponsiveDesign #DeveloperTools #CleanCode #TechInnovation

Simple, decoupled codebases “The source code for each individual micro frontend will by definition be much smaller than the source code of a single monolithic frontend. These smaller codebases tend to be simpler and easier for developers to work with. In particular, we avoid the complexity arising from unintentional and inappropriate coupling between components that should not know about each other. By drawing thicker lines around the bounded contexts of the application, we make it harder for such accidental coupling to arise.” Martin Fowler & Cam Jackson https://lnkd.in/gzUWDysK

Short, uninformative names might seem quicker to type at first, but especially in larger projects, they can make your code harder to understand – even for yourself! Taking a few extra seconds to use clear variable names that reflect their purpose will make your code much easier to read and debug later on. #didyouknow #codingtips #software #softwaredevelopment #softwaredevelopmentcomapny #webdevelopment #frontend #backend #uiux

Forget the frameworks, let’s create Micro-Frontends with React Router Using Bun and Vite: Part 2 Overview: - Vite: A modern build tool offering fast development, efficient module loading, and optimized builds. - Bun: A high-performance JavaScript runtime that improves the development and production experience. Advantages of Vite for Micro-Frontends with React Router: - Blazing Fast Development Experience: Quick server start and instant refresh after code changes, ideal for iterative development. - Efficient Module Loading: Loads only the required source files on demand, reducing initial load times. - Enhanced Hot Module Replacement (HMR): Provides immediate feedback during development, boosting productivity. - Optimized Production Build: Uses Rollup to create lean and efficient bundles, ensuring fast load times. - Seamless Integration with React Router: Enables easy setup of client-side routing, facilitating smooth navigation and dynamic loading of micro-frontends. Differences Compared to Established Frameworks: - Architecture and Design: -- Vite and Bun require manual setup for integrating micro-frontends, whereas established frameworks like Single-SPA, Bit, and Module Federation provide built-in tools and APIs. - Integration Complexity: -- Vite and Bun involve manual integration for routing, state management, and communication. Established frameworks offer easier integration with advanced features. - Performance and Optimization: -- Vite provides fast HMR and optimized builds, while Bun enhances runtime performance. Established frameworks focus on efficient dependency management and module loading. Pros of Vite and Bun: 1. Performance: Fast development and high-performance runtime. 2. Flexibility: Highly customizable setup tailored to specific project needs. 3. Simplicity: Easier to set up for developers familiar with React Router and Vite. Cons of Vite and Bun: - Manual Setup: Requires manual integration for various aspects of micro-frontends. - Limited Features: Lacks advanced features like lifecycle management found in frameworks like Single-SPA. - Consistency: Ensuring consistency across micro-frontends can be challenging without a centralized management tool. Using Vite and Bun provides a performant and flexible solution for creating micro-frontends with React Router, suitable for projects where simplicity and high performance are key. However, for larger, more complex projects, established frameworks offer the necessary tools and features for effective micro-frontend management. https://lnkd.in/e7PNtWxi

Unit Test Structure : - Setup - Logic - Assertion. Tips : Repeated code is more useful because you got everything at glance. https://lnkd.in/daz-qPm8 Personal notes : https://lnkd.in/dinZ7pu4 . . . . . . . . #infrastructure #ui #business #development #react #vite #playwright #web #enterprise #scalability #scale

Yesterday, we covered one of the main pitfalls with #nocode / #lowcode: https://lnkd.in/dKbxCVcs Today, let's continue with the next one: 2️⃣ Limitations in the functionality Basically, it's when you can't do what you want to do. And you know that these things are, in general, feasible except on that platform. And there is nothing you can do about that. Sometimes, you can't customize UI; other times, there is a lack of components you need. Like with "Deferred complexity," the root cause of the problem lies in the nature of no-code—high-level abstraction. Easy to start, hard to scale. Easy to build a typical solution, hard to customize. Solution? There is no good solution. Just before committing to some no-code tool, learn its limitations. Maybe this particular one is not a good fit for your case. And you need to go around to find something better for your goals.

Adding or modify features in your codebase is better to keep thing simple and DRY. When writing test is more compelling repeated code per test, since it got everything at glance. https://lnkd.in/dpiHHCtA Personal notes : https://lnkd.in/dinZ7pu4 . . . . . . . . #infrastructure #ui #business #development #react #vite #playwright #web #enterprise #scalability #scale