Meghan Perez

Anthropic's latest Claude AI model is taking human-AI interaction to a whole new level! 🖥️🤖 The new Claude 3.5 Sonnet can now use computers just like a human would - by looking at the screen, moving the cursor, clicking buttons, and typing text. This is a major leap forward in AI capabilities. Key features: Operates based on screenshots, emulating human computer use Can perform complex multi-step tasks across different applications Self-corrects and retries when encountering obstacles2 Accessible via API for developers to build with Why it's game-changing: This opens up incredible possibilities for AI assistance in data entry, form filling, software testing, and automating repetitive computer tasks13. Imagine having an AI assistant that can seamlessly work alongside you, handling tedious computer work while you focus on higher-level tasks. While still in beta, this technology demonstrates how AI is rapidly advancing toward more human-like interaction with digital interfaces. As it develops further, it could revolutionize how we work with computers and boost productivity across industries. The future of human-AI collaboration just got a lot more exciting! What do you think about this new capability? #AIInnovation #FutureOfWork Here is a video about it: https://lnkd.in/gh8aNYEu

6

Satya Nadella sparked a new (or reignited) debate about death of apps as a result of AI agents. While he makes a great point on the Agentic AI architecture and how traditional architectures will be obsolete, wondering if front-end apps will go away. Often, tools like Excel or well-designed user interfaces help me identify the right questions to ask. Can AI alone replace the value of that interactive discovery process? What do you think? #ArtificialIntelligence #AI #AgenticAI #AIApplications #FutureOfApps https://lnkd.in/g8UKWQmf

8

1 Comment

While there are certainly individual variations in skill and experience when discussing modern software development the story is much more nuanced than pure individual effort.  * software development is a team sport -- individual performance is heavily impacted by the system in which they are asked to operate in.  * we pair skill and experience to this model of understanding performance by expecting people to be able to influence and adapt in direct proportion to their seniority, aka the more senior you are the more responsible you are for the outcomes of your work, the less senior you are the more your manager and management chain are responsible.  * humans want to succeed, we're social animals who derive purpose from demonstrating skill, and working collectively. All of which is to say there is no way you have over 1000 people underperforming at your company without senior leadership deeply implicated in.  If nearly 10% of your company is failing, versus just having the market move against you, you need to fire the CEO.

150

9 Comments

A data-driven approach to driving wound healing outcomes Marcella Gomez, University of California, Santa Cruz https://lnkd.in/gAkWZYJT Meet: https://lnkd.in/g4AAWkcK YouTube Stream: https://lnkd.in/gwtqaTmf Talk details: https://lnkd.in/gWn3B3cU Subscribe for talk announcements: https://lnkd.in/g5ciuNuX Abstract: Precision medicine requires an ability to predict the response of an individual to a prescribed treatment regimen a priori. Thus, advancement in the field is challenged by a lack of predictive models and, arguably, a lack of time-series information for a highly dynamic system. Here, we discuss work in wound healing, for accelerating wound closure. We argue that timing of treatments is as critical to consider as the choice of drug or therapy. Due to system size and complexity, data-driven methods need to be explored to develop multi-dimensional quantifiable indicators tracking systemic changes. In this work I discuss how bioelectronic devices enhanced with deep learning can help facilitate real-time sensing and actuation for automated decisions in treatment for wound healing and preliminary work in transcriptomic based classification of wound states. Bio: Marcella M. Gomez is an associate professor at UC Santa Cruz in the department of Applied Mathematics and Associate Dean for Diversity, Equity, and Inclusion for Baskin Engineering. She received her PhD from Caltech in 2015 and a B.S. from UC Berkeley in 2009; both degrees in Mechanical Engineering. Her research interests are in the broad field of bio-control leveraging methods in machine learning and control theory. Applications range from controlling single-cell response to driving complex systems such as wound healing. #modeling #simulation #medicine #healing #trauma #predictivemodeling #datascience #data #woundhealing #biology #bioengineering #systemanalysis #sensing #omics

3

Check out the latest in our "Debuggability" blog series! This blog is authored by Kevin Downey Jason Johl and me and talks about how we built a Debuggability Paved Road at Intuit using Ephemeral Containers and Argo Workflows. We'd love to hear your thoughts on the topic. Also, what tools do you build as-a-platform to help debug service, compute and network issues in Kubernetes at scale? #intuit #kubernetes #debug

23

A theory of #softwareengineering effectiveness as the triad of business outcomes, developer productivity, and developer experience. 1. "Effective software organisations focus their investments on the right outcomes." 2. "Effective software organisations make fast and consistent progress toward their goals." 3. "Effective software organisations give engineers the support and tools they need t o feel engaged." WDYT? #technology #operatingmodel #devex #devops #valueengineering #value #engineeringmetrics #cto #cio

3

Large Language Models (#LLMs) are evolving rapidly, and the demand for running them at scale is skyrocketing. #Ollama is stepping up to meet this need with its official container image on Docker Hub, excelling in local #deployments. However, there’s a catch for containerized environments: downloading #models requires the ollama serve command to be running within the #container. This extra step complicates automated deployments via #CI #CD #pipelines, making seamless model access challenging. To take your #model to production, it needs to be #container-ready—a feature Ollama has yet to fully support. The gap in #AIOps for smooth deployments gets blurred with the inference services available as an easy way to take it to production. Goal is to overcome obstacles and deliver solutions 😉 so here is to get you started on having your (O)#llama #production ready in a private #deployment from your #local to #cloud all in #oneshot . Enjoy Medium: https://lnkd.in/g9jqBQ8d dev.to: https://lnkd.in/gi_gGwam #AI #LLM #Ollama #llama3 #phi3 #mistral #S6overlay #AIOps #CI #CD #oneshot #container #docker #podmanEnjoy

11

What it looks like to responsibly deliver educator value using Generative AI -- ensuring reliability and trust -- while moving rapidly and iteratively https://lnkd.in/egUdnV6w

10

Will be really interesting to check how mixed Agentforce agents for Sales, Service, Marketing, Commerce, etc. work together that would balance the utilization of cloud computing resources, or instead influence cloud providers’ computing, memory, networking resource configurations.

15

1 Comment

"Software is eating the world," a phrase coined by Marc Andreessen over a decade ago, rings truer today than ever, especially with the Nobel prizes in Physics and Chemistry awarded to pioneers in AI (John Hopfield, Geoffrey Hinton, Demis Hassabis and John Jumper). AI is transforming modern science and nearly every discipline in fascinating interdisciplinary ways, proving that we are only at the beginning of a revolutionary era. It's not far-fetched that, some day in the near future, we are going to see a miracle drug discovery by AI! #NobelPrize

38

2 Comments

🚨 I took down a major piece of infrastructure as a tech lead at Yahoo! and didn’t get fired…. I think this is the nightmare scenario for engineers - to not only break your own product, but to do broader carnage to systems at the company. I think we all fear what the repercussions are if we do this. However, when intent is good, recovery is swift and learnings documented, these things are actually quite formative. When it happened, I was able to remain calm and walk through a rollback in 2 minutes, which allowed the downstream infrastructure to recover in about 10 minutes. This was also the start to my reputation as a level-headed technical leader. Good relationships with my peers in the infrastructure team allowed us to quickly diagnose that my code push was the cause of the incident and take action. I was leading a team building a very powerful piece of software. We had a client library that was installed on every server and allowed us to push out front-end code to every web property simultaneously. Code changes would propagate in about 2 minutes from push. It allowed us to provide a consistent branding, search and navigation system.  Because we understood the power of the system, we also had plans in place if something went wrong and had practiced rollback and forwards. Typically, when things went wrong, they were minor UX bugs in the interface. Medium problems cost us some dollars in search revenues. However, this time, my change had a massive impact downstream. I had added a new polling feature that worked against the caching strategy of the platform I was calling. Within 2 minutes of diagnosis I executed the rollback strategy. The bad news was the product manager had to wait a few more days for the new feature to roll again respecting the caching strategy of the platform. The good news is that we recovered quickly. I learned a few lessons from this outage: 🚨 Outages happen all the time and you will likely not lose your job if you cause one. 📝 Your team should have plans should an outage happen how you will approach debugging and recovery. ⏰ Practice for urgent situations before they occur. 🏋‍♀️ Building and maintaining strong connections with leads of systems where you have dependency is key. 🧞‍♀️ I have a special ability to appear completely calm while feeling absolute panic inside, which is a good capability to have. 

60

10 Comments

Back in my volunteer days at the San Jose Suicide and Crisis Hotline, I stumbled upon a peculiar realization: our emotions are often reflective mirrors of those we interact with. Fast forward to today's remote work era, this understanding has proved invaluable as an engineering manager. In a world where Zoom meetings replace in-person interactions, it's easy to feel disconnected from your team. But, remembering my hotline days, I've learned to check-in with my feelings during remote 1:1's, sensing the vibe from the other end. If I'm bored, they likely are too - time to shake things up. If I'm anxious, they could be feeling the same - let's address it. This "emotional telepathy", combined with genuine curiosity about my team, regular check-ins, and consistent career growth discussions, has enabled me to build trust and maintain cohesion, even from afar. Sometimes, the past holds the keys to our present challenges. Looking to navigate remote leadership? Feel free to drop a message. Let's connect, share, and grow together. #Leadership #RemoteWork #EmotionalIntelligence #EngineeringManagement ----------------------------------- Check out the full article at https://lnkd.in/gmUUHFWX

8

1 Comment

When I took CS-1411 in college, the professor was great. He had us code in C++, Lisp and a third language that I don't recall. What I thought was most helpful was the way in which he made us think about the strength and weaknesses of each language. Today I generally don't code on a daily basis, but I attend code review sessions and find the language not as important as the concept behind the language. Learning ten languages seems a bit crazy, but learning 3 or 4 different types of languages allows you to understand what to use where and when. https://lnkd.in/e6Yrbk8z

8

3 Comments

"Over 25% of all new code at Google is now generated by AI", according to CEO Sundar Pichai in today's earnings call. But is this shift aimed at speeding up the development of complex software, or simply cutting engineering costs? One potential indicator will be if Google reduces headcount by 25% while boosting revenue per employee. Here are some details behind this productivity metric in Google's own research page . Majority of this '25% code' is in the area of code completion, not in code creation. "LLM-based inline code completion is the most popular application of AI applied to software development..." Watch the video to understand further on this metric.

16

3 Comments

Stop playing Tetris with your teams and projects. Investing heavily in meticulous planning to try and achieve the fantasy outcome of multiple teams, schedules, budgets, people, and projects aligning perfectly to meet your overly ambitious and tightly packed agenda is doomed to fail. The odds of that succeeding are slim-to-none yet, it's what we default to when there's so much we want to do. Do more by doing less! 1) Reduce WIP: Work on less things in parallel, not more. 2) Prioritize: Work on only the thing(s) that will deliver the most value the soonest. Will this guarantee success? No. But, the odds of success are orders of magnitude higher than trying to plan for a perfect game of Tetris. John Cutler's latest installment of The Beautiful Mess, "The Failure Threshold" explains this beautifully. How many of you have been in the following situation (pulled from his post): "If George and Ina each allocate 50% time to Project Thunder, and then Lenny does 10% time combined with moving the two open reqs to Team Apollo and hiring those roles in the next two months, we should—if we sort of combine Project Thunder and Project Inferno—be able to finish Thunder, Inferno, and chip away at Homestead so that when The Hex Pistols are done with the event streaming re-architecture and Project Kafka-esque, assuming Xenia approves the design document, we should be able to hit the deadline for Project Sycamore as promised in the 2023 annual plan."

12

The Site Reliability Engineering: How Google Runs Production System book is arguably one of the most prevalent and well-known SRE resources out there, but there are many other great options for folks looking to expand on their learning. We recently spoke to Google's Reliability Advocate, Steve McGhee, in our Humans of Reliability interview series. In addition to his interesting anecdotes on the early days of SRE at Google, and his journey to becoming a Reliability Advocate, he also shared a handful of his favorite SRE resources, which we compiled here into a list: https://lnkd.in/gpUVhyRa

16

My team and I built an AI agent that helps us debug our production issues. And now we're sharing some code for you to build your own 👩‍💻 I’ve talked to quite a few engineering teams that want to launch an agent for engineering teams to investigate and fix production issues faster. Because there’s no great reference architecture, template, or guide, it took me months of trial and error to get to a point I’m happy with. Now, my colleague Eric Abruzzese has written down several pro tips and steps on how to build an AI agent so you can learn from (and avoid) our mistakes. So what took us months could take you a few hours to do (if not less). In our 3-part series, we cover: 1. How to set up an application in Chainlit 2. How to connect your application to an LLM (in this case, gpt-4o) 3. How to make your Agent faster and add real-time “typing” (similar to ChatGPT) 4. How to give your Agent a personality and specialization 5. How to give your Agent the ability to search a collection of files 6. How to integrate your Agent with external tools (in this case, PagerDuty) Check out part 1 of the guide on our site (link in comments), and keep an eye out for part 2 coming soon (if you want a sneak peek, drop a comment and I'll send you the private Notion page 🕵️).

118

8 Comments

The most clear, fact-based, logically reasoned (and well-written) view on the the positive places that AI can take us from someone who really knows what he's talking about, Dario Amodei (Founder and CEO of Anthropic). This is the article I would have aspired to write if someone asked me to write about this topic. https://lnkd.in/g-xN7zRW

7

2 Comments