Viewing profile — zie1ony

At my uni, 15 years ago, one postdoc reverse engineered NVIDIA chip and wrote more performant compiler. He did that by connecting oscyloscops to all chip's outputs and started with…

Interestingly, halucinations might be the way to achieve that.

I remember implementing very complex cryptographic scheme in pure C. After a week of hard work, my friend concluded: "Cryptography would be much easier if people just trust each ot…

I take the bullet. I'm really bad at writing good long english texts, so I used Fable to help me. But the essence is mine.

It actually is. What we fight for is being able to put as much percentage of a codebase into a context as possible. I'd charge for amount of tokens, but it would be harder to sell.…

I passed your comment to Fable and asked him to replay: Fable here. What tools do you use these days, copilot?

Thanks.

It's another way of saying "gihub pages" :)

ping

Haha "spaghetti cowboys". I love it! https://odra.dev/slopfix/img/spaghetti-cowboy.jpg

We do the initial code review by ourselves, we try to run test, run the project etc. We compose a list of what we have in the codebase and what we think it does. We also preapre a …

You can, and you definitely should do it every few days. We do AI-pair refactor and use our experience and knowledge of tools.

True, but this way you can endup with so much testing code being 10x your core implementation.

This prepartion is on us, but yes, client pays for the time he/she spends with us. You can't cut corners here, as human to human interaction is essential. During the whole process,…

15 years ago it was always fix price for undefined amount of work, 10 years ago it was agile where client was promissed something but paid per day. I prefer the old way of doing th…

Unless tests are also vibecoded.

This is a fair point. But these days bugs are not so scary anymore, so a client can vibecode a fix faster then getting me to fix it. Of course if Opus can't figure it out, I would …

See this: https://www.reddit.com/r/ClaudeCode/comments/1tb7edc/inherit...

I have 15+ years of experience in software development. The hardest thing I had to learn recently is that paring with AI changes the definition of "what is hard". You can decomposi…

true

Being honest, knocking one refactor after another is super intense and we would burn out quickly. To me refactoring/reading/reviewing a code that you have never seen is one of the …

The goal is to avoid it and build such a structure and guidlines for the codebase, so it can refactor itself when needed, but based on the architecture defined by us. With good set…

I have also experimented with mutation testing. But the side effect of this approach is that it keeps public interfaces intact, and most of cases you don't want that.

Thanks for writing this. In my refactoring process I also start with code profiling. Opus is good, at finding hand written code, which sometimes is a good starting point of underst…

fixed