Hacker News Reader

malogaon Making games in Go: 3 months without LLMs vs. 3 days with LLMs

Agreed, I got an LLM to build me a Super Mario Bros game with 0 code and it's playable after 2 prompts but I'm stuck with the spritesheet as well.

malogaon Making games in Go: 3 months without LLMs vs. 3 days with LLMs

Nah, whatever bug you're referring to is my fault, haha, don't blame the LLM. But in between game state bugs are very unlikely, haha: https://github.com/marianogappa/escoba-de-15/blob/main/src/A...

I can't imagine state surviving a location reload with nothing on local storage and no server.

malogaon Making games in Go: 3 months without LLMs vs. 3 days with LLMs

I think the reason is because you have to pay a non-negligible amount of money per game you publish, and most don't expect to make that back. In my case, making money wasn't my goal, as I explain in the article.

malogaon Making games in Go: 3 months without LLMs vs. 3 days with LLMs

No need to think or guess. You can just bite the bullet and actually read the article. I explained why I built it.

malogaon Ask HN: Could you share your personal blog here?

https://marianogappa.github.io/

I had a couple popular blogposts on Go/Scala related adventures. My blogposts were often published in Golang Weekly.

malogaon Crypto influencers are preying on millennials who found salvation in crypto

Just to clarify, this refers to a paragraph where I claim that many see BTC/ETH as the fastest viable way to multiply your savings.

I do not offer any kind of paid services to make money at all! I'm just an engineer sharing a pet project, which doesn't involve money at all, yours or mine.

malogaon Crypto influencers are preying on millennials who found salvation in crypto

Thanks! I use Google Charts + manual CSS-based overlays, ran via google-chrome --headless, triggered by the Golang binary that runs the cron that evolves predictions. I'm going to write a blogpost about the architecture, because I think it's an interesting one worth sharing.

malogaon Crypto influencers are preying on millennials who found salvation in crypto

Reddit link: https://www.reddit.com/r/CryptoMarkets/comments/wxidq0/crypt...

malogaon Zoom is reinstalling itself after a minute of being uninstalled [video]

Very unlikely, because we've double-checked on a couple of machines at the office here. Only on Mac though. Would be useful if we get some more confirmations.

malogaon Vulnerability in the Mac Zoom client allows malicious websites to enable camera

Btw Zoom is also reinstalling itself one minute after uninstalling it. Made a video of it here: https://news.ycombinator.com/item?id=20390755

malogaon We saved $50k/year with a Go microservice coded in a hackathon

Blogpost author here. Thank you so much for all the attention, comments, upvotes, likes, retweets, etc! I've done a pass over the comments and can't really answer them all but I'd like to clarify a few things:

There seems to be a general opinion trend that the queries generated by the group builder algorithm are very inefficient, that it'd be easy to come up with a solution with much better response times, and that that would be achievable in any reasonable programming language in roughly the same time with similar results.

The language argument will always be controversial and I won't address it here; we have a point of view that is expressed in the Conclusion and on this blogpost: https://movio.co/en/blog/migrate-Scala-to-Go/

I can imagine that seeing a query with JOINs, subqueries, GROUP BYs and UNIONs can raise some eyebrows, but there is some lacking context in that story, and that's on me. Here's some of that context:

* The schema that the group builder algorithm operates on is not uniform in nature or composed of simple yes/no fields; it's an incredibly complex legacy schema that to a large degree wasn't even up to Movio: it's been up to the film industry as a whole, and it has evolved over the years, as is the case everywhere. Note that every different kind of filter translates to a very different kind of query, and we have more than 120 different filters, sometimes with dynamic parameters, and sometimes even bespoke for a particular customer!

* The group builder algorithm predates the team that built this service (myself included), as well as predating the first commercial release of Elasticsearch, MariaDB, mainstream Go success, etc. Nevertheless, it's still very fast and is being used today by ~88% of our customers (i.e. all the non-behemoths). It's been successful for many years, and continues to be, for the most part.

* But I don't like it because it's fast: I like it because it's simple and flexible. It allows our customers to build a really complex (and arbitrary) tree of filters to segment their loyalty member base, and it compiles all of that into one big SQL query, that in most cases is quite performant. That's pretty awesome. But yes; it doesn't scale to several million members.

* Migrating the very engine of the main product of a company is not a decision that is taken lightly. As is the case with every big company I can remember (e.g. Twitter, SoundCloud), behind a big success story there's always a legacy monolith, and our case is no exception. From that standpoint, achieving such breakthrough (i.e. cost reduction + significant response time improvement) within one hackathon day is really not all that common in my experience. Definitely something worth sharing, IMO.

Hopefully that clarifies some of the questions :) Cheers.

malogaon We saved $50k/year with a Go microservice coded in a hackathon

Blogpost author here. That is correct. Sorry if the explanation isn't super clear; for this particular question, you can consider the two diagrams as a before and after. They pretty much convey what you have explained here.

malogaon Making the move from Scala to Go

That's not what I meant to emphasise, but kind of. I was contrasting the Scala programming experience to this: https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ which seems to be pretty much the point expressed by the Coursera people in the blogpost I quoted from them.