|
| 1 | +--- |
| 2 | +title: "Hybrid Meetup #51 wrap-up" |
| 3 | +date: 2025-05-28T08:00:00+01:00 |
| 4 | +draft: true |
| 5 | +tags: |
| 6 | +- summary |
| 7 | +- meetup |
| 8 | +--- |
| 9 | + |
| 10 | +## Flaky LLMs and secure containers |
| 11 | + |
| 12 | +Hybrid Meetup #51 took place |
| 13 | +[2025-05-27](https://www.meetup.com/leipzig-golang/events/306803728) 19:00 at |
| 14 | +renewable energy startup [Gridfuse](https://gridfuse.com) and we had two |
| 15 | +shorter presentations: |
| 16 | + |
| 17 | +* Beyond Benchmarks: [Human x LLM for Go and other code](https://github.com/miku/nightjet/blob/main/notes/2025-05-27-lgo-51-short-talk.md) (intermediate report) |
| 18 | +* StackRox architecture and repository setup |
| 19 | + |
| 20 | +### LLM for coding related tasks |
| 21 | + |
| 22 | +LLM use for coding remains constrained to well scoped problems with some human domain knowledge and |
| 23 | +oversight and review. It is still possible to spot generated code, it lacks a kind of handwriting. |
| 24 | + |
| 25 | +Using an LLM can teleport you into a codebase and let you explore or ask |
| 26 | +specific questions. For code generation, a disciplined approach would be to |
| 27 | +review every line of output. |
| 28 | + |
| 29 | +[](https://github.com/miku/nightjet/blob/main/notes/2025-05-27-lgo-51-short-talk.md) |
| 30 | + |
| 31 | +This was an intermediate report and we hope, we can have a more comprehensive |
| 32 | +assessment of the effects on (Go) software development in the future. |
| 33 | + |
| 34 | +### Container security and StackRox architecture bits |
| 35 | + |
| 36 | +We did some architecture and code review along [diagrams](https://github.com/stackrox/stackrox/blob/92e5d0badaf6a86f0691ad39b739fe233ed193bc/central/platform/reprocessor/singleton.go#L11-L25) and [code](https://github.com/stackrox/stackrox): |
| 37 | + |
| 38 | +[](https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_security_for_kubernetes/4.6/html/architecture/acs-architecture) |
| 39 | + |
| 40 | +Some notes: |
| 41 | + |
| 42 | +* [Open Policy Agent](https://www.openpolicyagent.org/) could have been a component, but for the StackRox use case it was deemed to slow at the time |
| 43 | +* StackRox is an example of a vertically scaled project (albeit at some point in the past they had a microservices architecture) |
| 44 | +* data structures are modeled in with [protobuf](https://protobuf.dev/), e.g. for [storage](https://github.com/stackrox/stackrox/tree/master/proto/storage), other code is then generated from these definitions |
| 45 | +* we looked at a singleton service pattern, e.g. used here: [singleton.go](https://github.com/stackrox/stackrox/blob/92e5d0badaf6a86f0691ad39b739fe233ed193bc/central/platform/reprocessor/singleton.go#L11-L25) |
| 46 | + |
| 47 | +Meetup [#48](/posts/meetup-48-wrapup/) also gave a high level overview of StackRox. |
| 48 | + |
| 49 | + |
| 50 | +### Misc |
| 51 | + |
| 52 | +* [What Is ChatGPT Doing ... and Why Does It Work?](https://openlibrary.org/books/OL47286904M/What_Is_ChatGPT_Doing_..._and_Why_Does_It_Work) |
| 53 | +* [SWE-Bench](https://paperswithcode.com/search?q_meta=&q_type=&q=swe-bench) |
| 54 | + |
| 55 | + |
| 56 | +### Thanks, Gridfuse! |
| 57 | + |
| 58 | +Thanks a lot to [Gridfuse](https://gridfuse.com) for providing a great venue |
| 59 | +and atmosphere for our meetup (and |
| 60 | +[others](https://www.meetup.com/leipzig-devops/))! |
| 61 | + |
| 62 | +---- |
| 63 | + |
| 64 | +[Join our meetup](https://www.meetup.com/de-DE/leipzig-golang/) to get notified of upcoming events. |
0 commit comments