andrelgomes

I am not convinced of the validity of using scorecards to interview candidates. I understand it attempts to put quantitative aspects to subjective interviewing, but scoring is subjective so the foundation of this system seems flawed. My concern is the consequence of relying on the "data" and unable to convince the team that the highest rated candidate is actually not the best choice.

Any find success in this? Alternatives? If do use scorecards, things one should now? Most resources online are from HR and not the software team perspective.

Any advice for building a office server* for a small company (10 people)? Main use would be backups of files vital to our business but hope to setup redundancies as well. Also cannot complain to run internal intensive computation test. Any stories, obstacles, things not to overlook would be appreciated.

*I know there may be some thoughts on the waste, resources, needed for in house server compared to cloud but we need/obligated to have an in-office server for backups in general. We do have cloud services.

Looking for insights mostly on smaller companies (3-50)with internal software applications with a focus on onboarding new junior devs?

We have three applications, 2 web client and 1 backend. Initally, I am setting training now with a walk through our documentation at a high level but show them where to find more in-depth knowledge is located in docs, setup peprsonal environment, and do a simple task so that we can go through the whole process of developing, testing and deploying to production.

I am trying to implement Cybersecurity within our company. Beyond news articles of corporate hacks and anecdotal stories, are there any resources, scientific articles that show numbers/stats of the dangers of weak security. Trying to make a compelling case of why we should invest in practices now vs feature-product development (we are a small company so we have small bandwidth).

Also I am not just thinking software changes like backend throttling, best encryption method to use, but enforcing password managers, password generators, phishing protection.

We are moving to a new office and the software team (only me right now) are getting our own room - closed from the open office where the rest of the team is. I am fine with an enclosed space but we are getting new software team members and interns in the summer and I do not want them coming in a complete white room. Any ideas or inspiration from your office plans? Plants? Artwork? DIY cool lights?

Specs: 171 sq ft^2 (enough for 3-4 engineers) the entire office space is 1600 sq feet No windows