Notes

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/

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.

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: ...

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.

Similar to earlier, I was looking at enterprise servers again. Primarily, R730 or R730XDs. Some notes from that: Don’t get hardware RAID controller as it has bugs. Don’t expect NVMe for booting OS. If you set it to ‘off’ by the ‘Fanspeed offset’, and you enable ‘Maximum exhaust temperature limit: Default (70c)’, it runs really quiet and you can use a fanscript to dail it back even more. Resources to manage fan speed/noise: ...

Scope (of my role at current organization). About me, as an individual: Strengths. Growth areas, in terms of technical skills. Growth areas, in terms of leadership skills. Feedback that surprised you. What inspires me. What drains me. Leadership skills: Conflict with teammate. (Could be an example where you changed your mind.) Conflict with cross-functional team. Conflict with a partner/cross-organization team. Engagement with a partner team that went well. Engagement with a partner team that didn’t go well. Gave feedback to a peer or junior. Handle shift in priorities from leadership. Best mentorship relationship. Situation where you needed crisp communication. Acted in a tense/ambiguous situation where you didn’t have enough data. Some cross-function partner or someone from another organization wasn’t performing well. Manager specific: What do you look for in your manager? Feedback to upper management. Conflict with manager == feedback to manager. Project retrospective (for one large project): What would you do differently if re-starting from scratch? Technical and organizational challenges. (Not the same as trade off.) Technical trade off. Business trade off. Biggest: Technical problem == road block. Risk that paid off == decision that went against popular opinion. Failure == risk that didn’t pay off as expected. Operational event. Operational process you setup. Short-term vs long-term trade off. Something you did for the team that you are proud of.

This time, we flew into and out of Delhi to save costs and that was tiring. Especially flying out because, 1st day, we left Ahmedabad at 8 am and, 2nd day, at 4 am for Seattle, so we couldn’t sleep properly for 2 consecutive nights. The Dubai to Seattle leg felt long, so maybe try flying to through another city. So, a flight that reaches Ahmedabad in a single hop but divides the two legs somewhat equally. Bring a meal or two for when we return home so that we can avoid cooking right away. Eat healthy in India: avoid eating fancy, oily or restaurant food all the time. It makes us lethargic and doesn’t feel good. Fly business class next time? Dry fruits (from Costco) make for great gifts.

Case: Mini or micro ATX for sure. Fractal Design or Jonsbo. https://www.wundertech.net/diy-nas-build-guide/#Selecting_Hardware_For_a_DIY_NAS_Build

Used https://www.airalo.com/ on our previous trip to Europe and it worked well. Recently found out about https://esimdb.com/ which seems to be an aggregator of prices across multiple providers. Might try that next time.

As usual, I spent quite some time on side-projects during my ongoing trip to India. Here’s a quick run down: I realized that the firewall I use at home, Opnsense, is a powerful piece of software and I could leverage it more than what I do today. First, I installed Wireguard on it and gradually switched from Tailscale to Wireguard for all self-hosted connections. Well, almost all, because I left Tailscale on one machine in my home, so that it can act as a fall back in case Wireguard has some issues and somehow the internet connection on Opnsense still works. The Opnsense setup was straightforward but I wasted quite some time trying to setup Wireguard through NixOS. I eventually dropped the idea because I decided that a VPN on the router was a better idea (instead of port forwarding and all) and because the Opnsense approach was just simpler. Second, I setup DNS blocklists on Unbound. (Again, pretty easy.) I’ll gradually removed AdGuard Home. IPv6 through Tunnelbroker.