4 ms·
I'm probably in the 5x-10x range, but we are a very small team, and we've been accumulating a backlog of ideas over the years. I drive the architecture, and hav
by bdcravens 2mo ago
I'm probably in the 5x-10x range, but we are a very small team, and we've been accumulating a backlog of ideas over the years. I drive the architecture, and have almost complete autonomy over the work I do. I think someone in my shoes will see a greater result than someone trying to do the same thing in large team, with all the usual process and ceremony, only wanting to go faster.
- RegW 2mo agoWhere as I'm stuck in a big team with a legacy codebase and lots of business rules, performing small incremental changes. So I spend my days banging the Esc key and shouting "Shut the f**k up!". Luckily I work remote. I'd turn it off again, but my usage is monitored and I don't want to look like a Luddite. So may be .75x to .8x range.
- xXSLAYERXx 2mo agoIn my experience a legacy codebase is where LLM shines. What would take days to grok is understood and explained almost immediately. There was a bit of job security with being the one whose worked with IIFEs to manage state. You must know the codebase well if the LLM is slowing you down.
- bdcravens 2mo agoSome of our biggest wins were in a legacy code base, where changes would require a lot of archaeology. I feel like Claude (and probably most coding LLMs) really shine when optimizing fat blocks of SQL, given the complex relational calculus.