There are preservation systems used by libraries that will continuously do what you're describing: https://www.archivematica.org/en/

Work on making people feel safe with the situation before asking for direct feedback.

A few examples of how this could be done:

  Give them more than a few weeks to get comfortable with you and the company culture.
  Give concrete examples of things that have improved due to employee feedback.

It's hard to offer better advice through a HN post but easy to observe in person. Perhaps you can hire an external consultant to help or ask a mentor or advisor to fill this role by spending a few days in your office.

Digirati | Software Engineer (PHP) | Glasgow (UK) | Full-Time | Onsite

We're a small (45 people) software engineering and UX consultancy with offices in Glasgow and London. We work in a variety of sectors but we've begun to focus on the Galleries, Libraries, Archives, and Museums (GLAM) sector in particular.

In addition to consulting we're building our own product call the digital libraries cloud services (DLCS), which makes use of a number of new standards such as IIF and open web annotations.

The interview process involves an initial phone screen, a broad quantitive technical test and a final qualitative "culture fit" interview. Time and availability permitting the 2nd and 3rd step can be done in a single visit.

Full details:

https://digirati.com/technology/our-solutions/digital-librar...

http://digirati.com/about/careers/php-software-engineer/

I don't have a suggestion for an aggregator but ...

I find Harvard Business Review to be my best source of management and leadership article, both the books they publish and the quarterly magazine.

Another source I like is Software Lead Weekly mailing list.

Make sure your acceptance criteria for the deliverables and definitions of done for each stage in your workflow are explicit.

In future design your hiring test filter out candidates who don't understand the bars for quality that you require.

If you want staff which are "switched on" and learn things like the above through observation you may need to pay more to hire better quality staff.

Theory of constraints.

https://en.wikipedia.org/wiki/Theory_of_constraints

how have you used it?

There's a number of excellent resources suggested in this post by others already so I wont repeat them.

One unique thing about becoming a PHP expert is the contempt you'll occasionally run into from others in the technology world.

Remember engineers get paid to solve problems for the business and success has very little to do with what the current flavour of "cool" is.

These are all valid points but many organisations are not at the level of maturity where the inputs to the engineering team are of the high quality you're describing.

Additionally there's an element of negotiation or dialogue around requirements which can often lead to cheaper/quicker to market/better solutions with input from engineering.

Both of these are much easier to do in person.

As a London based developer for BBCWW who grew up in Glasgow I can tell you this is definitely a good thing, the BBC is far too London centric.

Being in a similar situation to you I was grossly confused with Ruby until I ran update-alternatives, then things started to make more sense.