Seve Kim’s Post

Platforms and portals aren’t created for developers. They’re created for managers. They don’t address technical problems, they address organizational problems. They sooner platform teams realize that the sooner they’ll build better solutions. For devs and managers.

People want their problems to be solved, not your tools to be used. If you build things because you like technology, you probably build for a different customer than you originally anticipated: yourself! That's not necessarily a problem though. Especially long-term commitment to a product and sustainability of working with its codebase become easier if you write one or two user stories with yourself as the persona. Developer quality of life is an objective you’re allowed to follow. 🤓 Just be honest and transparent about it (to yourself and stakeholders). Because in the end, people want their problems to be solved, not your tools to be used.

Definitively I would dislike to get disrupted by yet another new tool but developers always have centers of gravity in which they look for context. Usual centers of gravity are CI/CD servers (they give me context of the status of my software), project management dashboards (they give me context of my WIP). The missing center of gravity is something that can give me context of my own work and all the tools I need to operate. For example, I am 99% sure that most of us whenever we start on a team we get a list of links of the tools used e.g. the URLs of our CI/CD server, the observability dashboard, the git repositories, HR portals, etc. Developer portals contextualize the above links to my context i.e. instead of giving me the URL of the CI/CD server, they could provide the URL of all the pipelines that my team uses day to day.

Have you ever worked or built a 12-factor app? The 12-factor app methodology is a set of best practices for building modern software applications that are scalable, maintainable, and easily deployable. It was originally introduced by Heroku and has since become a widely adopted standard in the software development community. The 12 factors are as follows: 1. Codebase: A single codebase tracked in a version control system, with multiple deployments. 2. Dependencies: Explicitly declare and isolate dependencies. Use dependency management tools. 3. Config: Store configuration in the environment, separate from the code. 4. Backing services: Treat backing services (databases, caches, etc.) as attached resources that can be easily swapped. 5. Build, release, run: Strictly separate the build, release, and run stages of the application lifecycle. 6. Processes: Run the application as one or more stateless processes. 7. Port binding: Export services via port binding. Applications should be self-contained and not rely on runtime injection of a web server. 8. Concurrency: Scale out via the process model. Applications should be able to scale horizontally. 9. Disposability: Maximize robustness with fast startup and graceful shutdown. Processes should be able to start and stop quickly. 10. Dev/Prod parity: Keep development, staging, and production environments as similar as possible. 11. Logs: Treat logs as event streams and provide centralized logging. Application should not concern itself with routing or storage of its output stream. 12. Admin processes: Run admin/management tasks as one-off processes. They should be run in the same environment as the app, with access to the same config and code. By following these principles, developers can create applications that are easier to develop, test, deploy, and scale, while also improving the overall reliability and maintainability of the software. 📌 Follow Dinesh Varyani for more such content. #softwaredevelopment #community #management #development #startup #event #software #environment

Minimizing Frontend Updates: A Strategic Approach in Software Development Today, let's delve into a strategic aspect of software development: the practice of minimizing front-end updates. 🔷 The Case for a Stable Frontend: Think of the frontend as the user's window into your digital world. But why is it sometimes wise to keep this window unchanged? 🛠 Empowering the Backend: Behind the scenes, the backend serves as the engine powering your digital presence. By enabling it to adapt to changing requirements, we establish a robust technical foundation. So, why prioritize a stable frontend? 1. Deployment Efficiency: A stable frontend means infrequent code updates, streamlining deployment processes. 2. User Confidence: Consistency in the frontend experience fosters user trust. 3. Development Streamlining: Fewer frontend changes simplify development workflows and maintenance. 4. User Experience Focus: Teams can concentrate their efforts on perfecting the user experience, knowing that the frontend remains constant. 5. Business Agility: The backend can respond promptly to market shifts while preserving the familiar user interface. This approach is about minimizing disruption, not diminishing the frontend's importance. It exemplifies efficient software development that benefits both users and development teams. #reactjs #frontenddeveloper #softwaredevelopment #frontend #deployment #strategicplanning

👋 Hello LinkedIn Community, Performance in software development can make or break an application with just one line of change. Sometimes, to improve performance, you might have to rewrite an entire application, but other times, small changes can make a big difference. As developers and companies, it’s important to think about the different backgrounds that users come from and what technologies they might be using to access your products. Performance can make a big difference between gaining a user or losing a user. If the application is not performing, is not responsive, or is not fast enough, then people will not use it. Performance is usually something that is built incrementally and is achieved by making incremental changes. It’s an underlying part of the application that without it, you can’t really have the applications. One of the things that React does really well is that it’s very efficient in building and rendering web applications. React localizes the change such that if you need to change a small text, you can only have the work for training that small text instead of having to rewrite the entire page. Look for bottlenecks and then dive deeper into this and see why is this component so slow? Why is it taking so long? How can you refactor this component to make it faster? Maybe you can delegate some of the computation to the back-end so that you’re not incurring this cost on the user on the front-end. In order to achieve performance and usability, there are certain design patterns and well-established approaches that engineers have developed over time that have known to work really well and increase the performance of applications. Like using memoization or delegating part of the processing to the back-end. I encourage you to look for those and find ways that you can introduce these design patterns in your application. #React #FrontendDevelopment #SoftwarePerformance

An interesting but obvious observation in software development is that what might be good for the frontend may not be good for the backend, and vice versa. In this regard, development teams often need to align on putting product-level decisions ahead of their technical views; issues like user experience may have to be prioritized over performance in times where both share conflicting requirements. #frontend #softwaredevelopment #userexperience

Key Advantages of React seamless state management: Effortless Integration: Seamlessly integrate state management solutions into your React components, reducing unnecessary complexity and enhancing code maintainability. Enhanced Performance: Optimize your application's performance by adopting efficient state management practices, ensuring smooth and responsive user experiences. Improved Developer Experience: Enjoy a more gratifying development journey with reduced debugging efforts and increased productivity. Spend less time wrestling with state-related issues and more time crafting exceptional features. Scalability: From small-scale projects to enterprise-level applications, seamless state management adapts to your project's requirements, providing scalability and reliability at every stage of development. #webdevelopment #webdev #webdeveloper #webdevelopers

Are you eager to explore the vast possibilities of our cutting-edge developer portal? 🌐💡  We are thrilled to announce the release of an informative video that will take you on a deep dive into our developer portal's remarkable features and functionalities. 🎉✨ Feel free to like, comment, and share this post with your fellow developers.🌟💼 To watch this exclusive video, simply click the link below. 👇🔗 #DeveloperPortal  #API #DeveloperCommunity #CodingJourney #Innovation #Growth #technicalwriting #developerportal #developers #websitedevelopment #developer #comment #comment #share #video #like

🚀 Overview of State Management in Software Development! 🌐 Just dropped a must-read for all tech enthusiasts and developers! 🌟 Discover the ins and outs of state management - from its core principles to the hottest libraries. Why is it a game-changer? How does it revolutionize app development? Find answers and more in my latest piece. Perfect for anyone looking to enhance their software development skills! 🔗 Dive in now https://lnkd.in/dUQRmuCa and let's elevate our coding journey together! 💻✨ #statemanagement #softwaredevelopment #techtrends #innovation #developercommunity #redux #vuex #bloc #ngrx #reactjs #reactnative #flutter #angular #frontend #contextapi #mobx