I've interviewed 3k people with Karat as a professional interviewer, and several hundred more as a hiring manager. The very few times I received direct emails from candidates attempting to circumvent the normal process were met with unequivocally negative reactions. First, I find the Internet sleuthing they'd undergo to find my email address a bit creepy – for example, Karat would only show the first name and profile pic for your interviewer. But more importantly, the sheer audacity to go for such a stunt would firmly anchor them in the box of people I'd never want to work with. I'd still be polite and professional to a fault, of course, but I'd never seriously consider them past that point.
But in bad times where "the normal process" can't even let you have a human look at your resume, it's different. "circumventing" is at worst a simple act of rebellion to annoy people who can change their process. It's a best a chance to actually get the response that isn't even granted with a form rejection these days.
I've been calling this context.md in my projects (alongside a progress.md for TODOs and breaking down complex tasks). I don't care what we call it as long as we settle on a convention.
I use it mostly as smarter autocomplete and it's still absolutely worth it. I really tried having it write unit tests in Go, write simple Astro websites, etc, but I'm never satisfied with how dumb it is when "vibe coding", so I use it as Intellisense on steroids for now, but I don't doubt it will become even better soon. The chat feature is fantastic and between it and the contextual help I barely ever have to reach for actual (code) documentation.
Having used Go professionally for over a decade, I can count on one hand the times I used recover(). I've actually just refactored some legacy code last week to remove a panic/recover that was bafflingly used to handle nil values. The only valid use case I can think of is gracefully shutting down a server, but that's usually addressed by some library.
I used to do thousands of interviews across the industry and I vividly remember Apple backend devs being almost always unmitigated disasters. They would always pick Java and could barely use it - to the point where a for loop would be challenging. Their Swift guys were fairly decent though IIRC.
Oof, must suck to work for a company who doesn't use technical design docs well. I quite like Oxide's RFD model, based off Joyent's I assume, given who their CTO is. https://rfd.shared.oxide.computer/rfd/1
I've just recently this video on the engineering of Venice: https://www.youtube.com/watch?v=77omYd0JOeA -- relevantly, it shows how they devised an "active" drainage system that relied on the tide movement (both vertical and horizontal). The timestamp for waste management is 7:45, but I recommend watching all the video.
I found the part about clay cisterns fascinating (6:40). Does anyone know the trade-offs about lining the outside of cellar walls with a thick layer of clay. Would it be effective to pour a slab foundation onto a thick layer of clay? Or, to have a thick layer of clay, and then a few feet of gravel, and to pour a slab onto that?
reply