Testing CI intelligence platform - troubleshooting, analytics and performance for humans and agents.

Vancouver, BC, Canada
Joined June 2021
Replying to @GithubProjects
Already did ;)
1
3
34
993
currents.dev retweeted
Replying to @GithubProjects
Already did ;)
1
3
34
993
What can possibly go wrong?? 馃拝馃拝馃拝
3
37
currents.dev retweeted
Replying to @theo
Only thing AI is missing is 'verifying' the output of what it has produced. e2e tests help but there needs to be a system around it. Call it verification engineering, proof-driven-development, reliability layer or something else. But there needs to be a system for that
1
1
140
Don't worry people, it's safe :)
2
59
currents.dev retweeted
Replying to @theo
Everyone will move to E2E tests. At the current volume of code generated by agents, verification is the new bottleneck. And you can't do that by code review given the volume of PRs. Plug in some E2E tests and a mechanism to capture and share evidence and you're good to go.
3
3
131
We're all prompt engineers now :)
28
No but why are some docs soooo bad 馃槶
1
46
All regex is internal company folklore 馃拝
1
35
Living dangerously! 馃拃
2
35
currents.dev retweeted
We鈥檝e all taken this exit. 馃殫馃挩 Now, we'll be taking it in flying cars!
1
3
1
6
201
Did the assertion fail tho?
2
33
Am I the only one? 馃槀馃
2
34
Friday is technically Sunday! 馃槀馃槀馃槀
3
40
We鈥檝e all taken this exit. 馃殫馃挩 Now, we'll be taking it in flying cars!
1
3
1
6
201
Sanitisation is important! 馃泚
3
39
What tricks do you use to cut CI time? 馃
1
35
currents.dev retweeted
Guess what takes lesser time 馃
1
1
3
93
Guess what takes lesser time 馃
1
1
3
93