HN user

lmarcos

894 karma
Posts5
Comments315
View on HN

Agree. Interviews taken into account side projects are biased towards:

- people who have free time to work on side projects (usually young people have more free time than people with families)

- people who don't mind sharing their code with others

- people who work on interesting side projects. If your side project is boring, that will probably bore your interviewers -> no offer

- people who work on side projects on regular basis. If I get to work on one side project every year, well, chances are I may have forgotten the hell I did on that project (depending when the interview takes place). If I work on side projects constantly, I have no trouble picking up a fresh one to talk about

As someone not familiarized with background checks, why is it weird to do bg checks after handing the offer?

If the employer does the bg check before handing the offer, that means the candidate hasn't resigned yet from their current job. So wouldn't the bg check expose the candidate? (E.g., my boss would know I'm thinking about leaving)

I'm the only one still listening mp3s? I have a sandisk mp3 player (size similar to the classic ipod shuffle) and I use yandex to get the mp3s. And I transferred all my old CDs to mp3 format as well.

I don't use my smartphone to listen to music because it's too big/heavy (running with it is so uncomfortable).

They tried that, but they couldn't because:

- my contract says the place of work is city X

- they don't have an office in city X

- they cannot unilaterally change the contract (Europe)

They asked me if I would be willing to relocate to a city in which they have an office. I declined. I'm still working from home. The company is big, so they don't care much about isolated cases like mine.

For Spanish speakers who know English, reading Don Quixote in English is probably easier (and more pleasant). The Spanish one is full of words that even though a native speaker can understand (with footnotes sometimes), it's just not as pleasant as reading modern Spanish.

Same. I always work on any given (hard enough) problem twice or three times. The first time I come up with some kind of prototype that may work or not, but it gives me foundation to work on the second prototype. The second one tells me how a final working and performant solution could look like, so I discard it and start from scratch. At the end I come up with the best possible solution I can provide. Sometimes it takes fewer steps, sometimes more. And more often than not I let some time pass between attempts (maybe I go for a walk in between or I let a full day pass to work on something else).

At interviews they stop me at my first attempt.

The dragon book is a theoretical book. It's like any other (good) OS book out there: good source of information to know the foundations. After reading it, go out and read something more practical (which you probably won't have issues learning it since you now know the foundations)

I believe knowing their data-structures and algorithms is the difference between an okay programmer and a good one

For me, the difference between and okay programmer and a good one is: how much Linux/Unix they know (processes, core system calls, networking, sockets, awk/sed/bash). Whether you are writing apis for ecommerce platforms or writing custom k8s providers, Linux knowledge is a must. Knowing how to implement a trie? I bet most of us have never been in that situation.

But even if the job actually requires solving puzzles like that one, what's the point of asking the candidate to solve it in 45 min? Without googling? That's what it's actually totally unrealistic.

Give me any problem related to algorithms+ds to be solved in 45mins without internet access and someone looking over my shoulder and I will give you a poor solution. But give me a day and internet connection and I will solve the problem in the most efficient/readable/maintainable way possible.

I think one disadvantage of putting everything (nginx, web server, database, monitoring tools, etc.) in one machine is that suddenly your machine is exposing a myriad of ports to the internet and one mistake on your side (e.g., misconfigured auth module) is all what's needed to compromise your entire service.

Having some sort of vpc where you can safely put your db server that only listens to requests from servers within the same vpc (e.g., web server) sounds like good practice to me.

I love painting. I paint landscapes in my free time. Tons of them. I love my career: being a painter.

No one pays me for painting landscapes, so I work for company Paint Inc where I paint portraits. They pay good money since I'm very good at painting. I don't really like painting portraits. It's okeish. I don't hate it either. I take it as a job. No more nor less.

Now, do you wanna meet up to paint landscapes? I pay the drinks!

I can easily scroll down through Google search ads. With Bing chat, I would have to type many times "next please" and wait each time for the response. Seems like a step back when it comes to searching the web.

"Poorly" (in quotes because it's a relative term) written codebases are the best:

- tons of opportunities to improve things!

- fixing bugs is like being Sherlock Holmes. I enjoy that

- and the best is: if you need to deliver something that has a deadline and you couldn't make it, you can always blame the "poorly" written codebase