Certainly situational but I will share some of my experience and it regards the concept of "Seniority" of an engineer. When having a goal --> Multi-tasking can be bad In most cases, you will be tasked with something specific that you need to complete. As humans, are brains are drawn to distractions like bees to honey. What happens then is you deviate from you single goal of the day/week/month and the actual output you have is effectively decreased. That also goes for the quality of your work. As a Senior --> Multi-tasking is probably required Seniority as I have experienced it being the most effective, except for the excellent technical competency, entails the concept of "being able to enable" as many people as possible. Either that be: Solving an issue between Dev & QA Getting new ideas into the table ( Technical or Product-oriented ) Enabling Marketing doing their job X times faster by teaching/showing them some automation capabilities etc. Times and times again this might come into people as "Imposter Syndrome", because they are successful in their job, by just being there, enabling and giving their technical edge. Nothing more, which is great!

Hey Nishant Mittal I have used Eleventy for development and article management and I could not be happier. Markdown for the content Nunjucks for special tagging/snippets Building with community based plugins (Styling and theming was custom made by myself so I don't know of the ready-made options) For hosting, Netlify all the way! I bought a custom domain from GoDaddy and the integration was fast and seemless. If this for a client, the discussion has many variables that are highly dependent of context. For another time :P Cheers!

Hey Edidiong Asikpo :) This is pretty common to question yourself. People going through school, are most probably never taught the "right" way to write and when the time comes, are feeling inadequate. Which is totally wrong. Nobody mentions that writing as any other "craft" is multi-faceted and can have as many contexts as there are people. So, experiment, release your articles and be open to feedback, you will get better by it in time. I have been doing technical development editing for more than one global software engineering book companies for years and I am still learning. If you are into tech-writing, Google has released some good courses with nice directives https://developers.google.com/tech-writing Cheers!

Hey everyone! Really happy to be a member of this community! I am Peter and I will be representing my website " The Home of Web Automation " As it is expected I will be posting my own recipes, thoughts and techniques about things like Web automation tools End to End testing QA practises & strategy etc... The difference that I want to make is with the way the content is presented. I have tried to differentiate a bit from all the other hubs of software related content. My aim is to open the page of the post or the actual website and feel joy that you are there. No need to rush, no need to take everything so seriously but with great professional content. Thanks again for this community being here and if you want to learn more about the mission, take a shot at the about page . I would really like if you comment or message me and request a post about a tool or methodology you want to get more info about and I will try my best to get this up :) Best, Peter