Sign in to view Andrew’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Oakland, California, United States
Sign in to view Andrew’s full profile
Andrew can introduce you to 10+ people at ngrok
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
2K followers
500+ connections
Sign in to view Andrew’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Andrew
Andrew can introduce you to 10+ people at ngrok
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Andrew
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Andrew’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Activity
2K followers
-
Andrew Harris posted thisThe 18-24 year old developers are disappearing from industry. This will crash the tech industry worse than the upcoming AI bubble-burst. This can be corrected, but it must be corrected soon. Since 2011, Stack Overflow has published an Annual Developer Survey[1]. The last five years of survey results for developers' age can be directly compared: 18-24 years old: 2025 - 18.7% 2024 - 21.4% 2023 - 20.11% 2022 - 23.46% 2021 - 25.47% Yes, the pandemic happened. Yes, remote work and online learning made it easier for newer participants in the tech industry to get started. We know why there was a boom in 2021/2022. We also know why the 18-24 demographic group is steadily shrinking: - Layoffs disproportionately hurt earlier-career individuals, both in who loses jobs first (juniors), and in who gets hired afterwards (seniors). - AI spending has succeeded in destroying headcount for interns, recent college grads, and similar entry-level roles. These two forces, layoffs and AI spending, seem unlikely to end. But that isn't my point. What we aren't talking about yet is the impact in five more years of a continued decline in the 18-24 demo. If we assume that the trend of roughly -1pp to -1.5pp change in the 18-24 demo continues, then by 2030 we should expect the 18-24 demo to comprise between 11 and 13 percent of developers. That slashes the demo fully in half since the hiring peak in 2021. Additionally, this was the first year in a decade that "under 18" was not represented in the survey results. A population pyramid describes demographic ages in a population vis-a-vis births and deaths[2]. A population is considered to be stable when births more-or-less replace deaths. A population is considered to be at risk of societal conflict when there is significant surplus of unpaired individuals of reproductive age, or when deaths significantly outpace births. We can apply the same lens to the tech industry. Between layoffs (unpaired individuals) and slashed early-career headcount (low "births"), companies are increasingly at risk over time of conflict, constriction, and liquidation. Maybe AI can close some of these gaps. The technology to write software is improving! However, as older developers continue to retire from industry, the hands to replace them simply won't exist. And the technology to write software just isn't ready yet. It's yet to be seen whether it will ever be ready. The long-term answer, as it has been and will continue to be, is to hire more early-career people. Hire interns and co-ops. Hire from underrepresented groups. Hire career-changers and returners. Make room for internal transfers, such as from operations and support roles. Train new people as part of your regular work practices. Companies that do this will survive the demographic crash. Companies that don't will answer to their shareholders, investors, and liquidators. Tick tock. --- 1 - https://lnkd.in/gFnpSzV7 2 - https://lnkd.in/gzhufgwZ
-
Andrew Harris posted thisThe AI agents aren't a replacement for humans. Not now, and probably not for a while to come. I pushed myself to use more AI tooling in my code work over the last few days. I had a relatively tightly scoped implementation of a thing, and a known error case that I wanted to test. I asked the AI agent to generate a unit test for the error case. The AI agent: - Generated an unrelated test. - Generated two more copies of the unrelated test. - Generated a test that asserted that a fixed string contained another fixed string. - Generated a test that asserted "true". - Claimed at each of the above steps that these covered my requested error case. - Claimed, upon correction, that the test was impossible to write. - Got lost in loops at least three times that I noticed. - Lost the ability to reference its own internal tools mid-session. I started a new agent session, and after a bit more prodding I successfully generated a valid test for my requested case. This was with an enterprise account on a popular agent-based AI coding platform. I have no idea how much fresh water I dumped back into the ocean, or how much coal smoke I released into the sky, during this process. "Maybe you asked it the wrong questions." "Maybe it was your prompt or your underlying rules." "Maybe you just got the agent into a bad state." Sure. Whatever. You know who asks me questions, instead of declaring that their test strategy is correct? You know who has so-far never deliberately misled me about the behavior of a test they wrote? A human colleague. An intern or recent college grad. A career-changer or returner. A person who has been at this for ten days, ten years, or whatever in between. Hire more humans.
-
Andrew Harris shared thisThe next gold rush is early-career talent. AI is hot. The boom in AI agents has been driven by high-burn-rate foundation and tooling platforms, short-sighted leaders wooed by promises of slashing personnel expenses, and *vibes*. And what a boom! But someone has to pay for that. AI agents have successfully eaten away hiring budgets typically earmarked for recent college graduates, career-changers and returners, and other kinds of early-career talent. This is true especially in technology roles, however we're seeing it across many sectors right now. [1] Unemployment in June among 22-27 year olds was over 7%, nearly double the national average. [2] When we fail to make room for early-career talent, we fail to grow seasoned ICs and leaders. We will necessarily run out of ICs and leaders, and we will run thin on new ideas and creativity along the way. It's a race against time, measured perhaps in years but nonetheless a race. We must redesign work, so that "early-career" doesn't simply mean "rote, low-level work". The boring, repetitive stuff should be done by AI agents! AI agents are great at complex copy-paste! Work must be restructured so that we "focus on framing the problems, asking better questions, and building relationships" as first-order concerns. [3] We must redesign teams, so that seasoned late-career ICs and managers seek out opportunities to mentor and teach. The best way to understand a subject is to teach it to another. This also creates an opportunity to refine and practice interpersonal communication skills, and for late-career folks to learn what's important for the next generation and what we might improve. Finally, we must redesign leadership, so that C-suite and adjacent leaders see the intrinsic value and necessity of seeking out and hiring early-career talent. This is an existential threat. If your company wants to remain competitive in three to five years when the AI wave comes crashing down, you must hire and begin growing early-career talent now. The next gold rush is early-career talent. And growing new talent is a genuine investment in your company, unlike other kinds of "gold" on the market. 1. https://lnkd.in/g-BYMe3J 2. https://lnkd.in/g2Pgnwku 3. https://lnkd.in/g3vBThqBThe Perils of Using AI to Replace Entry-Level JobsThe Perils of Using AI to Replace Entry-Level Jobs
-
Andrew Harris reposted thisAndrew Harris reposted thisLife Update ▶️I'm back on the job market ◀️ Looking for: - backend engineering role - nyc hybrid preferred, but willing to do full in office or strong remote culture Industry agnostic, but definitely want to be in a role that I can dive deep into the implementation of complex backend system, continue to push my 0-1 skills. I want to be building. About me: - 3 years backend engineer experience + 5 years of dev rel experience + founder experience - wrote golang in previous role, have experience in python - but can pick up any language as needed, have done some work in react and javascript - strong communication/soft skills - public speaking, documentation, and project organization - I work hard at work and outside of work - side projects include building my own linux distro, organized the net gala, and do technical content creation across multiple platforms on a regular basis - MIT grad (MEng + BS in EECS) Can start ASAP My DM's are open - if you know of any opportunities. I am also open for intros to people who you think would be a good connection.
-
Andrew Harris reposted thisAndrew Harris reposted thisYesterday, Checkr, Inc. parted ways with some incredible and exceptionally talented individuals who helped to build Checkr into what it is today. I’m so grateful for each and every person who was impacted for their contributions and impact, and I’m here to support them in their transition in any way that I can. For all who are hiring right now, I would love to connect you with these talented individuals. Their experiences range across all sales functions including both IC's and leaders as well various other roles throughout the business. Please directly comment with roles you are hiring for below - I have some amazing referrals to send your way!
-
Andrew Harris reposted thisAndrew Harris reposted thisAs many of you know, Checkr recently underwent a workforce reduction impacting 32% of our team. It’s been a tough week for all of us, and my thoughts are with everyone affected by this difficult news. ❤️ The people who are impacted by the layoff are some of the most skilled, hardworking and collaborative software professionals I know. I want to leverage my network and support them as much as I can. Here are some ways you can help: 1. Share open positions at your company 2. Recommend specific former colleagues for relevant roles 3. Connect impacted individuals with hiring managers in your network Let's come together and support this amazing group as they transition to their next opportunity. #Checkr #layoffs #jobsearch #opentowork
-
Andrew Harris reposted thisAndrew Harris reposted thisFor those of you who have open positions to fill, I highly recommend you consider employees who were impacted by Checkr's layoffs today. The company laid off 32% of its workforce, including 382 amazing human beings. So many of these folks were my former colleagues and some of the most passionate, brilliant, values-driven and hard-working individuals I have ever met. It is a massive blow for the company and a huge opportunity for all of you employers out there. Highly recommend you snagging them before someone else does! Here are some of those incredible humans that any company would be lucky to have: Chris Dunaway, Paul Keeling, Sean T., Taylor Heuser, Elliot Wright, Griselle Fonseca, Cesar Cuadra, Forrest Drew, Kevin Bruce, Scott Matsuda I will continue adding people as I discover who has left. For my friends and former colleagues, please reach out to me if there's anything I can do to support you in this transition to a new chapter.
-
Andrew Harris liked thisAndrew Harris liked thisLife Update ▶️I'm back on the job market ◀️ Looking for: - backend engineering role - nyc hybrid preferred, but willing to do full in office or strong remote culture Industry agnostic, but definitely want to be in a role that I can dive deep into the implementation of complex backend system, continue to push my 0-1 skills. I want to be building. About me: - 3 years backend engineer experience + 5 years of dev rel experience + founder experience - wrote golang in previous role, have experience in python - but can pick up any language as needed, have done some work in react and javascript - strong communication/soft skills - public speaking, documentation, and project organization - I work hard at work and outside of work - side projects include building my own linux distro, organized the net gala, and do technical content creation across multiple platforms on a regular basis - MIT grad (MEng + BS in EECS) Can start ASAP My DM's are open - if you know of any opportunities. I am also open for intros to people who you think would be a good connection.
Experience & Education
-
ngrok
***** ******** ********
View Andrew’s full experience
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Recommendations received
4 people have recommended Andrew
Join now to viewView Andrew’s full profile
-
See who you know in common
-
Get introduced
-
Contact Andrew directly
Other similar profiles
Explore more posts
-
Sam Barker
IBM • 822 followers
The Kroxylicious projects is excited (when are we not??) to announce v0.18.0. This release focused on supporting authentication both from the broker and in proxy! Release announcement: https://lnkd.in/gQ89SkUt release artifacts: GitHub: https://lnkd.in/gAaTgFKm Maven Central: https://lnkd.in/ghpcRGRV
23
-
Marcos Heidemann
symphony.is • 13K followers
While everyone was talking about Opus 4.6, for me the true killer feature of the recent Claude Code updates is the agent teams. It's been something i've been trying to achieve with customization for a while. Custom agents, orchestration scripts, specific CLAUDE.md instructions to coordinate work... with some degree of success. But what Anthropic shipped natively is a WHOLE different level. What makes this stand out is the inter-agent communication. We're not talking about simple fan-out/fan-in where you spawn workers and collect results. These agents talk to each other. Peer-to-peer messaging, dependency-aware task graphs that auto-unblock, agents that self-claim work from a shared task list. The lead can even enter Delegate Mode where it does ZERO implementation, only coordination. The image below is from one of my setups. A team manager orchestrating a librarian agent, a PhD lead, and 5 research sub-tasks with blocking dependencies. The librarian unblocks the research tasks, the PhD lead aggregates everything. All coordinated autonomously. And with this a whole new world of orchestration just unveiled itself. Distributing work across agents is the "easy" part. You break down tasks, assign owners, define dependencies. The HARD part, and what MOST stands out now, is aggregation. How do you take the output of 5 parallel agents, each with their own context window, and synthesize it into something coherent? That's the new skill. Anthropic themselves used 16 parallel agents to build a 100,000 line Rust C compiler that compiles the Linux 6.9 kernel. No human actively coding. ~$20,000 in API costs over ~2,000 sessions. We went from pair-programming with AI to managing AI engineering teams. The skills that transfer are the ones from engineering management: task decomposition, context management, knowing when to intervene vs let the team self-organize. This is a new paradigm, and i think it opens up several possibilities we haven't fully explored yet. ref.: https://lnkd.in/dVCe344z
68
12 Comments -
Jonathan Desrosiers
Bluehost • 1K followers
In case you missed it when the episode dropped, I was recently on the Crossword podcast. I finally had a chance to write a bit about our conversations on my site. We covered a lot of ground, including the concept of active versus passive contribution, how to find the appropriate balance between those two groups, the importance of being prepared when new contributors show up, and the nuance between a do-ocracy and a meritocracy. I'd love to hear your thoughts after you listen! https://lnkd.in/evmRqabE
-
Stephen Connolly
Radiant • 687 followers
I 100% support this message. Corporate users should all be using an internal permanent caching mirror for both continuity of business as well as potentially security scanning up front. Companies that consume through a permanent caching mirror (i.e. it stores anything it has fetched at least once) should not be the overconsumers that Brian and others are complaining about. Another way to reduce the load would be for the IaaS providers to host their own caching proxies and require their customers to pay if they connect to the artifact storage tiers directly. But the biggest point is that it's in your interest to use a caching proxy. The companies who are thanklessly hosting terrabytes of artifacts for consumption by the community are doing so because it's the right thing... your side of that bargain is to do the right thing yourself and consume responsibly... I suspect that in the majority of cases it's that you have a CI job... if you have it pull the dependencies through a cache then you are consuming responsibly... oh and there's a second win for you too, your jobs are now faster
4
-
Adesh Singh
Lockheed Martin • 124 followers
I was recently asked in an interview: "How would you explain Server-Side Rendering (SSR) to a non-technical person?" The Analogy: Think of SSR like ordering a custom cake online. 🎂 Client-Side Rendering (CSR): The bakery sends you a box of raw ingredients flour, sugar, eggs and a set of instructions. Your browser (the customer) has to do the heavy lifting of mixing and baking the cake before you can eat it. This takes time. Server-Side Rendering (SSR): The bakery does the work for you. They bake, frost, and decorate the cake, then deliver it finished. All you have to do is open the box and enjoy. In simple words: The server builds the webpage completely before your browser even sees it.
4
-
Rhonda Coleman Albazie
Macrodata Refinery • 301 followers
TIMING ASYMMETRY Displacement does not happen evenly. It happens in sequence. First: contractors. Then: new hires. Then: junior roles. Then: middle layers. Finally: senior roles: last, but hardest when it arrives. By the time senior roles are affected, escape velocity is gone. Layoffs are not the signal. They are the lagging indicator. By the time displacement is visible, retraining is already obsolete. — GRACIQ Institute #TimingAsymmetry #AIJobs #Automation #FutureOfWork #LaborReset #WorkforceShift #SystemsRisk #EconomicTransition #GRACIQ
1
-
Jacob Clark
12K followers
At face value the throughput acceleration AI enables feels like progress, faster pipelines and more commits shipped. When you look more closely however, the data reported in the 2025 DORA Report points to a harsher truth... we are moving faster with less control. The metrics behind instability, change fail rate, rework and recovery time are all trending upwards. More often than not, AI is simply automating in failure. The 2025 DORA Report surfaces four painful realities of embedding AI into your SDLC: - AI boosts throughput at the cost of higher deployment failure and rework. We are codifying instability into our pipelines. - Burnout remains flat. Productivity gains are absorbed by higher business expectations, not returned to developers. Faster delivery means faster deadlines. - Over 80% feel more productive with AI. Yet the research shows developers who slowed down by 19% still believed they were 20% faster. Perception of acceleration from AI usage is often just a placebo effect. - The AI Capabilities Model makes value contingent on seven systemic investments, including platforms, data ecosystems and strategy. For many organisations this means a multi-year transformation before they can get close to extracting real value from AI tooling. AI is not a silver bullet, it magnifies the strengths of already high-performing teams, while compounding the weaknesses of others. It is becoming clear that if your team and organisation are already practicing engineering excellence and have a strong, continuously improving product culture, you will benefit the most from AI adoption. If your organisations maturity is low, you are better off investing in foundational changes to your ways of working and culture first.
29
8 Comments -
Satishkumar Dhule
Salesforce • 2K followers
POV: It’s 2026 and your manual infrastructure is a ticking time bomb. 💣 If you’re still running terraform apply from your local terminal, we need to talk. Production-grade IaC isn't just about "making it work"—it’s about making it unbreakable. The 2026 Playbook for Terraform Elites: 🔒 State Isolation is King: Local state is a myth. Use S3/GCS with DynamoDB locking. Separate your Dev/Prod states or prepare for a $100k "oopsie." 📦 Modular or Bust: Stop copy-pasting code. Build versioned modules. Pin everything. If a provider update can break your stack, your stack is already broken. 🛡️ Zero-Trust Secrets: Hardcoding passwords in .tfvars? Straight to jail. 🚩 Fetch them dynamically from HashiCorp Vault or AWS Secrets Manager. 🤖 Policy-as-Code (PaC): Don't just plan. Use Open Policy Agent (OPA) to auto-kill any PR that tries to open Port 22 to the world. Stop clicking buttons. Start scaling logic. 🚀 What’s your #1 Terraform "lesson learned" the hard way? Drop it below. 👇 #DevOps #Terraform #CloudNative #SRE #InfrastructureAsCode
8
-
Chris Rimondi
EXECUTIVE ENGINEERING LEADER… • 693 followers
Just published a new blog post on how engineering teams can “shift down” compliance into platform abstractions. I share thoughts on compliance leverage, OSCAL components vs capabilities, and how platforms can carry the heavy lifting for controls like TLS and mTLS—freeing developers from duplicating effort. Read it here: https://lnkd.in/eh5cABU5 #OSCAL #ComplianceEngineering #PlatformEngineering #ComplianceAutomation
9
-
Brandur Leach
Stainless • 756 followers
Blake Gentry and I are happy to report that River is now SOC 2 Type II compliant! We like to think that we've followed best security practice since day one of starting this thing, but we've gotten enough inbounds requesting a more formal certification that we went ahead and got it. River's now been checked for universal MFA, least-privileged access, controlled change management, and had its own vendors inventoried and vetted (amongst a thorough list of other things). → https://lnkd.in/gvVRjFUr
28
3 Comments -
Yevgen Safronov
Cloudflare • 386 followers
We shipped automatic snapshot expiration for R2 Data Catalog today. With this new feature you can define retention policies (age thresholds and minimum snapshots to keep) so old snapshots are cleaned up automatically, reducing metadata overhead and storage costs while keeping table performance healthy. https://lnkd.in/eAD5rKd8
46
-
Pavan Pothnis
Salesforce • 1K followers
I've always found myself switching to Claude models when working through coding problems. There's just something about how Claude handles context and works its way through large code bases and complex logic. With Claude Code, that workflow has become ridiculously smooth. Also been experimenting with OpenAI's Codex (GPT-5 powered) and the results are way better than previous versions. The code generation quality has taken a real jump. Now here's where it gets interesting. You keep hearing stories about developers opening multiple coding agents, feeding them the same task, and manually cross-referencing outputs to find the best solution. Turns out there's an easier way. By integrating Codex as a skill inside Claude Code, you get insights from both agents in a single terminal session when you need. No tab switching, no copy-pasting, no manual comparison. Claude Code orchestrates the workflow while Codex brings its strengths. Best of both worlds in one window. Claude OpenAI
34
-
Karim Mourra
Prebid.org • 2K followers
PSA for publishers migrating off the Appnexus (Microsoft) cache: don't forget that you also need to update the line items in your ad server. Thanks to Doug Shore’s contributions, Prebid’s Line Item Manager makes it much easier to create the new line items in GAM. Open source and free, as always https://lnkd.in/emgJqyTS
7
-
Sacha Ghiglione
Davos Tech Summit • 25K followers
This is genuinely good. Anthropic is cooking. Introducing Cowork: Claude Code for the rest of your work. Cowork lets you complete non-technical tasks much like how developers use Claude Code. In Cowork, you give Claude access to a folder on your computer. Claude can then read, edit, or create files in that folder. Try it to create a spreadsheet from a pile of screenshots, or produce a first draft from scattered notes. Once you've set a task, Claude makes a plan and steadily completes it, looping you in along the way. Claude will ask before taking any significant actions so you can course-correct as needed. Claude can use your existing connectors, which link Claude to external information. You can also pair Cowork with Claude in Chrome for tasks that need browser access. Cowork is available as a research preview for Claude Max subscribers in the macOS app. Click on “Cowork” in the sidebar: claude.com/download
11
3 Comments -
Deepthi Talasila
Microsoft • 1K followers
Anthropic’s new Claude Sonnet 4.6 promises Opus-level coding at Sonnet pricing Anthropic on Tuesday launched Claude Sonnet 4.6, the latest version of its mainstream model. This new version promises to almost match the company’s flagship Opus 4.6 model, which launched barely two weeks ago, in most tasks, but at the significantly lower price of $3/$15 per million input/output tokens (compared to $5/$25 for the Opus model). Just like the previous version and Opus 4.6, Sonnet 4.6 offers a 1-million-token context window in beta. Stay connected for industry’s latest content – Follow Deepthi Talasila #DevSecOps #ApplicationSecurity #AgenticAI #CloudSecurity #CyberSecurity #AIinSecurity #SecureDevOps #AppSec #AIandSecurity #CloudComputing #SecurityEngineering #ZeroTrust #MLSecurity #AICompliance #SecurityAutomation #SecureCoding #linkedin #InfoSec #SecurityByDesign #AIThreatDetection #CloudNativeSecurity #ShiftLeftSecurity #SecureAI #AIinDevSecOps #SecurityOps #CyberResilience #DataSecurity #SecurityInnovation #SecurityArchitecture #TrustworthyAI #AIinCloudSecurity #NextGenSecurity https://lnkd.in/gJ3USuAK
-
Josh Pollara
Stategraph • 8K followers
A competitor just told our lead they charge 10x for drift detection. 10x. For a cron job that runs terraform plan. That's not a pricing model. That's contempt for your operational safety. Drift detection is 50 lines of code. Schedule. Compare. Alert. Your intern built this last week. But the moment you need it reliable, documented, at scale, suddenly it's "enterprise functionality." They're charging you $50 for airport WiFi because they know you're trapped. They KNOW drift kills. They KNOW you need this. And instead of making it table stakes, like anyone who actually cared about your infrastructure would, they're betting you're too scared of compliance to push back. We've normalized vendors treating our basic safety as a luxury good. Stop accepting this.
47
8 Comments -
Cherif YAYA
Pinterest • 1K followers
What I'm Reading This Week 📚 🤖 Vibe Code Reality Check Steve Krouse's piece argues that "vibe coding" where you "forget that the code even exists" creates legacy code nobody understands. Programming is fundamentally theory building, not just producing lines of code. This resonates - I recently spent hours trying to fix a frontend bug with Claude Code and Gemini CLI stuck in a dead loop of guesses. Two minutes of human inspection found the inefficient hook render. We still very much need the human (expert) in the loop. https://lnkd.in/g_Dt-_kz 📐 Mathematics as Code Dan Abramov's exploration of Lean shows how mathematicians can treat mathematics as code - breaking it into structures, theorems, and proofs that are statically checked and composable. His playful example of "haunted math" where 2=3 demonstrates how axioms shape mathematical reality. Always fascinating to see bleeding-edge programming language theory, especially when it bridges math and code in such elegant ways. https://lnkd.in/gebHeMSU 💻 Local LLMs Innovation Simon Willison highlights how his 2.5-year-old laptop can now write Space Invaders using GLM-4.5 Air and MLX. Open source models are rapidly pushing the frontier of what's possible on a chip. The future where we get GPT-4 level intelligence running on phones feels closer than ever and a powerful enabler for humanity. 🚀 JavaScript's Wild Decade Jamie Birch's comprehensive dive through JavaScript runtimes reveals a staggering ecosystem - from Node.js to Cloudflare Workers to React Native's Hermes. I remember when Apple had a strict no-JS-runtime policy for the App Store. We've come so far that every platform now has multiple JS engines optimized for specific use cases. The proliferation shows JavaScript's incredible adaptability across contexts. https://lnkd.in/g843sYBk 📊 Amazon's Dev Experience ROI Amazon's "Cost to Serve Software" framework quantified a 15.9% reduction in delivery costs through developer experience improvements. The key insight: giving developers back time and reducing toilesome work. For a company with 1,000 developers, a 15% improvement translates to $20M in cost avoidance. Good concrete ROI numbers on investing in developer productivity. https://lnkd.in/ghv5CTfa Which trend do you think will have the biggest impact on software development: local AI democratizing access, the continued JavaScript runtime explosion, or finally having concrete metrics for developer experience ROI? #AI #JavaScript #DeveloperExperience #Programming #LocalLLMs #VibeCoding #SoftwareDevelopment
9
2 Comments -
Jason Godson
Shopify • 774 followers
A small real-world problem: my son had 200+ Roblox friends, and Roblox doesn’t offer a bulk removal option. My latest blog post walks through a simple, browser-based approach using dev tools and JavaScript. Nothing fancy - just practical, repeatable steps for anyone who hasn’t done this sort of thing before. 🔗 https://lnkd.in/gQhsUCdW #webdev #parenting #javascript #automation
18
-
Tim Burnham
Burnham Consulting LLC • 1K followers
How I built a small business app for my wife's family Tl;dr, 1) Use Claude Artifacts to build basic functionality 2) Use cursor / claude code to build it out fully 3) Make mistakes and refactor to different technologies more than I probably should. Long version: 1) Use Claude artifacts to make a simple form 2) port it into GitHub using create react app, connect to vercel (super easy!) 3) get it working (can create and share receipt images, woohoo! In laws love it) 4) move to vite (apparently CRA is old and AI used it) 5) move to nextjs to have a semi backend 6) convert js to typescript (that took awhile) 6.1) Revert at least once due to urgently needed new features. 7) Add a database using Neon 8) Decide not use to Neon, use Prisma instead (because AI suggested that) 9) decide not to use Prisma, use railway instead 9.1) Also switch from Prisma ORM to postgres.js 10) fight with AI not to use "unsafe" 11) build different data views and UI for all database operations (add, edit, delete) 12) Add multiple tables and build out more advanced functionality (like expenses!) 13) learn how to backup and migrate databases 14) create a dev and prod instance in GitHub + railway, start pushing to dev for testing instead of prod 15) eventually try to make a pdf report, fail, build f# backend to make pdf 16) Learn type algebra to and build a super elegant user permission management system. 16) Start moving APIs to f#, make elegant schema system 16.1) Break UX, then fix it. Users slightly confused but they're my in-laws so they'll be ok. 17) Accidentally wipe my local database (it was my fault, not AI's), then restore it from a backup. You are here Next steps - build ability to dynamically build forms. - find another small client - teach AI to build with me Lessons : I find that AI doesn't create bad code, it just has generic assumptions. As I guide it to have better assumptions it gets me to something that I find elegant and easy to work with. Still it starts messy and I have to massage it to something clean. I also find that I move faster if I think first, but often I like to skip that and do first. This loses time (note to self).
5
-
Pamela Fox
Microsoft • 14K followers
During the "Ambient Agents" meetup last week, Brace Sproul gave us a walkthrough of Open SWE, a coding agent built on Langgraph. Open SWE monitors GitHub issues. When it gets a new one assigned, it kicks off a multi-agent architecture with a Manager, Planner, and Programmer. It can receive messages from users at any time during the process and incorporate them into the state. Check out the slides for diagrams explaining each agent: https://lnkd.in/g3PnNHqG And the code: https://lnkd.in/gY68TKYy I found the takeaways really interesting: * Summarization is hard: Especially with code changes that can get quite long, you literally can't send the entire context history to the LLM, and highly detailed old diffs may distract it. IIRC, the agent sends the last 20 messages, and summarizes the changes before. * Agentic > hard coded: Open SWE tends to use the agentic approach of "here are your tools, pick which one to use" for almost all tasks. Except for one.. * Explicit error handling: When an error happens, Open SWE stops everything and focuses on resolving the error. Otherwise, it could get too far afield and be unable to get back to a good place to solve the error. (Hopefully I didn't mis-represent anything I heard!) #Langchain #Langgraph
93
3 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top contentOthers named Andrew Harris
-
Andrew Harris
United Kingdom -
Andrew H.
Metro Jacksonville -
Andrew Harris
Grand Rapids, MI -
Andrew Harris
Orlando, FL -
Andrew Harris
San Francisco Bay Area
2771 others named Andrew Harris are on LinkedIn
See others named Andrew Harris