# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 6
# self = https://watcher.sour.is/conv/rrxrx4q
@crunched The company that I work for might not be the best example (because we do a lot of things differently), but we hardly care about formal education or certificates. Some of our best employees have literally zero formal education in their field (devs, admins), many others have just the bare minimum. Only a tiny amount of people has a University’s degree. We instead care a lot more about what a person has actually *done* in the past – and this includes their spare time. In the absolute best case scenario, a candidate can show us their Git repos: Real code that they have written. We can then talk about that code and discuss it with the candidate in their interview. This (reading the code *and* talking about it with the candidate) tells us a lot more about the actual skillset and mindset of that person than any formal education ever could.
I guess it’s very different when you apply for jobs at really big companies. They get so many applications that you’re probably dismissed automatically if you don’t have certs. (The question is: Do you want to work at such a company?)
@crunched The company that I work for might not be the best example (because we do a lot of things differently), but we hardly care about formal education or certificates. Some of our best employees have literally zero formal education in their field (devs, admins), many others have just the bare minimum. Only a tiny amount of people has a University’s degree. We instead care a lot more about what a person has actually *done* in the past – and this includes their spare time. In the absolute best case scenario, a candidate can show us their Git repos: Real code that they have written. We can then talk about that code and discuss it with the candidate in their interview. This (reading the code *and* talking about it with the candidate) tells us a lot more about the actual skillset and mindset of that person than any formal education ever could.
I guess it’s very different when you apply for jobs at really big companies. They get so many applications that you’re probably dismissed automatically if you don’t have certs. (The question is: Do you want to work at such a company?)
@crunched The company that I work for might not be the best example (because we do a lot of things differently), but we hardly care about formal education or certificates. Some of our best employees have literally zero formal education in their field (devs, admins), many others have just the bare minimum. Only a tiny amount of people has a University’s degree. We instead care a lot more about what a person has actually *done* in the past – and this includes their spare time. In the absolute best case scenario, a candidate can show us their Git repos: Real code that they have written. We can then talk about that code and discuss it with the candidate in their interview. This (reading the code *and* talking about it with the candidate) tells us a lot more about the actual skillset and mindset of that person than any formal education ever could.
I guess it’s very different when you apply for jobs at really big companies. They get so many applications that you’re probably dismissed automatically if you don’t have certs. (The question is: Do you want to work at such a company?)
@movq Absolutely right, that's exactly what we do, too. At least here in that project I'm involved in. We're having over a thousand employees, so I don't consider us a small company. We're looking at what the person has done before and then figure if that would somehow match what we're looking for. Since we're having all sorts of different projects we might also tell other projects to look at the candiate if we believe there's a better skill fit somewhere else. Actually having a look at their code and commits is usually only possible for hobby projects. Alternatively they might be tasked with a small programming exercise and then we also go over their result with them in the interviews. No certificate will ever reveal how they work or approach a problem. But I don't get to see all the applications, only the filtered candidates for our project, so I don't know how the first filter(s) work they had to overcome. However, from what I've seen it appears to me, that education and certificates are no dealbreakers at all.
@crunched Generally I find scratching an itch is the best way to go 👌
@crunched Generally I find scratching an itch is the best way to go 👌