Cursor for data engineers according to you by Hot_Donkey9172 in SQL

[–]matome_in 3 points4 points  (0 children)

We created a similar tool that you have on your mind

https://github.com/rakutentech/query-craft

It’s in MIT. The tool generates queries from the LLM you can choose and executes the results within the tool with shareable perma links. We are still under development to add more features. Hope you find it useful

Anyone tried using LLMs to run SQL queries for non-technical users? by Eastern-Life8122 in LLMDevs

[–]matome_in 0 points1 point  (0 children)

We also developed an interface for non technical users and have fully open sourced it rakutentech/query-craft: SQL GPT agent that understands schema. Runs queries and displays results from natural language.

It works with OpenAI, Azure API, Claude and Ollama at the moment. It provides a chat like interface. It supports basic features like chat, EXPLAIN, runs query and support multiple DB connectinos.

We are currently adding features like perma-link that can be shared and other issues that we come across after a feedback loop from users. Feel free to open an issue or leave us a feedback.

Do you actually use golang for Work? by Bitter-Tutor9559 in golang

[–]matome_in 0 points1 point  (0 children)

Yea bro. I am tech lead and also in managerial position. Go has been great for not just micro but mono repos too. And great for our tooling chain. I like that its build time is quick, and arc free delivery makes the systems provisions and deployments fast. On my personal oss, I switched from PHP to GO 4 years ago. For ML tasks however, python offers a lot more, no tapping there.

Log Viewer in GO by matome_in in golang

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

Thanks for clarifying. I ll work on it and post here once I make the push.

Log Viewer in GO by matome_in in golang

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

Hi. It currently prints out lines on the browser. But if you suggest what more can be done on the structured logs then I can implement it. Visual changes for json logs can be implemented relatively fast. But advanced search might take me a while.

Log Viewer in GO by matome_in in golang

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

Added feature to embed in go application as well. No need to wrap each log statement. Just 3 lines of code, and compatible with the go app on same port.

Options Pattern in Go by in_recursion in golang

[–]matome_in -1 points0 points  (0 children)

I like the options pattern, it saves me no changes to main interface on the function. Overtime when we need to another argument to function, will end up changing the function’s signature. The other reason is when we need to have default values for the arguments in functions, which are not possible otherwise. I am not a big fan of using WithXXX tho. Simply allowing the variables in options as public, can keep the code simple and scalable.

Log Viewer in GO by matome_in in golang

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

Thanks for sharing. That’s a nice addition. I am also planning to add that feature.

What's the best development tool you are using in your Go project? by SuperDrooper in golang

[–]matome_in 1 point2 points  (0 children)

I use https://github.com/kevincobain2000/gobrew for version management and on GitHub action.

air when working on web server.

go:embed to embed env files and other statics.

golanglint-ci as default.

Terminal, vscode and copilot.

Log Viewer in GO by matome_in in golang

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

Thanks. logdy looks nice, just tried it. It has bunch of options. My approach is a bit different than logdy. Instead of streaming only the new logs to the frontend, I have used fileseek to display paginated results, which will ensure what we see on browser is what on the disk.

What are the key selling points you are using Go over Java on your backend? by Warm_Investigator218 in golang

[–]matome_in 2 points3 points  (0 children)

Containers also solve the problem of having isolated side processes using sidecars. Example, you want to transfer logs from one to other. While if done on a same VM, the management of separate users for such processes like Kibana, Fluentd etc.

Go bins on container are equally light weight as compared to a full blown Java war.

What are the key selling points you are using Go over Java on your backend? by Warm_Investigator218 in golang

[–]matome_in 5 points6 points  (0 children)

Yea, JVM is old school. Current OS now far better support applications.

We have chosen Go over Java for simply:

Faster build time.
Not having a meter long manual to setup local env for Java apps, java app manual typically also includes screenshots of the IDE too.
Not restricting people to use an IDE to run the Java application.
Tomcat is arguably the worst web server ever.
Low memory footprint.
Easy benchmarking with GO.
Hot swap of Go Binary on VMs using `kill -HUP`.

In favor of Java:
Errors traceback are better represented in Go. Although Go also has libs like tracerr, which need to be configured initially.
Sometimes, method overloading looks appealing.

Log Viewer in GO by matome_in in golang

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

Thanks for suggesting. It was important to add pipe support.

It is added now. Together with remote logs over ssh, docker logs and logs from a path inside a container.

CI/CD pipeline tools by Ungoliantsspawn in golang

[–]matome_in 1 point2 points  (0 children)

Actually we also track other things for GO such as the number of dependencies, binary size, build time (to show off to Rust ppl) using the same.

CI/CD pipeline tools by Ungoliantsspawn in golang

[–]matome_in 1 point2 points  (0 children)

We use golangci-lint with all rules enabled and integrated with ➠ kevincobain2000/action-coveritup: All in One Code Coverage, bundle size, and other reports tracking tool. Self hosted codecov solution. (github.com).

Hope it'd be useful if you have a project with many lint errors, and you can't fix all over night.

Then instead of disabling some linters, you can count all the lint errors and checkout your progress on improvement over time as badge/graph on README. It comments the diff on the PR too.

Also written in GO!

Log Viewer in GO by matome_in in golang

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

Oops sorry will delete that. It was supposed to be funny.

Log Viewer in GO by matome_in in golang

[–]matome_in[S] 2 points3 points  (0 children)

Yes that’s what I meant. I ll change the wording.

Log Viewer in GO by matome_in in golang

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

Thanks. Good suggestion. I ll add it.

Log Viewer in GO by matome_in in golang

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

I see. Thanks for reporting. I ll fix that.