I think what's most interesting is not that this works well for common languages, but it seems to be useful for languages that don't exist yet. If you want _some_ highlighting for your SQL variant, or your language that borrows many common idioms, or just sloppy code that's close enough to the target language, this could be useful.
I don't use them as coding agents, but they can be very useful for things like text transformation, summarizing, or text extraction.
That said, if you have a subscription to a paid model already, you're not necessarily winning out on anything except perhaps privacy, which isn't nothing.
They might have opinions about it, but look at the pay for frontend engineers at the same company. It's not uncommon to see the same seniority be 20% lower than a backend role.
I see a lot of people say you have to use methodology X, or that methodology Y is worthless.
I'm the end, I think we have maybe different uses for notes. Journaling, scratchpads, to-do lists, research, etc.
Take a methodology with a grain of salt. If it doesn't fit, there's a good chance it's solving someone else's problem, but you can always inform your own approach with it.
I think you're operating in a scale that is small enough that there's little risk.
You'll be able to iterate if you run into anything that doesn't work. You should however be clear on what problem you and your team are solving, and not just "get some rag".
Sure - I neglected to include the pain point itself. Right now we spend a large amount of time during troubleshooting of a problem (incident) or when working features related to these two systems, and heavily rely on our existing internal documentation. Rather than combing through tons of those docs, a RAG chatbot made sense to me and the team seems to agree. Will move forward- thanks for the input.
reply