I have a personal checklist I go by before I publish anything to a community repository like NPM. I've followed in the past for Nuget and other private repositories too. For example I've posted libraries to internal organization repositories and it's a good idea to follow many of the same checklist items. Continuous integration is setup for the particular library that needs to be published. The library has a good build, and only on a good build a trigger will deploy specific tagged versions to the repository. i.e. If the build is tagged "v1.x.y" where x and y are valid version increments set for release. The library is used by myself, if publishing personally, or "dogfooded" by the team building it within an organization. It has to have docs, a clear site that states what that library is for and how to use it. Ideally with as minimal and simple of steps that can be put together. Basically, I ensure that there are certain gates the library must be moved through before I post the library. Otherwise it simply doesn't get published until it can meet the requirements to pass through those gates.

"Hiring should be always on the skill basis." then the future is ill planned for, as software development isn't a job like "use X crane" but one of thinking and problem solving. If a company hires for skills only they've short sold themselves and their future hiring will go down the drain. A company has to act strategically and not with such a myopic focus. "Not on minority, majority, women, disability political correctness crap." One doesn't have to set quotas or the like to make this happen, they just have to get rid of their misguided viewpoints, understand their actual pool of hiring, and realize who actually is and isn't a good hire. The data is there, people have to pull their bigoted viewpoints out of their proverbial ass and realign with some actual reality. There's dramatically more opportunity and profit to be made when a company realizes this and lifts its employees up in the process of profiting. "Get things done. Business should be about profit, not charity." Exactly, which is why having a skills only based viewpoint is short selling one's company, and very likely (as so many startups can prove out) setting up a company for failure. "Don't play hero of equality and inclusiveness. That is going to destroy more companies and the talent than anything." The data on companies and hiring already show this to be false.

The first problem with this question is that nobody is 100% introverted or extroverted. Once one fixes that then such a disheveled question doesn't need to be asked. Effective programmers are defined by characteristics, not by a single characteristic but of many. Starting with the broken paradigm of introverted or extroverted only with a Boolean answer as a result just bides more bad notions.

A person simply shouldn't sit for any period of 8 hours. That's asking for all sorts of health problems. One should get up regularly and stretch, walk around, get some water, and generally take a deep breath or three. Our bodies need that, they really weren't designed to be sitting for 8 hours, or doing a single activity of any sort for 8 hours. It's really bad for one's health to do something like that over and over. :)

~6 hour work day is reasonable, and most people can actually give 100% then. Anything over that and the motivation to push harder really just plummets. Especially working for a corporate enterprise or something that is just a "job". But often one can push those hours a little bit if they're super motivated over something, but even then that starts to turn into burn out at a pretty quick pace. Usually it only takes about 6-12 months for someone to really have the burn out kick in and the apathy just builds up until they're giving about 20% for an 8 hour day, mostly sitting around and twiddling their thumbs while chatting around the water cooler. Simply, keep the work day to about 6 hours and things are remarkably better for everybody involved over the long term. :)

Hello all! My name is Adron Hall. Glad to have joined the Hashnode Community, as I'd finally stumbled into good material here enough that I decided to go ahead and sign up. The first time even gave me inspiration to start writing up some descriptions of how long one codes during a coding session . I’m a jovial, proactive, test & code, code & test, get things done well, software architect, engineer, code monkey, coder, and distributed systems advocate. But I'll be posting more technical content - some from my blog but I'll also be contributing to conversations and some Hashnode specific content too, so hopefully some of you will find that useful. Besides all that technology stuff, I dig some good coffee, great beer, wine, food and a good music show. I cycle, almost everywhere these days, don’t own a car (but I’m a car snob of the serious racing sort auto-x, tuners, drift, rally, etc), I verge on the “transit nerd” and “rail nut” category along with “plane spotter” and “exotic car driver”. I also play guitar – primarily thrashing (metal), love to prog with some Jazz, croon along with some blues, and delve into a range of musical nuances. …and I’m sure that misses a few things, but I think it gives a good overview of where you’d usually find my mind and I. I'm also Adron on Twitter and Github , and a number of other places. Glad to be here, looking forward to checking out more material, connecting with people, and contributing back. Cheers!