Skip to main content

Bias (the team)

In software development, micromanagement and favoritism can suppress creativity and reduce team morale, often fueled by office politics. These practices can lead to unequal opportunities and a toxic work environment, undermining productivity and innovation.

Revisit the software development process.



In reality, we do waterfall in each module or sprint๐Ÿ˜Š

Agile basically comes into picture when the initial phase of the project is delivered.

In an ongoing process after post production, agile is the way. 

Scrum doesn't actually needed as jargon, but an initial meeting alternate standup, review are enough and will be a part.

Only draw back is show casing individuals suppressing the team is worse.๐Ÿ˜‚

The lowering or low branding of team members in the standup even by a gesture word, email all affects the productivity.

The actual team is mostly rejected in tech meetings, or no access to management even once in 2 months, are lose points.

The opinions or technical aspects are avoided and neglected for the sake of office politics is another issue.

So who is the asshole?


While Agile can improve post-production work, micromanagement and favoritism hurt team unity and output. Ignoring team input and sidelining members in meetings worsen these problems, damaging creativity and morale.

In Agile software development, where suppression, favoritism, and office politics often prevail, patience is essential. Burnout and frustration can exhaust us, but patience helps us persevere. Despite the mental toll of arrogance and favoritism, patience enables us to move forward, fostering team growth and stability in a challenging environment.

Comments

Popular posts from this blog

Discrepancies in Corporate Morality

 Major corporations often launch pride campaigns, yet fail to align with ethical obligations, sometimes contradicting their stance by ignoring human rights violations worldwide. This discrepancy undermines their claim to honest and ethical morality.  Pride Campaigns and Ethical Obligations!

ChatGPT is not alone

 The tech industry is celebrating ChatGPT as new language processing AI. But there is not much music for those who worked behind the technology. Even it's not a single achievement. We humans are always forget to thank or show gratitude ๐Ÿ˜Š. ChatGPT or even any technology wouldn't be a reality, if the previous generation paved the way to achieve it. Means, it's a series of discoveries and inventions, for a better life. When the tech is developed, frankly, after a short time, it moved into the list of "profitable business" traps. All industries, as said earlier trying to provide the humans an easy and better work life balance. https://globalwomanmagazine.com/mira-murati-the-albanian-woman-who-developed-chatgpt/?fbclid=IwAR3ps6zYYL4Nk04GiSI2vMvoe-MVzBoNlb_QatVGiMTXegEQcXE-aCBfDt8

Ui vs api

 In a data-rich engineering web app where GraphQL is used for data retrieval, the time ratio between API development and UI development can vary based on several factors: 1. Data Complexity:If the data structures are complex or have varying relationships, more time might be spent on API development to ensure efficient querying and data retrieval. 2. UI Customization Needs: When the UI requires extensive customization for each section or table, additional time might be allocated to UI development to ensure each component meets specific requirements. 3. Integration Challenges:Bridging the gap between the GraphQL responses and UI components, especially in scenarios where components cannot be easily reused, can significantly impact the time spent on integration efforts. 4. Functionality and User Interactions: If the application involves complex user interactions, form handling, validations, or real-time updates, a considerable amount of time may be dedicated to implementing these featu...