Some of these opinions are ones I don't really hold anymore so deleting isn't a big deal. I will admit that some of the ones I am deleting upset me because I still do think that way.
3 karma · joined August 19, 2025
Some of these opinions are ones I don't really hold anymore so deleting isn't a big deal. I will admit that some of the ones I am deleting upset me because I still do think that way.
The posts on LinkedIn should probably go too.
In my normal personal life I tend to be pretty sarcastic and self-deprecating. My therapist says it might be a defense mechanism to avoid actually confronting problems; if you make a person you're talking to laugh then they usually think everything is fine and stop worrying about you.
I try not to do that during interviews. I don't think I'm coming off like I'm trying hard to be smart or brag, but it's very possible and likely that some level of my normal insecurities are bleeding through, and that happening even subtly might be enough to poison it for me.
But when I get the technical questions correct and TLA+ seems to agree with me, that's where I get really confused. I'm not typically interviewing for management positions, I'm interviewing for engineering jobs.
I've always found it very irritating when I felt people were trying to force saying my name in a conversation, but I think you're probably right and I'm just a weird case.
Salary requirements are a valid point; in this most recent example my salary requirements were smack in the middle of the listed range so I don't think it was an issue for this particular one but it's possible that they feel I'm too expensive.
Dunno, it's just hard not to take this a bit personally sometimes. As I said, if I felt like I knew what I was screwing up, then that would be something I could work on. It's not hard to buy textbooks and learn more about concurrency theory or distributed systems or something, or to build a project on my server to play with a library, or something like that. It's extremely hard to solve a problem if you have no idea what the problem even is.
You're not wrong with anything you said though. I just need to keep applying and go from there.
I've never really had much of an issue saying what's on my mind, so I don't know that alcohol would really help me much, generally all alcohol does is make me louder and sleepy; according to my wife I don't really talk different when I'm drunk.
Before someone thinks I'm being cocky about me being right and them being wrong, after every interview involving concurrency I always write a PlusCal/TLA+ spec with my answer and use the model checker to make sure that my answer actually solved the problem correctly. This is why I can be confident that my answers were correct; I'm not smarter than anyone really, it's just that I try and verify my work.
The issue is not just this one company. I have been at this for months with similar stories for a lot of them.
Sometimes I get the technical questions wrong, so that's fair enough, I understand why they'd decline me for that and as I said that's something that I can at least work on for myself by reading through textbooks and/or building sample projects to understand a concept a bit better.
A lot of the time, though, I won't get the technical questions wrong, and it's this recurring thing of "I really don't know why I'm constantly being declined".
Mock interviews are a pretty good idea though.
And the slides are available here: [url-redacted]
I'm afraid that my humor isn't really reflected in the slides, but imagine everything here is said kind of snarkily.
Java can be mostly as nice as Go, the BlockingQueues and Virtual Threads can get you pretty far, though they're not quite as nice as Go channels because there's no real way to select across multiple BlockingQueues like you can with Go channels.
Overall though, I think Java 21 is actually not too bad. Shockingly, I even sometimes have fun writing it.
Here's what I sent:
Hello!
I don't have a lot to say to you, but I just wanted to say that about a month ago, I started the transition away from Google, and the most obvious thing to switch was search.
DuckDuckGo has improved substantially since the last time I used it (around 2012), and it's to a point where the results are comparable, and sometimes even better than Google, so changing was pretty seamless. Now the only Google-thing I need to remove from my life is YouTube.
As a somewhat technical person, I was curious about one thing; I saw that the primary language for DuckDuckGo is Perl. Without making any judgement here, was there a particular reason for that choice? Also, are you planning to move to Perl 6?
Anyway, I appreciate you reading my email. DuckDuckGo is a great service, and I hope you guys keep up the good work!
-Thomas Gebert.
Here was his response: Yes, though, the primary language is Perl. It was out of convenience and interest since that was my primary language when I started the project. There was/are a lot of libraries useful for text processing / web crawling. Now Python and other libraries have been similarly built up.I hear Raku is fun, I haven't used it, but I sort of swore a soft oath that I would never touch Perl again about a decade ago after having to debug some regex magic someone did. I'm assuming that once you get past the "hump", Perl becomes fun?
I've managed to pull it off somehow, but I rarely go a day where I don't wonder if I really should have as good of a job as I do.