text stringlengths 0 2.35k |
|---|
**Natalie Pistunovich:** It sounds like the unpopular opinion is popular... |
**Tiago Queiroz:** Yeah, I also agree. I never worked much with OpenTelemetry, but with other solutions that basically are observability and metrics... And yeah, you can go a very long way with just well-structured logs. Even \[unintelligible 00:47:09.12\] and it's super-simple, because you can just parse them, or put ... |
So my unpopular opinion... I still believe that the testing package from the standard library is the best testing framework that you need; the best out there. It's very simple, it's very powerful, especially now that fuzzing is built into the language, and everything... And because it doesn't introduce new concepts. So... |
\[47:58\] It makes the developer, the engineer writing the code think more about what they're doing, and probably also craft better testing failure messages. So instead of just saying "A is different than B", it's like "No. I was trying to do that, and that failed because of that." You can still fall in the pitfall of ... |
And of course, building a language is very different than building other kinds of applications, but as far as I know in Go, to write code they only use the testing package, so it's powerful enough to write Go... So it should also fit, I'd say most, if not all use cases. And you can always write your helper functions if... |
**Ian Lopshire:** I'm worried that one's gonna be popular as well. |
**Natalie Pistunovich:** Yeah. I brought an unpopular opinion as well. |
**Ian Lopshire:** Oh, wow. Okay... |
**Natalie Pistunovich:** I think that as a manager, a team lead, or a product manager, or whatever, making a round of messages on your tracking system, like JIRA, Trello, and whatever - "What's the status here? What's the status here? What's the status here?", and then your developer arrive the next day to like ten mes... |
**Liran Haimovitch:** Definitely. |
**Natalie Pistunovich:** No, it's supposed to be unpopular. Don't say that. |
**Liran Haimovitch:** Elon Musk is much, much better. Tell everybody they're fired next week if they don't deliver what you came up with overnight. \[laughter\] |
**Natalie Pistunovich:** Now, that's an unpopular opinion. |
**Ian Lopshire:** No, all those status messages never fail to give me anxiety. It's like, "Wait, was I supposed to get all of this done? Ah...!" |
**Natalie Pistunovich:** Even if yes, there's better ways of doing that than ten messages of "What's the status here?" |
**Tiago Queiroz:** Yeah, definitely. |
**Natalie Pistunovich:** Maybe you have an agreement that you should update at the end of every day, every week, every other day, I don't know... If you don't have such an agreement, you should set that up. If the team is not happy with this agreement, you need to find something else, but just around like opening your ... |
**Tiago Queiroz:** Yeah, I agree. |
**Liran Haimovitch:** If you expect people to spend the time to write down the answers, you should spend the time at least to write down questions that prove you know what each task is about, and be more focused about what you're asking, rather than generic "What's your status?" Because I might as well answer "It's pro... |
**Natalie Pistunovich:** Perfect! Oh, my God. Adopting... \[laughs\] |
**Tiago Queiroz:** I would even say some of those status update messages are like debug logs that just say "Yeah, it's moving. It's happening", but most of the time it's not what you need to see, not what you need to hear. |
**Natalie Pistunovich:** True. It is like info-level messages. |
**Tiago Queiroz:** Yeah, what you need is the error level. Like, "Hey, that's delayed because of that", or like "Hey, I had that problem then block it here, so task X, Y or Z is not moving. Or even moving backwards." |
**Natalie Pistunovich:** I think we're onto something here... We also have a lot of questions that we wanted to talk about, and lots of topics we wanted to talk about, and it looks like there's no other choice but to have a follow-up episode. And I wanna say thank you both for joining; I hope you will join too our next... |
• Different stages of engineering interviews, including recruiter screens, technical screens, panel interviews, and on-site interviews |
• Roles involved in conducting interviews for software engineers, including engineers, product managers, designers, and leaders |
• Key qualities assessed during interviews, such as technical skills, leadership abilities, culture fit, and collaboration skills |
• Flexibility in tailoring the interview process to specific teams and roles within a company |
• Common types of interview questions and exercises, including system design, coding challenges, debugging, and algorithm/database-related questions |
• Company mission and problems they're solving |
• Importance of understanding the team dynamic and interviewing with actual team members |
• Use of automated tools in the hiring process (LeetCode, etc.) - pros and cons |
• Differences in interview process depending on job level (associate, staff, senior) |
• Evaluation criteria for different levels of engineers |
• Expectations for knowledge gaps and learning abilities at different levels of seniority |
• Importance of ability to learn and self-starter initiative in engineers at any level |
• Key differences between hiring junior vs. senior software engineers |
• Interview process considerations for startups vs. large corporations |
• Typical length of interview processes and job search timelines |
• Three months' notice in contracts is standard, but companies may take longer to make hiring decisions |
• Take-home assignments for coding interviews should be around 1-2 hours, not 4 hours, to avoid exhausting candidates and provide a fair signal of their abilities |
• Structuring take-homes with specific problems to solve and clear guidelines can help mitigate the risk of over-performing candidates |
• Technical screens in-person are often preferred over take-home assignments due to the potential for burnout and decreased candidate pool quality |
• Preparation for interviews involves practicing and being mindful of the hiring process, including its length and complexity. |
• The importance of practicing interviewing skills |
• Creating a learning plan and prioritizing prep time |
• Understanding the types of companies and roles you're applying for and focusing on relevant areas to practice |
• Practicing speaking out loud against problems and delivering answers clearly and concisely |
• Familiarizing yourself with role-playing and pretending to collaborate in interviews |
• Prepping stories and examples from your experience, including making mistakes and learning from them |
• Crafting answers to common interview questions, such as "Tell me about yourself" and sharing difficult experiences |
• Being mindful of the interviewer's job is not to trip you up, but to understand key takeaways and lessons learned |
• Highlighting key experiences and qualifications for clarity |
• Asking clarifying questions before offering solutions |
• Being honest and humble about limitations and uncertainty |
• Displaying logical thinking and problem-solving skills |
• Showing empathy, teamwork, and willingness to learn from failure |
• Red flag: being overly aggressive or solution-focused without understanding the problem |
• Red flag: exaggerating or misrepresenting experience on resume |
• Red flag: lacking genuine curiosity or interest in the role |
• Importance of candidate research and preparation for interviews |
• Red flags in interviews (sexism, racism, ableism, ageism, lack of empathy, poor communication) |
• Qualities of a strong candidate (initiative, interest in company mission, technical skills) |
• Unpopular opinions: |
• Mustard is better than ketchup |
• Dual monitors are unnecessary and create distraction |
• The panel discusses the necessity of a single monitor for work-from-home setup |
• They argue against having dual monitors or multiple screens, citing unnecessary expense and complexity |
• They joke about how "hacker movies" have exaggerated the need for elaborate computer setups |
**Angelica Hill:** Hello, and welcome to Go time. Today we're going to be talking about engineering interviews. We're going to be talking about tips, tricks, gotchas, as well as some potential interviewing horror stories, positive stories, red flags, things to avoid, as well as hopefully some green flags - what should ... |
I have the absolute pleasure, as always, of being joined by my wonderful, beautiful, intelligent, bafflingly beautiful Natalie as my co-host. |
**Angelica Hill:** Hi, hi. |
**Natalie Pistunovich:** Hello. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.