Hansi

As a middle manager I can confirm, I have a certain set of standard interview processes I apply but if the candidate is warranted to ask for an alternative approach to assess their skills in condensed time I can accommodate those situations too. Simply asking directly is most likely the best approach, suggesting a route is likely fastest to get an answer e.g. instead of 4x1hr can we do 1x1.5-2hr and reference your code for them to measure your skills overall.

In your country/social group. Messanger has a bigger footprint than WhatsApp in some of my social groups in Europe.

Check the other comments on the link? Solution c) is already there?

I thought about stopping but decided to keep reading. I'm not sure these guys know what ETL Tooling means, some of the entries were just bespoke R script only packages that just extract data into R.

+1 RedHat 7 and 8.

Might be location specific but out of 300+ candidates for 15 positions mid to senior level over 8 years in London recruited using this technique I've only ever had one person turn it down. We ask for fairly simpler requirements and for people to limit themselves to 4-6 hours over the course of a week with a focus on comments and recording their thoughts in a readme to suggest how they'd scale things if it was a real project. We don't really bother with many technical questions outside of the project anymore. It really is the single most important thing to get a glimpse into a persons ability to deliver, let them code at their own time in a setting they are comfortable with and then do a peer review with them on location and discuss the implementation and potential enhancements. The rest after that is generally just team fit and culture alignment checks.

I'm a bit of a outsider looking in being a manager that doesn't code much anymore but why the dislike of Typescript? I really don't see the downside. Transpiling doesn't make it 1:1 anymore but all devs seem to praise it.

I find breaking in two as a bunch convenient since it makes it slightly easier to manage lengths. I do smaller for my daughter (2yo) since she struggles with scooping up the long ones on her own but is fine with smaller bits.

The lack of an ISO is a bit anti-enterprise I feel. Working in a bank with firewalls that flag a lot of stuff as false positive blocked items using the builder is problematic. The 2015 ISOs solved a lot of issues for us in terms of building a deployment via SCCM. I'm getting a headache just thinking about trying to get pulling hundreds of packaged executables through the firewall signed off by IT Security.

I feel an ISO including only standard packages from Microsoft itself would solve a lot of issues.

Layout is really crappy around blocked files or corporate firewalls. It feels untested in anything other than a completely open environment because some of the package downloads can fail silently with a fuzzy enterprise proxy. Creating layouts for patches seems dependant on what direction the wind is blowing, I think 2015 Update 3 took about 4 tries to download everything correctly and only way to verify was reading through the logs. Also that one needed a random Windows KB update on Windows 7 which was extra fun.

Better handling for layout around error handling and validation of downloads would be a boon. It would be great if there was a way of verifying an already created layout. Is there any way?