Just came back to work today to find that OneDrive lost me almost all of Friday’s work. My changes are nowhere to be found in “previous version”. OneDrive is such a mess.
Well, often you don't get to "dump" your pension fund. In Denmark, it is your employer deciding what pension fund to use, and you will then have to use it. It is kinda ridiculous.
AFAIK only pension contributions mentioned in a collective bargaining agreement is mandatory. If you get offered a regular contract offering a salary plus 10% pension you can accept the job, write an email to HR stating that you opt out and get the extra 10% as take home pay. You can the make voluntary pension contributions to whatever pension fund you have a private agreement with. And all the private pension companies are very happy to make such an agreement, though the terms will be worse than an employer plan from the same company. Or you could do a completely self-administered one, e.g. through Nordnet.
Not OP, but a very simple example: I use AI to review my work before opening a PR for my colleagues to review. I ask it to review the commits in my branch. Instead of consuming tokens just to instruct it how to use git operations and other tools to find the commits since the base commit, I asked AI to create a little bash script to make patch files commit1.patch, commit2.patch, commit3.patch, etc, for all the commits in my branch since the base commit. Now I just use this script to prepare the context of commits to review.
I feel like an imposter here, I’m definitely not using AI as much as it seems everyone is :( I can’t imagine using hundreds of dollars of tokens a day. But maybe this little tip for reviews might be helpful to someone.
Not op, made a tool to convert Microsoft OneNote notes to Obsidian canvas and Markdown. First it used a python lib which was too limiting. Then it used windows API to plug into OneNote and read the doc in its original XML form. That made the conversion correct and fully featured.
Not OP, but I've been focusing on linting and automation.
Custom lint rules to encode best practices that previously relied on astute/alert code reviewer to call attention to. This is handy not just for humans but it steers the bots too. Or turning on some existing rule that required a big cleanup/migration to be compliant with. Now I just throw an LLM at it, since they're often laborious but mechanical changes. Which is the sweet spot for an LLM.
Also automating everything I can. That annoying release process that everyone hates but wasn't quite long/arduous enough to justify the time before? It's now automated. GitHub workflows for all the things.
This kind of stuff will forever be useful, even if the bottom drops out and the bubble bursts. And none of it is reliant on AI to run
> What's really happening is that a few employees realized they can game the system by turning on a firehose of AI slop and pushing 10x the LOC than any other engineer (with or without AI)
Did they figure out how to game the system? Or was the system set up exactly with incitaments to produce exactly this outcome?
They figured out how. Mind you the system was setup with incentives to produce this outcome - but before AI it wasn't really realistic to produce all those lines of code even though you could and so nobody was gaming it so badly it broke. (it was always broke, but the breakage was acceptable before)
reply