I'm redoing how we do technical interviews at JLR in US. I'm interested in horror stories, things that you liked, things you didn't like, things that sounded good on paper but didn't work. This would be specifically for software development -- code, any code, at any level.
I'm also looking for inclusive interviewing practices to avoid implicit biases during this process as well.
Toot back at me and let me know!
I had an interesting project that I'm pretty happy about the result:
When a software application must have a master node (and consequently is a pet, and not cattle) how does one turn it back into cattle with a forced leader election?
For the solution, I used consul-template with ansible. The nodes look at the consul KV and compare that to the nodes in the service discovery component. If the server isn't there, there is a race to lock the KV record. The winner reconfigures itself with ansible.
Welcome all the new people, since this is the thing to do, I too shall do the thing.
I'm one of the Lead DevOps Engineers over at Jaguar Land Rover. I write software that helps people write software faster. We utilize a lot of open source tools and so part of my function is to endorse these tools both within and without the company.
I'm also a Brazilian Jiu Jitsu purple belt.
I've seen a few more advertising accounts on mastodon.technology and have updated the Code of Conduct to explicitly forbid advertising.
The Code of Conduct is available here: https://mastodon.technology/about/more . If you see a toot that you're not sure about, please err on the side of reporting it and I can follow up with next steps.
If you have questions or concerns, just let me know. I'm always here to clarify anything. Take care!
Damn tech #recruiters are annoying!
"Hello, would you like a great opportunity as 3 month contract position for a jr help desk role?"
... I'm an FTE and lead with over 20 years experience. Why in the world would I want that? 🤔
At least look at my title first before messaging me on linkedin.