# 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 11
# self = https://watcher.sour.is/conv/palzduq
movq
www.uninformativ.de
View Thread
@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
www.uninformativ.de
View Thread
@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
www.uninformativ.de
View Thread
@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
www.uninformativ.de
View Thread
@crunched I’m not really sure I understand the question. 🤔 😅

Here’s a hypothetical example. Let’s say you’ve written a little blog software in Python/Django. You’ve never actually used that software to drive your blog, though, you still use Wordpress. I’d call this a “practice project”. It’s only 20-30% interesting to me, because we can’t talk about how your program evolved:

- Why did you choose Python as a language and Django as a framework? Do you have prior experience in that area? What did you use before?
- Have you hit any major obstacles while writing your program? Which ones?
- Did you have to refactor parts of it?
- Did you run into performance issues?
- In this case, it’s software that runs on a public server (a public blog), so how about security? (Like, if that blog has an admin area, we can talk about how you prevent other people from accessing that …)
- Is there a test suite?
- Did you use any “project planning tools” or methodoligy? (To me, personally, it’s not really important to follow a particular method, but it’s still an interesting topic.)

And so on. You can only answer any of that if it’s an *actual program that you use* (and not just a practice project).

Is that … does that answer your question? 😅
movq
www.uninformativ.de
View Thread
@crunched I’m not really sure I understand the question. 🤔 😅

Here’s a hypothetical example. Let’s say you’ve written a little blog software in Python/Django. You’ve never actually used that software to drive your blog, though, you still use Wordpress. I’d call this a “practice project”. It’s only 20-30% interesting to me, because we can’t talk about how your program evolved:

- Why did you choose Python as a language and Django as a framework? Do you have prior experience in that area? What did you use before?
- Have you hit any major obstacles while writing your program? Which ones?
- Did you have to refactor parts of it?
- Did you run into performance issues?
- In this case, it’s software that runs on a public server (a public blog), so how about security? (Like, if that blog has an admin area, we can talk about how you prevent other people from accessing that …)
- Is there a test suite?
- Did you use any “project planning tools” or methodoligy? (To me, personally, it’s not really important to follow a particular method, but it’s still an interesting topic.)

And so on. You can only answer any of that if it’s an *actual program that you use* (and not just a practice project).

Is that … does that answer your question? 😅
movq
www.uninformativ.de
View Thread
@crunched I’m not really sure I understand the question. 🤔 😅

Here’s a hypothetical example. Let’s say you’ve written a little blog software in Python/Django. You’ve never actually used that software to drive your blog, though, you still use Wordpress. I’d call this a “practice project”. It’s only 20-30% interesting to me, because we can’t talk about how your program evolved:

- Why did you choose Python as a language and Django as a framework? Do you have prior experience in that area? What did you use before?
- Have you hit any major obstacles while writing your program? Which ones?
- Did you have to refactor parts of it?
- Did you run into performance issues?
- In this case, it’s software that runs on a public server (a public blog), so how about security? (Like, if that blog has an admin area, we can talk about how you prevent other people from accessing that …)
- Is there a test suite?
- Did you use any “project planning tools” or methodoligy? (To me, personally, it’s not really important to follow a particular method, but it’s still an interesting topic.)

And so on. You can only answer any of that if it’s an *actual program that you use* (and not just a practice project).

Is that … does that answer your question? 😅
movq
www.uninformativ.de
View Thread
Actually, let me rephrase that a bit: That’s not a standard set of questions that we ask our candidates. I actually had to think for a while to come up with these specific questions. 😅 The point is: You can talk about that stuff *naturally* when you talk about a real project that you wrote and that you really use. And this conversion then tells us a lot about how you work.
movq
www.uninformativ.de
View Thread
Actually, let me rephrase that a bit: That’s not a standard set of questions that we ask our candidates. I actually had to think for a while to come up with these specific questions. 😅 The point is: You can talk about that stuff *naturally* when you talk about a real project that you wrote and that you really use. And this conversion then tells us a lot about how you work.
movq
www.uninformativ.de
View Thread
Actually, let me rephrase that a bit: That’s not a standard set of questions that we ask our candidates. I actually had to think for a while to come up with these specific questions. 😅 The point is: You can talk about that stuff *naturally* when you talk about a real project that you wrote and that you really use. And this conversion then tells us a lot about how you work.
prologic
twtxt.net
View Thread
@movq's point is spot on. this is why it's so important to "dogfood" or "drink your own kool aid" (similar expressions) when writing a piece of software, or building a product. There is nothing more important that being a user yourself.

There are other things that are quite important too, like fail fast, fail early. But I won't go into that too much here 😅
prologic
twtxt.net
View Thread
@movq's point is spot on. this is why it's so important to "dogfood" or "drink your own kool aid" (similar expressions) when writing a piece of software, or building a product. There is nothing more important that being a user yourself.

There are other things that are quite important too, like fail fast, fail early. But I won't go into that too much here 😅