text stringlengths 0 2.35k |
|---|
• They think they are raising the bar too high, making it difficult for others to match their skills. |
• The speaker tries not to be unreasonable when interviewing candidates and assesses if they can learn during the process. |
• They present challenges that require internalization and practical application, such as problem-solving under constraints. |
• The goal is to see how candidates think and act in real-time, rather than just solving pre-existing problems. |
• Opportunities given to the speaker and their potential for growth |
• People's loyalty when given opportunities and a chance to prove themselves |
• The importance of trying new things and investing in one's potential |
• Embracing failure as an opportunity to learn and grow |
• Addressing preconceived notions and biases based on past experiences |
• Acuity platform is in beta and focuses on Kubernetes native application delivery, Argo CD, and GitOps |
• Co-founders Jesse Suin and Alexander Matusenchev discussed their vision for the platform |
• They aim to provide a fully managed Argo CD solution and improve developer experience with new tools and ecosystems around Argo |
• Acuity wants to integrate multiple tools into its DevOps platform and deliver a user-friendly interface that enables developers to achieve what they need in just a few clicks. |
• Mention of Argo CD enterprise readiness |
• Explanation of what makes Acuity platform unique (audits and analytics out of the box) |
• Comparison to previous experience at Intuit |
• Promotion of LaunchDarkly platform for software delivery, innovation, and deployment |
• Brief mention of host's background in C++ and development |
• Mention of a jobs fair where an idea was discussed |
• Discussion about a requested workshop or presentation |
• Mention of procedural code and Go programming language |
• Questions about the reasoning behind the request for the workshop |
• Exclusion of certain patterns and approaches due to incompatibility with team's coding style |
• Explanation of past reorganization efforts and unsuccessful middleware pattern implementation |
• Discussion on the concept of object-oriented programming and its benefits |
• Comparison between Go and other programming languages (Pascal and Java) |
• Explanation of how object-oriented thinking makes coding easier |
• Reflection on why some people may not understand or utilize object-oriented principles in their work |
• Mention of a real-world problem that led to the development of an object-oriented language |
• The speaker mentions Go being compared to Pascal as a child of its branches |
• The speaker's familiarity with Pascal is limited and they don't see similarities between the two languages |
• The speaker believes that knowing about language histories can be useful but not always necessary |
• The discussion turns to C++ and JavaScript, both having many features that are rarely used |
• The importance of letting go of unused features in programming and focusing on maintainable code is emphasized |
• Discussion of people's reluctance to use a certain concept |
• Use cases for a particular technique (with billing mentioned as an example) |
• A quote from Rob Pike about a professor using multiple classes for a simple lookup |
• Comparison of Java and Go programming languages regarding type awareness and explicitness |
• Concerns about creating complex code bases for simple tasks in non-Go programming languages |
• Go is explicit and requires clear design choices |
• Packages should meet the open/closed principles |
• Type assertions can be used to extend functionality |
• Designing extensible code is challenging |
• Interfaces are key for encapsulating and extending functionality |
• Clear documentation and teaching others are difficult without proper understanding of the problem |
• The speaker is trying to write a package that is extendable and usable |
• Different programming languages have different requirements for writing packages |
• In Go, the speaker does not need to expose interfaces like in other languages |
• Writing a good package requires thinking about how people will use it |
• The speaker struggles with teaching how to write good packages |
• Defining what makes a package "good" is unclear |
• Discussion of why the command-line tool "curl" is effective and does not require redesigning |
• Reflection on defining when object-oriented programming (OOP) tasks are complete |
• Transition to a more lighthearted tone, discussing "aha moments" in career development |
• Mention of an upcoming workshop that will guide participants through a maze-like exploration of OOP concepts |
• The moment when one realizes they can do something (in this case, coding) |
• Lack of confidence and the importance of trial by fire |
• Succeeding in something previously thought impossible |
• Interview experiences and advice to "just go" and not wait |
• Unpopular opinion on AI-generated code tools and their limitations |
• The relationship between AI and coding, specifically whether AI systems can write code or understand object-oriented programming (OOP) |
• The idea that AI may not need to follow the same constraints as humans when creating code |
• The possibility of using bots for static analysis or dynamic analysis to evaluate if something is complete or open/closed |
• The value of collecting opinions from non-professional developers about Go and other languages, rather than teaching them the language |
• Evolution of best practices in Go |
• Influence of Go on other languages and industry |
• Openness to being influenced by non-Go developers |
• Unpopularity of opinions and the "hall of fame" |
• Relationship between Go and Object-Oriented Programming (OOP) |
• Security audits and pen testing for tech startups |
• Discussing code and business logic, with a focus on identifying scary parts that may break functionality |
• Mention of the importance of prioritizing and checking complex code segments |
• Comparison to a TV show "Severance" regarding intuition about potentially problematic areas |
• Credits for partners and thanks to listeners |
[0.00 --> 4.06] The answer is I don't know, but I am leaning towards yes. |
[4.26 --> 6.66] It is an object-oriented programming language, |
[6.98 --> 10.58] and it's because of multiple features that it has. |
[11.00 --> 13.46] And to explain why I think it's an object-oriented language, |
[13.58 --> 18.02] I should probably explain why I think it's definitely more object-oriented, |
[18.40 --> 22.98] for instance, than other languages that are considered object-oriented. |
[22.98 --> 24.98] And I'm looking at you, Java. |
[30.00 --> 35.66] This episode is brought to you by our friends at Square. |
[35.94 --> 37.98] Square is the platform that sellers trust. |
[38.46 --> 42.72] There is a massive opportunity for developers to support Square sellers |
[42.72 --> 45.30] by building apps for today's business needs. |
[45.66 --> 48.48] And I'm here with Shannon Skipper, Head of Developer Relations at Square. |
[48.88 --> 51.54] Shannon, can you share some details about the opportunity for developers |
[51.54 --> 52.88] on the Square platform? |
[52.88 --> 53.62] Yeah, absolutely. |
[53.86 --> 56.52] So we have millions of sellers who have unique needs, |
[56.84 --> 59.92] and Square has apps like our point-of-sale app, like our restaurants app, |
[60.00 --> 63.72] but there are so many different sellers, tuxedo shops, florists, |
[63.86 --> 66.28] who need specific solutions for their domain. |
[66.54 --> 69.96] And so we have a Node SDK written in TypeScript |
[69.96 --> 73.72] that allows you to access all of the backend APIs and SDKs |
[73.72 --> 77.62] that we use to power the billions of transactions that we do annually. |
[77.84 --> 82.20] And so there's this massive market of sellers who need help from developers. |
[82.28 --> 86.94] They either need a bespoke solution built for themselves on their own Node stack, |
[86.94 --> 90.80] where they are working with Square dashboard, working with Square hardware, |
[90.80 --> 93.62] or with the e-com, you know, what you see is what you get builder. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.