Notes

I am one of those people who function better by writing things down. One day, I realized that most of my notes don’t have to be private, so here they are - my second brain. Be warned that, if you stumble upon something here that doesn’t make sense to you, it isn’t meant to!

Hung networking hardware in Proxmox

I one day woke up in the morning to the following error on my Proxmox server: Apr 20 00:06:20 pve kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Down Apr 20 00:06:20 pve kernel: vmbr0: port 1(eno1) entered disabled state Apr 20 00:06:23 pve kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Apr 20 00:06:23 pve kernel: vmbr0: port 1(eno1) entered blocking state Apr 20 00:06:23 pve kernel: vmbr0: port 1(eno1) entered forwarding state 2025-04-20T00:14:45.918353-07:00 pve kernel: [1789014.672581] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: After some digging, I added the following to the /etc/network/interfaces file. Haven’t seen that error again in at least a few months: ...

Break down of Staff+ role

Different aspects of the job: Project delivery. Big picture thinking. Could be both vision or strategy. Mentorship. Different skills they need: Technical skills. Product management. Project management. People skills: how to organize people to work as a team, grow their careers etc. Different archetypes, i.e. style of work they do: Team lead: usually a starting point for a Staff engineer, something they transition into from a senior engineering role. Architect. Solvers: usually present in teams that place more emphasis on individual contributions than on teams. Right hands: borrow power from and act as proxies for senior leadership.

How to approach the interviews

Speak slowly. Pause before you respond to anything. Story telling tips (for behavioral rounds): STAR technique - very important. In most cases, the technical details (of the situation or actions) don’t matter too much, so no need to delve into those unless cross-questioned. As for actions, try to answer in numbered bullet points: I did 3 things: One, … When asked a question, pause a few seconds and think what the actual underlying question is or what exactly the interviewer is looking for. For example, a binary question doesn’t need to be answered by a yes/no. Some behavioral questions require you to show how you collaborate. So, talk about 2-3 stakeholders you worked with to answer those. (Escalation should be the last resort: don’t bring it up unless absolutely required.) Phrases to use: One of my teams. But … therefore. (Conflict and context.) Don’t use and then. Drove alignment. Calculated risk. Build relationships with people. Build trust. I > we. I learnt XYZ from this engagement/project. I collaborated vs I told junior SDE to do X. Bring in engineering perspective by saying something like, I analyzed how the requirement would fit into our current architecture. Project retrospective: ...

Reverse interviewing

Questions to ask if I am talking to a medium sized company: How do you handle difficult decisions? Can you talk about a situation where you changed your company/product direction because of such discussions? What’s the long term vision? Or are you thinking of one?

Automatic disk decryption on Fedora Workstation

Note: See this for how I played with disk encryption for an external drive on my Raspberry Pi. I recently setup a Fedora machine and (obviously) enabled disk encryption on that. However, that meant that I had to enter a long passphrase every time I rebooted my computer and, in my setup, this was different from my user account. So, I wanted to enable automatic decryption if a USB drive was present during reboot. Plus, the system should fall back to passphrase if the drive weren’t present. ...

Official train websites in Italy

As of today, seems like the 2 official sites are: https://www.trenitalia.com/en.html https://www.italotreno.com/en

Fstab with special characters

I wanted to mount a Samba share to my (new) Fedora Workstation machine and that share had some special characters, a ' and a space. Escaping those wasn’t sufficient. Instead, I had to use Ascii octal codes. Here’s what worked in the /etc/fstab file: //10.0.1.179/Ketan\047s\040Drive /mnt/samba-at-home cifs credentials=/etc/samba/credentials,uid=1000,gid=1000 0 0 10.0.1.40:/var/nfs/shared/Backups/Fedora /mnt/backups-on-nas nfs defaults 0 0 Resources: https://askubuntu.com/a/1460762 https://www.asciitable.com/

Platforms for mock interviews

https://igotanoffer.com/ https://www.hellointerview.com/ https://interviewing.io/ Things to keep in mind: I feel these work well for people interviewing at an SDE-3 or Staff level roles. For more senior roles, such as Senior Staff or Principal, I couldn’t find suitable interviewers at least on the first website above.

Automate SOPS encryption in Git

Note: While the following worked, the entire setup felt fragile. Plus, I realized there was little point in encrypting the source code in my repository, given the repository is hosted locally on my home network where I already have encryption at rest. So, I reverted this stuff after trying it for a few days. Initial setup Ensure the Age private key is available in the right place (i.e. ~/.config/sops/age/keys.txt). Update .gitattributes in the repository to look something like this: ...

Feedback from mock interviews

I recently gave a few mock interviews. Here’s some feedback I got from those. 1/29: “User flow/experience”. Non-functional requirements. Scale explicitly. Latency. Get easier part and finish it as well. Can help put more boxes on the diagram. Trade offs: focus on that. Proactively find issues and try to get things right in at most 2 passes. 2/3: Capacity planning good. Don’t assume database is a black box - dig deeper. Non-functional requirements. Latency. Availability. Keep updating the diagram as you speak. 2/16 (behavioral): Use examples to answer generic questions. Ask questions for behavioral too. (Gives you time to think too.) Ask questions early. (Very important, and maybe early so that you don’t run out of time at the end.) People like to hear their your own voice. Do some research about the company beforehand. Can help you ask good questions as well. Roughly finish an answer in ~2 mins. (3 mins is too long.) 2/16 (behavioral): About yourself: You can tell about your background etc. so that you can build curiosity. For projects, talk about impact. And what did you learn. Moving fast. Measurable business impact. Scalability. What you learnt: add to every answer. Collaboration important as well. We vs I. Need more direct conflict stories. Co-worker, manager, etc. didn’t agree with me. 2/17 (project retrospective): Dog feeding. Think of metrics. TPS. CSAT. Done better: Lack of expertise == lack of technical gap. “Better job in covering our technical gaps.” Architecture: More complex. Need to speak for 45 mins. Scalability in everything. Use PM, TPM in your stories. 2/19 (behavioral): Shoot for ~3 mins. Story: STAR-L format. L == learning. A -> bullet points.