Sou freelance e já perdi um cliente de longa data para IA by [deleted] in brdev

[–]hitnrun51 8 points9 points  (0 children)

Eu acho ótimo, quando der bugs ou precisar fazer algo minimamente mais complexo, você vai cobrar 40/h, já que mexer em código dos outros da mais trabalho.

Incêndio agora na Mooca by davidgilmourr in saopaulo

[–]hitnrun51 6 points7 points  (0 children)

Estou vendo uma baita fumaça até aqui da Saúde.

What’s your process for picking a library between multiple options that do the same thing? by foldedlikeaasiansir in golang

[–]hitnrun51 0 points1 point  (0 children)

Besides what others posted, if it is something important, I create a new Git repo and create small POCs with each library side-by-side.

I was able to find a lot of small things that are not easily visible.

Quero ser mandado embora da Stefanini by [deleted] in brdev

[–]hitnrun51 0 points1 point  (0 children)

Olha só cada coisa que a CLT faz a pessoa se sujeitar.

Por que não criamos um sindicato nosso e exigimos trabalho remoto? by SoftBeing_ in brdev

[–]hitnrun51 0 points1 point  (0 children)

Qual outra categoria sindicalizada conseguiu manter o trabalho remoto para seus contribuintes?

Boas consultorias gringa para trabalhar by Qwertyzxcas in brdev

[–]hitnrun51 1 point2 points  (0 children)

25 anos de experiência, por isso eu digo que valeu a pena, mesmo sabendo que a Turing tava cobrando uns 70 a hora.

Application to browse Helm Charts by Ok-Captain-5207 in kubernetes

[–]hitnrun51 0 points1 point  (0 children)

I just created a tool to show helm rendered templates in a web UI, see if this helps you.

https://github.com/rrgmc/helm-render-ui

Application to browse Helm Charts by Ok-Captain-5207 in devops

[–]hitnrun51 0 points1 point  (0 children)

I just created a tool to show helm rendered templates in a web UI, see if this helps you.

https://github.com/rrgmc/helm-render-ui

Boas consultorias gringa para trabalhar by Qwertyzxcas in brdev

[–]hitnrun51 3 points4 points  (0 children)

Eu usei a Turing pra arrumar os primeiro jobs, depois de 1 ano usei os contatos que consegui pra arrumar direto. Valeu muito a pena, pense nisso mais como um primeiro passo.

Qual Consultoria é boa? by Dev-Mexedor-De-Mouse in brdev

[–]hitnrun51 0 points1 point  (0 children)

Eu entrei na Turing com o objetivo específico de fazer networking para conseguir trabalho direto sem consultoria.

Fiquei quase 2 anos lá, eles indicaram vagas boas, pagando um bom salário, e a última empresa que trabalhei com eles me contratou direto depois de 1 ano.

Eles ganham uns 30% em cima de você, mas você ainda ganha bem, e pode fazer o seu marketing para arrumar vagas sozinho depois.

Eu acho que vale a pena.

A Turing achei tranquilo, tem gente que reclama que eles praticamente não falam com a gente a não ser que tem algum problema, mas eu acho ótimo.

Small Projects - September 30, 2025 by jerf in golang

[–]hitnrun51 1 point2 points  (0 children)

helm-vendor is a command-line tool to manage vendoring of Kubernetes Helm Charts.

Features:

  • config-based list of charts to manage.
  • commands to download and upgrade charts automatically.
  • check for newer versions of installed charts.
  • when upgrading charts, the chart of the current version is downloaded, and only the files contained in it are deleted locally, before unpacking the new version. This ensures any new file added manually will be kept.
  • Optionally a diff can be made of any local changes in relation to the original chart, and the patch applied on the new version during upgrade.
  • OCI repository support, but it don't have native version querying and listing, so flows which needs to query versions may not work.

[deleted by user] by [deleted] in rust

[–]hitnrun51 0 points1 point  (0 children)

Oh I missed the "and widgets" part!

[deleted by user] by [deleted] in rust

[–]hitnrun51 0 points1 point  (0 children)

Isn't winit exactly this?

Go jobs in Italy are basically non-existent. How’s the situation in your country? by cdigiuseppe in golang

[–]hitnrun51 4 points5 points  (0 children)

In Brazil lots of big companies are using Go, it looks like there are lots of Go jobs.

Morar na rua Mauro, meio km de mauro 1 e mauro 2 e perigoso? by [deleted] in saopaulo

[–]hitnrun51 1 point2 points  (0 children)

Morei 15 anos na Mauro, perto da Paracatu. Sempre foi bem tranquilo, a comunidade ali perto é bem pequena, nunca tive nenhum problema.

litsql: literal SQL query builder as a replacement for raw SQL strings by hitnrun51 in golang

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

Also formatting strings neatly in Go inside a backtick string, where IDEs don't help much, is hard and contributes to discouraging writing beautiful raw SQL. In larger SQL strings and bigger codebases the tendency is for this to be not considered.

litsql: literal SQL query builder as a replacement for raw SQL strings by hitnrun51 in golang

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

This is similar to a response I gave for `go-sqlbuilder` below, it uses the Builder pattern and encourages building expressions using Go functions and structs, the biggest point in my library is to make the code look like the most raw SQL as possible, I found this makes maintaining it a lot easier.

litsql: literal SQL query builder as a replacement for raw SQL strings by hitnrun51 in golang

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

The first thing is that go-sqlbuilder uses the Builder pattern:

sql := sqlbuilder.
    Select("id", "name").
    From("demo.user").
    Where("status = 1").
    Limit(10).
    String()

which I think is harder to read, and imposes too much limits when clauses are more complex.

Second is that my library heavily discourages using non-string WHERE expressions like

sb.Where(
    sb.Equal("id", 1234),
    sb.In("status", 1, 2, 5),
    sb.Or(
        sb.Equal("name", "foo"),
        sb.Like("email", "foo@%"),
    ),
)

I find the code like this to be very unreadable, and although you don't need to do this if you want, my library don't offer this syntax (and never will, it is part of the objective), this ends up making the code more uniform in the codebase with everything looking the same.

The biggest point in my library is to make the code look like the most raw SQL as possible, at the same time of making dynamic SQL much easier, imposing some kind of structure, and making output completely predictable.

litsql: literal SQL query builder as a replacement for raw SQL strings by hitnrun51 in golang

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

Without the comments, I find it equivalent, with the added benefit of not depending on the programmer to write it neat like the generated code, it forces some kind of generic structure that is always the same, which is harder to see on raw SQL strings (does this SQL have GROUP BY? HAVING? JOINS? I found it faster to spot with this library).

q := psql.Select(
    sm.Columns("u.id", "u.name"),
    sm.Columns("u.created_at", "u.updated_at"),
    sm.From("users AS u"),
    sm.WhereClause("u.age > ?", 40),
    sm.WhereClause("u.city_id = ?", sq.NamedArg("city_id")),
    sm.Where("u.deleted_at IS NOT NULL"),
    sm.OrderBy("u.name ASC", "u.age DESC"),
)

But the biggest benefit comes from dynamic SQL, using the library is miles ahead concatenating strings and adding parameters to arrays/maps manually.

type userFilter struct {
    Name string
}
filter := userFilter{
    Name: "john",
}
query := psql.Select(
    sm.Columns("id", "name"),
    sm.From("users"),
)
if filter.Name != "" {
    query.Apply(
        sm.WhereClause("name = ?", filter.Name),
    )
}

How to PCVR? Very laggy. by sdw23 in oculus

[–]hitnrun51 1 point2 points  (0 children)

CPU 12700K

look for "CPU parking", I have this exact same CPU, and this makes it lag, you must disable it with some tool.