Facens

TLDR: I made a Claude Code plugin to measure coding productivity.

This helped us measure over +70% productivity in iubenda's dev team. Rationale and details follow.

For the past year I've been pretty obsessed with using AI for productivity improvement and I've been running initiatives to increase AI adoption within iubenda and team.blue, particularly amongst developers.

The challenge was to measure the results, but I saw problems with the most commonly used methods: - % of developers using Claude Code: pretty mute, just tells you who is using it, fine for initial rollout but doesn't really give you a sense of what the productivity really is, it's the kind of "tick the box" approach that leaves many companies with a very superficial AI adoption - Number of MRs / PRs: not the worst metric but very unreliable as different teams and developers have different styles in terms of sizes of the contribution (few but large vs many but small), which means that more or fewer MRs / PRs doesn't necessarily mean more or less productive team - Story points: not all teams use story points, plus story point scoring is a qualitative process and subjective. It also requires tracking story points across MRs / PRs / commits, which is very complex as very few teams have really deterministic connection between their git repo and their task management tool, meaning that issues in data coverage makes this method unreliable even on teams that actually use story points - Lines of code changed: I really like the objectivity of this metric, and if we keep as a constant the fact that a specific development team will keep the verbosity of their code and the mix between types of code (tests, translation, updates, comments, refactors, actual new code) indeed constant, then this metric is not bad at all, but in tests this still had huge variability due to large refactors or wide but low value changes skewing the metrics completely

Several weeks into the rabbit hole, I landed on using lines of code changed, BUT scoring them using Haiku. In essence, the plugin will: - Download all diffs from all repos you select, across all branches, and deduplicate them to avoid double-counting merge commits - Score each file diff with Haiku, giving it a weight that will score e.g. 0 a file change, low a translation change, low or zero a library update, high an actual genuine code change or refactor, etc (this can also act as code verbosity index) - Calculate a sort of "weighted lines of code" metric that you can plot over time to measure productivity improvements

Scoring is very cheap at around $7 per K commits.

The plugin also has a # of other features like creating reports, anonymizing developers with local hashing and the possibility to use BigQuery to share the database across a team.

I'm publishing it so you can grill me on the methodology, cross-check it, find bugs, you name it. All contributions welcome

What about Project of the month on www.unixstickers.com/donations ? I can help

What was the use case exactly? The readme doesn't go into much detail about this aspect

Ye there are all sorts of modules. There is also a free version, while the paid one is $27/yr.

Have you ever checked out iubenda (http://www.iubenda.com)? That's pretty much what it does, with 600 modular clauses in 8 languages.

"profitable growth"?

:puzzled:

We created a page at Unixstickers where you can purchase the posters for each of these patent arts and have them conveniently delivered to your home or office: http://www.unixstickers.com/posters/iconic-patent-posters

Check it out : )

Ehrr, feedback taken...

The site was probably down, too many requests, now we scaled the server and it's kind of coping...

Ye this was a WE project that just looked so cool, and some of the libraries needed were already out there. Opensourcing & moving everything to telnet/ssh is probably the next step. For now it was just fun :P

Eehhmm that's because our customers rule? XD Ok, this one was lame :>

Back up anyway with a scaled configuration

The server is suffering seriously, too many people playing with a very alphaish piece of software XD

Sorry guys, it's back up now

Let's keep in mind that opera purchased Skyfire a while ago, which is a lot about server-side engine browsers.

That's exactly what we try to avoid, because not only "doing anything we want with users data" is wrong, but also because it's not legal in most countries. Forcing website owners to inform their users precisely, other than being a legal duty, is how you use transparency to to ensure that users' rights are respected. The moment we forget about informing users and pretending to be informed is the same we start forgetting about privacy rights, and that subtly and slowly leads to huge privacy violations like the whole PRISM shame.

I know that we're still selling stuff, but our hope is to do something good along the way, and a world with more privacy information is surely a better one :)

You can also sign up without facebook! :)

And the part where you sign an NDA

"La Gazzetta del Mezzogiorno" is not a blog, it's a newspaper. The news was reported by other Italian newspapers too, quoting Charles Elachi's words during a speech held in Rome.

This article is totally pointless. It doesn't provide a single argument, just a bunch of assumptions.

IMAP works!

If you want you can generate a readable privacy policy with iubenda (https://www.iubenda.com), while TOS are coming soon :)

Did you try https://www.iubenda.com ?

Thank you for the question. You need to inform the user about the personal data collected. Examples of personal data are cookie, email, username, name, date of birth. I suggest you to add everything you recognize as used on your website. If your website has a blog or a form, I also suggest you to create a different privacy policy just for each of them.

Thank you for asking, and let me know if you have any other question :)

hahah

The reason why we decided to require a registration on the first page is that many visitors started playing with the generator and had no way to register (and to stay up to date) before completing the second step.

This caused confusion and many left the website right after reaching the first step.

So we decided to place the registration on the first generation page, something we did very quickly two days before the launch (happened one week ago). The fact that it was a quick&dirty move caused part of the issues that you suggested to fix :)

Ah, and if you skip it on the first page, you must still sign up at the next one. If you have any other feedback anyway, let me know :)

what?!

The privacy policy is shown right after clicking on the registration button, before we process the information. Your point is absolutely right anyway.

About skipping the registration, you can easily do it by clicking the 'x' on the registration box :)

Thanks for the feedback :)

Also consider that we are a tech/legal startup, and the ability to cover in house some of the legal trickiness was a huge pro on the Srl side. Here some other thoughts I forgot to link on the previous post: http://thinkamination.com/dove-incorporare/ [ITA] Here's a topic on Quora too: http://www.quora.com/What-are-the-benefits-of-being-incorpor...

Also consider that incorporating outside means you have to demonstrate that it's not for a taxation advantage, which would not be legal.