snapzee0

5 ms·

1.
Kotlin mutation testing; single compile; within your test suite(dev.to)
1 points by snapzee0 6mo ago|0 comments
2.
by snapzee0 6mo ago
I don't know,.any developer who would not deliberately decide to not use ai would be easily becoming better in using ai as any non technical person. Non technical people are usually not even able to use versioning software in a good wa
3.
by snapzee0 6mo ago
I think it could also be a good time for middle size open source projects. I built a middle size one which I didn't have started before the era of ai, because i didn't have enough time for it. But with the help i could concentrate
4.
by snapzee0 6mo ago
Hey i build a K2 compiler mutation lib for kotlin. The cool thing is that you only have to compile once. Then all mutation points are configured and enabled in a row via junit extension. So it just works within your test suite.
5.
by snapzee0 6mo ago
The title is click bait. Nothing complex could be built without some form of abstractions. That abstractions are not always right and they could leak is a correct observation. But far away from anything new. The article is correct but trivi
6.
by snapzee0 6mo ago
Yes i guess with the current ai we don't have this kind of learning. What works best for me.is to store important learnings in a instructions file or skill. Also i generate these days always some extra documentation about the overall d
7.
by snapzee0 7mo ago
Hey, this was quite a long read. But the outcome seemed.to me as a.software engineer quite obvious. I would never use any Workflow where there is no readable source code artifact as an outcome. Sure first of all for Humans to understand and