Skip to main content

Pause the Bossy

 Always when comes in a tech industry, people put a show off with terminologies, hypes, jargon etc. Think if an eco system, where everything works honestly and just, no need of even talking "diplomatic", or no show offs.

The right person must be served just-fully.  They must get the remuneration in the standard, and those who are in the same category must not feel the regret or jealous in the same section unless for a knowledge gap.
So basically, when we create such a society where equal rights, and equal privileges prevail, there wont be any ego, and the community grows progressively.

If someone possess a bossy culture, if the management can't stop, it will harm the team, even the persons in actual life.




Comments

Post a Comment

Popular posts from this blog

Micro Front and ui frameworks

 To mix technologies in a micro front-end architecture, where different parts of the application use different frameworks or libraries, there are several ways to approach this, and the technologies you mentioned—Astro, Nuxt, Next, and Vite—can play a role. Here's how you can mix them, along with new approaches to micro front-end architecture:  Micro Front-End Architecture Overview Micro front-ends involve breaking a frontend application into smaller, independent pieces (micro-apps), where each micro-app can be developed, deployed, and maintained separately. These micro-apps can use different technologies (React, Angular, Vue, etc.) and are usually stitched together by a wrapper or container that manages the composition and communication between them.  Approaches to Micro Front-Ends with Modern Tech  1. Module Federation (Webpack 5)    - How it works: Module Federation allows multiple independent builds to dynamically share code. You can create different mic...
Post a Comment
Read more

Pain Points in Development

        When finding a solution to a real world problem, if it involves a software component, definitely starts a "pain" to the developers. The environment configuration, as is to the tech solution, then the logic, optimization, unit testing, integration, business verification, deployment in stage and prod, after all the actual scenarios  where mostly all the stake holders missed something. But at the end, the whole blame comes to the one who "codes" it. Yes, the pain of being a software engineer is not so easy especially in development. Apart from mental stress, on calls, after all the physique posture problems, long lasting health issue... But still its a passion :)
Post a Comment
Read more