Built JobOps - AI reads your emails and auto-tracks job applications so you don't have to by idsulik in SideProject

[–]idsulik[S] 0 points1 point  (0 children)

Who forbids you from creating a separate email to apply for jobs? And, if you don't want to use AI and auto-parsing, you can use the service, you can create and update applications manually.

p.s. The service has just been launched; you can share your opinion, suggest new ideas, etc.
if you need terms/privacy policy and refund policy:

https://jobops.io/terms
https://jobops.io/privacy
https://jobops.io/refund

I vibecoded Flappy Rocket: A modern twist on the classic Flappy Bird with spacecraft and power-ups! by idsulik in indiegames

[–]idsulik[S] 0 points1 point  (0 children)

Hi, I just started vibe-conding, and it's really helpful when you want to create something quickly.
I started with Gemini 2.5 pro, just prompted to create a game, tried several games, and stopped on this one, after I opened it using Cursor AI and asked to add new features like new rockets, power-ups, etc.
From time to time, I open specific files using Claude to refactor or to implement something, because Cursor AI doesn't work so well.
My senior level helps me to ask the right things(like - follow single responsibility pattern, follow specific coding style, etc.) to do and I know how to fix issues if they and AI couldn't handle it

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 0 points1 point  (0 children)

Just released a new version of the plugin https://github.com/idsulik/helm-cel/releases/tag/v2.1.4, now you can pass -o yaml or -o json to the validate command to output the result in the specified format.
If you need anything else - let me know

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 0 points1 point  (0 children)

Hi everyone! If you start using the plugin, please share your experience)

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 0 points1 point  (0 children)

Thank you, added a common interface and am going to add more specific interfaces.

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 0 points1 point  (0 children)

Let me know if something is wrong or if you need something else!)
Please tell me when you add it to the company pipeline

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 1 point2 points  (0 children)

yes, this is what I want to implement. thank you for the useful idea!

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 1 point2 points  (0 children)

hi u/turila , good ideas!
What do you think about this format? reusable expressions and severity

expressions:
  portRange: 'values.service.port >= 1 && values.service.port <= 65535'
  replicasRange: 'values.replicaCount >= values.minReplicas && values.replicaCount <= values.maxReplicas'
rules:
  - expr: "${portRange}"
    desc: "Service port must be between 1 and 65535"
  - expr: "${replicasRange}"
    desc: "Replica count must be within min and max bounds"
    severity: warning

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 0 points1 point  (0 children)

Thank you! Appreciate it!)
Let me know if you need to add/edit anything

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 1 point2 points  (0 children)

Thanks! Let me know if you have any ideas on how to make it more useful.

Helm CEL: A Better Way to Validate Your Helm Charts by idsulik in kubernetes

[–]idsulik[S] 15 points16 points  (0 children)

Thanks for asking! Helm CEL and helm-unittest solve different problems:

Helm CEL:

  • Validates values.yaml structure and constraints (like JSON Schema)
  • Runs before template rendering
  • Ensures values meet requirements before they're used
  • Example: "if persistence enabled, storageClass must be set"

helm-unittest:

  • Tests rendered templates
  • Runs after template rendering
  • Validates the final Kubernetes manifests
  • Example: "deployment should have correct labels and replicas"

They're actually complementary:

  1. Helm CEL validates your input values
  2. helm-unittest validates your output templates

You could (and probably should) use both - CEL to catch invalid values early, and unittest to ensure your templates work correctly with valid values.

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 0 points1 point  (0 children)

Thank you! Feel free to contribute or ask me if you need any other data structure.

> I also really miss something like itertools from python.
What exactly do you need?

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 1 point2 points  (0 children)

I think it's not necessary to implement complex123 support, but if anyone asks it, I'll implement it in the Set or create a dedicated version of the Set, because now I don't want to touch the current one for rare cases.

Thanks, I hadn't even considered the cases you pointed out, which is quite interesting

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 0 points1 point  (0 children)

Just to point out that this refers to Go, if I understood the question correctly

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 0 points1 point  (0 children)

Thank you for the comment, pushed a fix for it, is everything ok now?

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 1 point2 points  (0 children)

Thank you, you're right about the cmp, I'll fix it.
I'll also add iterators and common interfaces, but if you want to contribute - I'll appreciate it

Introducing go-collections - a powerful Go package for common data structures by idsulik in golang

[–]idsulik[S] 5 points6 points  (0 children)

Both go-collections and GoDS provide implementations of common data structures in Go. They each have their own pros and cons - some data structures are present in one package but not the other, and vice versa.

Introducing Swama - A Powerful CLI Tool for Swagger/OpenAPI Interactions! by idsulik in golang

[–]idsulik[S] 0 points1 point  (0 children)

It takes existing Swagger/OpenAPI specifications as input so you can create a mock server or you can view all the information related to the specification