I like this idea of "technical taste". It gets into where software engineering is as much creative art as it is science. Four great takeaways (IMHO) for software devs in this era in particular: 1. Aspiring engineers should cultivate a sense of curiosity, experiment with different tools and technologies, and embrace a mindset of continuous learning. 2. AI has the potential to streamline processes and enhance productivity for engineers, but it may also lead to disruptions in traditional software development workflows. 3. Developing technical taste and judgment is essential for making informed decisions about which technologies and approaches to pursue. 4. Collaboration and open-mindedness are key to leveraging the full potential of AI and staying ahead of technological advancements. I also really liked these two quotes from Sam Schillace: 1. "The right time to do something is when you have that feeling in the pit of your stomach that's like, 'oh, this is a great idea and it's going to suck to build because nothing's ready yet.'" 2. "Technical taste is like, 'how well have you consolidated that set of experiences and heuristics into judgment that you can apply accurately when you see new things?'" 3. "It may be the case that very small teams can do very large projects, or like we were talking about before, it may be the case we're just going to get really ambitious about what we try to do with the same size of teams, which is kind of where I would put my money." Great job on continuing to put out great episodes, Brett Berson and team First Round Capital! #ai #engineering #softwaredevelopment
Lucas Dickey’s Post
More Relevant Posts
-
As the hiring pace slows down and #GenerativeAI skyrockets, the topic of productivity has become increasingly relevant in engineering teams. The question is: How can we achieve more with less? Sure, you use GitHub Copilot or Sourcegraph Cody or Amazon CodeWhisperer. But is it possible to not write all that code and instead find similar solutions to similar problems already in place within your company? There are a few obstacles that come to mind: 1️⃣ Discoverability. How can I find that solution? 2️⃣ Ownership. Who do I talk to if I want to reuse it or make a change? 3️⃣ Responsibility. If I make a change, does that mean I'm then accountable for any issues other teams may experience with it in the future? 🚀 If you want to increase engineering velocity, as a leader of an organisation, you need to solve for those problems long term. 🪚 Tooling helps with Discoverability. Tooling (again), culture of sharing and code review helps with Ownership. Empowering people to treat company as their own (and a little bit of tooling) helps with Responsibility. 🧐 Speaking of tooling, one radical technical solution that helps to solve those problems too is a company-wide monorepo. Everyone sees everything, can fix bugs and contribute to any product, any small internal tool. All engineers share the same coding convention and keep their dependencies up to date. There is no barrier to share and discover. Owners, as experts, review code and propose changes that work for everyone. Contributors come from every corner of the organisation and can make impact without asking their reporting chain first. ❓What's your end goal - siloed pockets of deep expertise with shallow sharing practices or freedom of innovation and experiments accessible to all? #softwareengineering #engineeringleadership
To view or add a comment, sign in
-
💡 Day 5: We asked Brad Powell, our Vice President of Software Engineering, how is AI impacting software development? 💬 "Artificial Intelligence is poised to reshape how software is developed. With that being said, I don't think that these new AI tools will replace the role of a software engineer, but rather serve as a catalyst to increased creativity. The current generation of AI tools can do this in two ways: 1. Eliminate the need of an engineer to write tedious boilerplate code, freeing their time up to solve more important problems. 2. Provide the engineer with new ideas of how to solve development problems which fosters continuous learning. Our engineering team is busy looking at how we can incorporate AI tools, such as GitHub CoPilot, into our development streams. We're committed at Rival to look beyond the horizon in how we both design and deliver the products that our customers need. It's a very exciting time to be in the software development industry as a member of Rival." #12DaysofAI #Developers #CoPilot #ArtificialIntelligence
To view or add a comment, sign in
-
-
✨ From an eager young developer to sitting in roles leading large teams, my journey in software engineering has been a fascinating evolution. Here's a glimpse of my reflections and tips for building engineering teams and systems: 🌱 Young & Curious: I'd often approached senior developers or CTOs in my early days, expecting them to unravel the mysteries of building exceptional software and managing productive teams. More often than not, their answers left me pondering. 🧔 Stepping into Senior Shoes: Fast forward, as I became more senior, I found myself on the other side - addressing questions from enthusiastic junior engineers. Then I realized how challenging it is to provide an 'elixir' for all inquiries. 🌐 Every Team, Every Company is Unique: What works for one organization will not fit another. 'Excellence' in software is subjective and largely depends on an organization's specific challenges and environments. 🎭 Improvisation is the Key: About 50% of engineering success is improvisation. Crafting solutions based on unique conditions, past experiences, the lessons from failures, and the scars we bear is imperative. 🔍 Back to Basics: The other half is sticking to the basics. It's about designing good APIs, writing high cohesion and low coupling code, ensuring test coverage, embracing automation, enhancing observability, managing incidents, investing in cybersecurity, and most importantly, resilience in bouncing back from setbacks. ⏳ The Evolving Basics: Remember, 'basics' today might be obsolete tomorrow. A decade ago, DevOps was nascent; today, it's a norm. 🤖 The AI Era: Given the pace of evolution, I firmly believe AI will soon be at the forefront, possibly replacing many roles in software engineering. Its capability to grasp the evolving basics swiftly and execute seamlessly makes me wonder: will we soon see an AI-CTO? 🚀 Our Role: As the boundaries of AI expand, it's vital for us to stay ahead, involve ourselves in the innovation, and remain competitive where AI hasn't reached... yet. To growth, adaptation, and the ever-evolving world of tech! 🚀 #growthmindset #softwareengineering #cto #ai
To view or add a comment, sign in
-
🚀 Exciting news for the developers in my network! Augment, a new AI-powered coding platform, has emerged from stealth with an impressive $252 million in funding. Led by ex-Microsoft developer Igor Ostrovsky and backed by former Google CEO Eric Schmidt, Augment claims to have both the best team and recipe for empowering programmers and their organizations to deliver high-quality software quicker. As they prepare for their official release, it remains to be seen how Augment will tackle the challenges faced by current coding assistants, such as issues with software quality, productivity, and intellectual property protection. #AI #Coding #Augment #SCDataAI 🚀
Exclusive: Eric Schmidt-backed Augment, a GitHub Copilot rival, launches out of stealth with $252M
https://techcrunch.com
To view or add a comment, sign in
-
There's been a growing buzz about #AI taking over software development in the next decade or so. But let's dig deeper and understand why this doesn't mean we're, as software engineers, on the verge of being replaced. https://lnkd.in/dx7HKQET #careergrowth , #softwareengineering
The Enduring Role of Software Engineers in the Age of AI: Debunking the Notion of Disappearance
bolshchikov.net
To view or add a comment, sign in
-
The first step in writing code should be asking HOW, but not 𝙩𝙝𝙖𝙩 HOW. How to write the code doesn't matter that much. 🤷♂️ AI could write the code... but we need to know something else! HOW are we going to test it? 👀 What does success look like? If a developer can't explain how we would test their work... did they know what they were doing? They have to understand its impact on everything else. All the things they could break. HOW do we ensure we aren't going to crash production? HOW do we know if your code works? HOW do the users use it? HOW??? 👉 Join 13,000 others for my weekly newsletter for startup founders and engineering leaders: https://lnkd.in/gyDvpfm7
To view or add a comment, sign in
-
Software Engineers 💻 👩💻 👨💻 on my timeline, this question is for you. The surge of AI in software engineering and products is impossible to overlook now. It's abundantly clear that utilizing and building AI software is becoming a top priority for most organizations. Yet, in my conversations with numerous software engineers, it's apparent that not everyone is keeping pace with the dynamic landscape of AI technologies and its evolution. Is it because of the following factors or something else? Lack of Interest 🤷♂️: Perhaps some engineers don't see the significance or potential of AI applications. Overwhelmed by Workload 😓: Maybe many are submerged in their daily office tasks, leaving little time for exploring emerging technologies. Swift Evolution 🚀: The rapid evolution of AI may be outpacing the ability of some professionals to keep up. Uncertainty on Where to Begin 🤔: It's possible that some engineers feel lost, unsure of where to start their AI learning journey. What do you think is going on here? Your thoughts?
To view or add a comment, sign in
-
-
🚀 Exciting News: I'm starting a blog! 🚀 Dear LinkedIn community, I am thrilled to announce the launch of my new blog dedicated to the world of Software Engineering, DevOps, and Artificial Intelligence. 📚🖥️ As technology continues to shape the landscape of our digital age, staying informed and engaged in these fields has never been more crucial. With this blog, I aim to create a space where we can explore and discuss the latest trends, best practices, and innovations in these domains. 👉 What to Expect: 1️⃣ Thought-Provoking Insights: Delve into thought-provoking articles on software development methodologies, infrastructure automation, and the exciting advancements in AI and machine learning. 2️⃣ Practical Tutorials: Learn from step-by-step tutorials that can help you sharpen your skills and excel in your software engineering and DevOps endeavors. 3️⃣ Industry Updates: Stay informed about industry news, breakthroughs, and emerging technologies that are driving our field forward. 4️⃣ Community Engagement: I invite you all to join the conversation! Share your thoughts, ask questions, and let's build a vibrant community of passionate professionals. I'm genuinely excited to connect with fellow enthusiasts, learners, and experts who share a passion for these topics. Together, we can navigate the complexities of our ever-evolving tech landscape and inspire one another to reach new heights. 🔗 Link to the blog: https://ndakic.com I will try my best to post at least one article per week. Please feel free to share your feedback and suggestions. I look forward to hearing from you! #SoftwareEngineering #DevOps #AI #Blogging #TechCommunity
To view or add a comment, sign in
-
In the ongoing TechCrunch Disrupt 2023, GitHub CEO acknowledges that despite AI gains, demand for software developers will still outweigh supply. AI-powered tools like Copilot are revolutionizing software development, but they're not replacing us! Human engineers remain essential as we tackle legacy code and embrace innovative AI solutions. The demand for tech talent is stronger than ever, we still need human engineers to bring the laughter (and the code) to life! #AI #SoftwareDevelopment #TechTalent
To view or add a comment, sign in
-
Join us for a compelling conversation with IT expert Scott Moore ⚛, as we navigate the nuances of modern software engineering. This episode doesn't just skim the surface but dives deep into the challenges and misconceptions surrounding the roles of testers and engineers in today's tech landscape. Scott shares his wisdom on the impact of AI, the evolution of networking, and the vital importance of adaptability and comprehensive knowledge for engineers. Tune in for an episode that promises to expand your understanding of the software engineering universe. 👇👇👇 https://lnkd.in/eA8ABqvw #performancetesting #performancetesters #performanceengieering #performanceengineers #sre #sitereliability #sitereliabilityengineers #DevOps #DevPerfOps #DevOpsFuture #TechTrends2024 #AI #softwaretesting #softwareengineering #testguildpodcast
To view or add a comment, sign in
-