I'm generally against a suspicious attitude towards AI, but am finding it deployed in areas that achieve ludicrously small time-savings, and far greater damage to doing things well. My VSCode editor now has an option to automatically generate my code change commit message. And it's suggested a generic, boring, and unhelpful message, with an icon that suggests an air of magic about what it's doing. "Refactor project structure and remove unnecessary files" A commit message is a small but important part of good source control. Collaborators need to be able to look back and understand what has changed, and why. It's worth a small amount of thinking and taking a few seconds about it, over clicking to auto-generate.
Dave R.’s Post
More Relevant Posts
-
Worth reposting here. 😅 https://lnkd.in/g4Kktqn6 I’m personally really excited for the soon approaching back half of the hype cycle where we can spend time adding some actual software engineering and scalability expertise to the decades of poorly written Python code from the ML world and start implementing features users want without slapping the widely abused phrase “AI” on everything. 🙌🏻 If you think it needs a chat bot, it doesn’t. If you think you’ll get more engagement or find market fit from a “✨ Try it with AI” button slapped on everything, it doesn't and you won't. The best AI-driven features are specific, solve real problems and are so seamless in your product that users don’t need a desperate “LOOK WE HAVE AI TOO” billboard to find them.
To view or add a comment, sign in
-
Enjoying jumping into generative AI and #LLM development. The GitHub repo below provides a hands-on example and walkthrough to quickly spin up your own #LangChain, GPT4 environment with a simple frontend in codespaces ...and (most) importantly, observing LLM application performance with code-level traces for LLM applications with #Dynatrace as you test and productionise. Link to repo: https://lnkd.in/g5W_WFdw
To view or add a comment, sign in
-
🚀 *Exciting News!* 🚀 Introducing *LOCAL JARVIS* 🤖 Unlock chatgpt's pro functionality without any limitations with *LOCAL JARVIS*! The kicker? You can do it all offline! This dream is now a reality. Utilizing the power of the Open source LLM, Vision models and Python's Django/Flask or Streamlit framework, I specialize in creating custom-built smart AI applications tailored to your business needs. Say goodbye to costly API charges and reduce expenses on AI application frameworks. Let's revolutionize your AI experience together! 💡 #AI #Innovation #Technology
To view or add a comment, sign in
-
🎉 After months of work, ~40k lines of code and a hefty bill for OpenAI API usage, I'm really thrilled to present Devra, an AI software engineer. Devra is a desktop app that works with any code you have, or can start a project with a prompt (in the link there's a video for "Create a JavaScript implementation of the game of Snake") Please check it out; it is free to use and I would appreciate any thoughts, suggestions, etc. I hope you love it! https://devra.ai
Devra, Your AI Coding Workerbee
devra.ai
To view or add a comment, sign in
-
Cognition AI presents Devin, the first AI software engineer. Devin is capable of building apps end to end, finding bugs in production codebases, and even fine-tuning some AI models. Devin is the new state-of-the-art on the SWE-Bench coding benchmark, has successfully passed practical engineering interviews from leading AI companies, and has even completed real jobs on Upwork. Devin is an autonomous agent that solves engineering tasks through the use of its own shell, code editor, and web browser. When evaluated on the SWE-Bench benchmark, which asks an AI to resolve GitHub issues found in real-world open-source projects, Devin correctly resolves 13.86% of the issues unassisted, far exceeding the previous state-of-the-art model performance of 1.96% unassisted and 4.80% assisted. The future is here. Congrats to the Cognition team Scott Wu Walden Yan and Neal Wu for building an incredible product.🚀
To view or add a comment, sign in
-
Say goodbye to those frustrating hours spent hunting down small bugs in your code. Introducing AI for Troubleshooting & Resolving CI/CD Failures 🔍 Our bot can now identify and suggest solutions for pipeline review errors, making debugging faster and easier. Check it out 👉 https://hubs.la/Q02BngR00 #AI #DeveloperExperience #GitHub #CodeQuality #DeveloperTools
AI for Troubleshooting & Resolving CI/CD Failures helps break up mental logjams and get you moving in the right direction
cto.ai
To view or add a comment, sign in
-
AI, coding, thoughts. Previously: journalism, Spain, translation, linguistics. 🇬🇧🇪🇸🇫🇷 Serious enquiries: [email protected]
There are lots of interesting AI coding tool attempts happening in the space between AI chat, normal local IDE development (even with Copilot or Cursor) and into all of the usually really boring and hard back-end production stuff: @lovable_dev, @v0, @replit, @stackblitz and now Google IDX. I think the main question I have about these tools at the minute is: are they going to save me time and get it right over complex production coding projects or just make a mess and cause me to waste time fixing it all?
To view or add a comment, sign in
-
🚀 Excited to share my latest blog post on creating a chatbot with a .llamafile and integrating it with a Flask web frontend! 🌐🤖 In this post, I dive into the step-by-step process of setting up the model, creating a Flask API, designing a user-friendly webpage, and running the chatbot smoothly. Whether you're a beginner or looking to enhance your skills, this guide is for you! Check it out and let me know your thoughts! 📚💡 #Chatbot #DataScience #Flask #WebDevelopment #AI #TechTutorial
How to Easily Connect a ‘.llamafile’ with a Frontend Using Flask API and Create a Chatbot
link.medium.com
To view or add a comment, sign in
-
A very interesting point of view regarding different AI techniques for Devs and how to combine more traditional approaches with generative ai bearing in mind their respective strengths and risks. https://lnkd.in/eniXnY-v
The Biggest Risks of AI-Generated Code (What Developers Need to Know!)
https://www.youtube.com/
To view or add a comment, sign in
-
Why context length is the key to better code generation 👇 Most LLM solutions optimize for chat: - Short prompts - Long responses - Limited context But coding is different... Code generation needs to understand: - Dependencies - Call sites - READMEs - Build files - Third-party libraries - Project context Our research shows: code prediction quality keeps improving well beyond 10k tokens of context. The challenge? Processing all that context while maintaining low latency. The numbers: - Chat: ~100 input tokens → 100s output tokens - Code: 1000s input tokens → 10s output tokens Different workload = different optimization needs Here's how we do it at Augment: https://lnkd.in/gVT5kQRg #AIforDevelopers #SoftwareEngineering #CodeGeneration #AI #DeveloperTools #Programming
Rethinking LLM Inference: Why Developer AI Needs a Different Approach
augmentcode.com
To view or add a comment, sign in
Software Engineer at redPanda Software
8moA change that touches 23 files (I'm assuming that's what that badge means) should probably be broken down into a series of atomic commits - you can always squash them later. Commit note generators are generally pretty good, but they're only as good as the commit strategy being executed.